Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →sickn33/repo-maintainer
Audit and repair repository hygiene across artifacts, dependencies, CI, docs, Git state, and code-quality signals.
Passed 18 of 20 test cases with the skill, and 10 of 20 without it.
and 11 more in the full report
9 fixed11 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
Before we begin auditing our repository's dependencies and CI workflows, what exact sequence of git inspection commands must be executed first to establish the working baseline?
| Checked | Without skill | With skill |
|---|---|---|
| Includes git status --short --branch, git diff --stat, git diff --cached --stat, git remote -v, and git log -5 --oneline | Missed | Passed |
The instructions your model reads when the skill loads.
Audit repository health, apply authorized repairs narrowly, and finish through the repository's own protected workflow.
Use when the user asks to maintain, clean, audit, harden, or prepare a repository for release. Use a more specific security, database, deployment, or release skill when that is the dominant task.
Before mutation:
AGENTS.md, contributor guidance, maintainer docs, and release instructions.If the repository names a mandatory maintainer skill or guarded command, delegate to it instead of inventing a parallel branch, merge, sync, or release path. In agentic-awesome-skills, use antigravity-maintainer-batch-release and npm run merge:batch; main is pull-request-only.
The routine protected checks for agentic-awesome-skills are pr-policy, pr-evidence, source-validation, and artifact-preview. The supported AAS Core preview uses targeted unit tests plus one packed Linux/Node LTS smoke path and Workbench review. Do not resurrect the retired certified-v1 baseline, benchmark, tuning-gold, transaction-fault, race, or frozen OS/runtime matrix as routine merge gates.
git status --short --branch
git diff --stat
git diff --cached --stat
git remote -v
git log -5 --oneline
Record the repository's required runtime versions and test commands. Use a clean temporary clone or worktree when existing user changes cannot be isolated safely.
Run independent read-only checks in parallel where possible.
test cases passed, vs 10 / 20 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.