governance-kit-review
Use when reviewing changes to Agentic Doc Governance Kit itself, especially templates, generated footprint config, repo-local skills, README usage examples, CLI commands, checkers, release metadata, or package contents. Use this whenever the user asks to review a governance kit diff, inspect a new skill, or check whether a kit change missed synchronization.
- License 许可
- MIT
- 最近更新
- 2026-07-21
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- governance-kit-review
- description
- Use when reviewing changes to Agentic Doc Governance Kit itself, especially templates, generated footprint config, repo-local skills, README usage examples, CLI commands, checkers, release metadata, or package contents. Use this whenever the user asks to review a governance kit diff, inspect a new skill, or check whether a kit change missed synchronization.
03 SKILL.md 正文
Governance Kit Review
Use this skill for code-review style inspection of this kit's own changes. Prioritize user-visible breakage, broken generated installs, stale registry entries, invalid command examples, and missing tests.
Scope
- Review template, script, CLI, checker, skill, and documentation changes
- Verify generated files are tracked in
.agentic-doc-governance.json - Check repo-local skill registry consistency
- Check README project shape and command examples
- Check local-checkout and npm-package command paths
- Check release packaging risk
- Recommend focused tests or smoke checks
This skill is for review. Do not edit files unless the user asks for fixes.
Default workflow
- Inspect the worktree and diff:
git status --short
git diff --stat
git diff
- For every new managed file under
templates/,scripts/,bin/, examples, or public metadata, verify it is listed in.agentic-doc-governance.jsonwhen generated-footprint checks should require it. - For every new or renamed skill, verify:
templates/.codex/skills/<skill>/SKILL.mdexiststemplates/.codex/skills/README.mdlists the skill- the skill includes
## Scope,## Default workflow, and## Output format - README's intended repo shape includes the skill if the shape is shown
- Review command examples from the point of view of an AI agent executing them:
- local checkout commands should use
node /path/to/kit/bin/agentic-doc-governance.mjs - package commands should use
npx agentic-doc-governance-kit - target repo commands should pass
--rootwhen the CLI is not installed inside that repo
- local checkout commands should use
- For CLI/checker changes, look for missing tests around invalid arguments, dry-run behavior, JSON output, rollback, path safety, and generated install smoke.
- For docs/template changes, run or recommend:
npm test
- If release packaging may be affected, run or recommend:
npm run release-check
Output format
Report findings first, ordered by severity:
- file and tight line reference
- severity
- bug or regression
- why it matters
- concrete fix
Then report:
- tests reviewed or run
- open questions
- brief change summary
04 同仓库更多 Skills
implementation-surface
Use when implementing or reviewing project-specific application code after feature lifecycle handoff.
governance-kit-operator
Use when installing, refreshing, or operating Agentic Doc Governance Kit in a target repo, including init dry-runs, generated governance files, feature lifecycle CLI usage, checks, and final user reports. Use this whenever the user asks an AI agent to set up this kit, apply it to another project, initialize governance docs, create governed feature work, or explain the operational workflow.
feature-readiness
Use when deciding whether a planned feature can move into implementation, including blocker analysis and artifact decisions.
feature-lifecycle
Use when adding, planning, updating, verifying, closing out, archiving, or relocating a project feature under the repo's documentation governance model.
feature-lifecycle
Example lifecycle skill.
governance-kit-target-smoke
Use when validating that Agentic Doc Governance Kit initializes correctly into a target repository, including init dry-runs, generated file presence, installed skills, docs checks, skills checks, and optional feature lifecycle CLI smoke tests. Use this whenever the user asks to test install output, verify init behavior, or confirm generated templates work in a target repo.