repo-audit
Ensures repository consistency by auditing current state and requirements before any edits.
Install
mkdir -p .claude/skills/repo-audit && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14450" && unzip -o skill.zip -d .claude/skills/repo-audit && rm skill.zipInstalls to .claude/skills/repo-audit
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Audit MCOS repository state before implementing a phase. Use before edits in every phase.Key capabilities
- →Read the active phase file and manifest.json.
- →Inspect readFirst paths for the current phase.
- →Identify old contracts that conflict with the phase objective.
- →Produce a file-by-file edit plan.
- →Identify tests and validation commands before editing.
How it works
This skill reads the active phase file and manifest.json, inspects readFirst paths, and identifies conflicting contracts to produce an edit plan and test strategy.
Inputs & outputs
When to use repo-audit
- →Pre-edit repository health check
- →Verify phase objectives
- →Identify conflicting contracts
- →Plan test updates
About this skill
Repo Audit Skill
Use this before editing.
- Read the active phase file.
- Read
handoff/realignment/manifest.json. - Inspect all phase
readFirstpaths. - Identify old contracts that conflict with the phase objective.
- Produce a file-by-file edit plan.
- Identify tests and validation commands before editing.
- Do not edit until the plan is explicit.
Output:
## Phase audit summary
- Phase:
- Existing contracts found:
- Conflicts:
- Files to edit:
- Tests to update/add:
- Validation commands:
- Risks:
When not to use it
- →When the user intends to perform edits without a prior audit.
- →When the user needs to modify the repository state directly without a plan.
Limitations
- →The skill does not perform any edits itself.
- →It requires an explicit plan before any editing occurs.
How it compares
This audit provides a structured plan for repository edits by identifying conflicts and required tests, which differs from directly making changes without prior analysis.
Compared to similar skills
repo-audit side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| repo-audit (this skill) | 0 | 3mo | No flags | Beginner |
| resolve-conflicts | 81 | 8mo | Review | Intermediate |
| dependency-upgrade | 26 | 5mo | Review | Intermediate |
| git-commits | 21 | 4mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
resolve-conflicts
antinomyhq
Use this skill immediately when the user mentions merge conflicts that need to be resolved. Do not attempt to resolve conflicts directly - invoke this skill first. This skill specializes in providing a structured framework for merging imports, tests, lock files (regeneration), configuration files, and handling deleted-but-modified files with backup and analysis.
dependency-upgrade
wshobson
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.
git-commits
bonny
Create well-structured git commits in logical chunks following best practices
git-advanced-workflows
wshobson
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
github-multi-repo
ruvnet
Multi-repository coordination, synchronization, and architecture management with AI swarm orchestration
git-workflow-enforcer
CrazyDubya
Ensures commits follow conventional commits, branch naming conventions, and PR templates. Use when creating commits, branches, or PRs, or when user mentions git workflow.