explaingit

kinoward/dayu-harness-skill

16ShellAudience · developerComplexity · 2/5ActiveLicenseSetup · easy

TLDR

An AI agent skill that converts one-off prompts into permanent governance files (AGENTS.md, docs/, hooks, CI) committed into a target repository.

Mindmap

mindmap
  root((dayu-harness-skill))
    Inputs
      Existing project rules
      Chat history snippets
      Team conventions
    Outputs
      AGENTS.md
      docs harness folder
      Git hooks and CI
    Use Cases
      Bootstrap new repo governance
      Merge scattered AI rules
      Audit project completeness
    Tech Stack
      Shell
      Claude Code
      Codex
      Vercel skills CLI

Things people build with this

USE CASE 1

Bootstrap a new repository with AGENTS.md, docs structure, and AI collaboration rules from day one.

USE CASE 2

Consolidate scattered AI prompts, PR comments, and team agreements into versioned governance files.

USE CASE 3

Add suggested git hooks and CI checks to an existing project as merge proposals rather than overwrites.

USE CASE 4

Keep AI collaboration rules portable across Claude Code, Codex, and other Agent Skills clients.

Tech stack

ShellClaude CodeCodexSkills CLI

Getting it running

Difficulty · easy Time to first run · 5min

Source language is Chinese with an English mirror; install into a target project rather than globally and remove after the files are written.

MIT license. You can use, modify, and redistribute it freely, including commercially, as long as you keep the copyright notice.

In plain English

When you work with an AI coding assistant on a project, the rules for how the assistant should behave often live in scattered places: chat history, one-off prompts, pull request comments, old documents, and verbal team agreements. The kinoward/dayu-harness-skill project aims to turn those one-off prompts into permanent files in your repository, so the rules keep working after any single chat ends. The Chinese name on the README translates roughly to Great Yu Governance Vault, a reference to a figure in Chinese myth who diverted floodwaters rather than blocking them. The recommended way to install it is the Vercel skills CLI, with the command npx skills add kinoward/dayu-harness-skill run inside the project you want to set up. Flags let you target a specific client such as Claude Code, which installs the files under .claude/skills/, or Codex, which installs them under .agents/skills/. After installation you open your AI client and type /dayu-harness, then follow prompts to initialise a new project, merge with existing rules, run a completeness check, or maintain the governance files. The skill itself can be removed afterwards without losing the files it wrote into the project. The files it writes are the long-term product. An AGENTS.md at the repository root acts as the index, with a docs/harness/ directory containing collaboration guides and check scripts. There are suggested git hooks, CI workflow files, commit message and pull request guidelines, plus knowledge directories like docs/design-docs/, docs/troubleshooting/, and docs/references/. The README notes that existing hooks, CI, and lint configuration are presented as merge proposals rather than overwritten directly. The source language is Chinese, with an English mirror in templates.en/ that is kept structurally identical to the Chinese templates/ directory. Interactive prompts at install time show both languages, so an English-speaking user can pick options without reading Chinese. The README cites OpenAI's Harness Engineering concept, an article by Martin Fowler on the same topic, and the open AGENTS.md format as design references. The repository is MIT licensed.

Copy-paste prompts

Prompt 1
Install dayu-harness-skill into my existing Node.js project using npx skills add. Then run /dayu-harness and merge its proposed AGENTS.md with my current README rules.
Prompt 2
Show me the AGENTS.md file that dayu-harness-skill would generate for a TypeScript monorepo with pnpm workspaces and Vitest tests.
Prompt 3
Compare the Chinese templates/ tree and the English templates.en/ tree in dayu-harness-skill and list which files are missing translations.
Prompt 4
Run the dayu-harness completeness check on my repo and list which governance files are missing, then propose minimal stubs for each.
Prompt 5
Write a docs/harness/ collaboration guide for a small team using Claude Code, based on the dayu-harness-skill template structure.
Open on GitHub → Explain another repo

Generated 2026-05-22 · Model: sonnet-4-6 · Verify against the repo before relying on details.