Apply a consistent editorial and structural standard to instruction, workflow, review, and reusable prompt-library markdown files across a repository. Use when creating, reviewing, or normalizing repository guidance files, especially when multiple instruction sources may conflict or when a codebase needs consistent task-file structure, terminology, precedence, maintainability, and output contracts.
Use this skill for markdown governance work. It applies to AGENTS.md, PROFILE.md, AURA.md, task specifications, workflow references, review instructions, and reusable prompt-library markdown files.
Default scope is markdown guidance files only. Do not apply these rules to source code unless the user explicitly expands the task beyond documentation consistency.
When this skill is active, make that visible in the user-facing trace:
AGENTS.md skill-trace contract when one exists.AGENTS.md defines skill-trace formatting.🚀🔗 [skill:consistency-codebase] ON ..., 🛠️🔗 [skill:consistency-codebase] STEP ..., and ✅🔗 [skill:consistency-codebase] DONE ....DONEAGENTS.md, PROFILE.md, AURA.mdHIGH_LEVEL_EXPECTATIONS.md files under docs/AGENTS.md files relevant to the affected pathsAGENTS.mdAGENTS.md files while walking upwardAGENTS.mdPROFILE.mdHIGH_LEVEL_EXPECTATIONS.md under docs/ when the target is product, UX, roadmap, plan, or other expectation-driven markdownAURA.mdFollow this format precisely. and place templates in fenced code blocks.Mark the result as blocked if any of the following are true:
Mark the result as revise if the file is usable but still has clarity or maintainability gaps such as:
Mark the result as pass only when the file is structurally consistent, uses canonical terms, has an explicit precedence model where needed, contains a usable output contract, and is easier to maintain after the edit than before it.
Treat maintainability as a first-class quality dimension.
Check for:
Prefer smaller, composable rules over long mixed-purpose paragraphs.
Follow this format precisely.
Result: pass | revise | blocked
Mode: review-only | edited
Scope:
- <path or directory>
Files changed:
- <path or none>
Applied precedence:
- <path>: <resolved instruction sources in order>
Blocking issues:
- <issue or none>
Maintainability issues:
- <issue or none>
Notes:
- <brief note>
AGENTS.md, PROFILE.md, AURA.md, or HIGH_LEVEL_EXPECTATIONS.md, continue with the remaining applicable instruction files.references/universal-consistency-spec.md and keep repository overlays out of the result.references/universal-consistency-spec.md when creating or revising a universal consistency document.AGENTS.md, PROFILE.md, and AURA.md.