Manage codebase instructions
Use when the user wants to create, audit, or maintain repository instruction files. Determine whether the repository uses AGENTS.md, CLAUDE.md, or another host-recognized filename, then manage its hierarchy, overrides, fallbacks, and directory scope. Do not use for agent orchestration or unrelated documentation.From its SKILL.md
npx -y skills add seanforge/skills --skill manage-codebase-instructionsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.7 KB, as published. Nobody here has run it
Manage Codebase Instructions
Shared workflow
Instruction files hold durable guidance that agents cannot reliably derive from the repository.
Use whatever sections the repository needs. Keep concise mandatory rules and small essential context inline; group longer non-code information by topic in Markdown files and leave only links; omit anything code or configuration explains.
- Read the effective instructions, code, and configuration.
- Apply the content boundary above at the broadest valid scope.
- Preserve unrelated changes and validate the result.
Choose the workflow
- When no effective root instruction file exists, or the user explicitly requests a fresh setup, read repo-setup.md and use root-instruction.md.template.
- When a noncanonical override or configured fallback is already effective, use maintenance.md. Migrate to the canonical root instruction file only when the user explicitly requests it.
- For an audit, correction, extension, or cleanup of existing instructions, read maintenance.md.
- For nested instructions, hierarchy audits, or moving rules between directories, also read hierarchy.md.
- For a full rebuild, read both workflow references and the hierarchy reference when nested files exist.