Agent skill · software engineering · sickn33
repo-maintainer
Audit and repair repository hygiene across artifacts, dependencies, CI, docs, Git state, and code-quality signals. Use for repository maintenance, cleanup, health checks, or pre-release hardening.
Why this skill is useful
Adds specific commands and checks for repository hygiene that the AI wouldn't reliably generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Repository Maintainer Overview Audit repository health, apply authorized repairs narrowly, and finish through the repository's own protected workflow. When to Use 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. Repository Policy Gate Before mutation: 1. Read root and nested AGENTS.md, contributor guidance, maintainer docs, and release instructions. 2. Inspect the current branch, worktree, staged files, remotes, default branch, and effective branch protection. 3. Discover repository-native validation, synchronization, merge, and release commands. 4. Preserve unrelated user work and generated outputs that are not in scope. 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. Usage 1. Establish the baseline 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. 2. Audit independent lanes Run independent read-only checks in parallel where possible. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/repo-maintainer--3e4eed