Home / repo-engineering

Repo Engineering

Repository engineering skills: verify documentation claims against the working tree, run an audit whose every finding cites a resolvable path:line, write AGENTS.md and CLAUDE.md that hold only what code cannot say, check a README's first screen, rank untested functions and entry points, write onboarding guides only from cited facts, plan restructures from the import graph, mine ADRs from git history, run offline hygiene checks with SARIF, check release notes against the commits between two tags, sweep stale branches with delete commands printed for review, check an implementation plan for required sections and unanswered questions, and check an MCP server's server.json and package files against the MCP Registry's publish rules before publishing.

Plugin repo-engineering, version 0.6.0, 13 skills, MIT licence. Source: repo-engineering-skills. Synced .

Install

In Claude Code, add the marketplace and install the plugin:

/plugin marketplace add basitalisandhu/claude-skills
/plugin install repo-engineering@claude-skills

Or copy the skill files into ~/.claude/skills/ from a clone:

git clone https://github.com/basitalisandhu/claude-skills
cd claude-skills
python3 install.py --user --only repo-engineering

Skills

SkillWhat it doesScripts
adr-minerRecover design decisions that were made but never written down by mining git history, manifest and config changes and rationale comments, then draft MADR stubs (status proposed) that cite a commit SHA on every line; a second script lints an existing docs/adr folder for numbering, status and superseded-link problems.yes
agent-context-writerWrite or refresh AGENTS.md and CLAUDE.md so they hold only what an agent cannot learn from the code, and lint them for lines that restate manifests, scripts, dependency lists or directory trees, paths that do not exist, generic advice and length over a budget.yes
cited-codebase-auditAudit a whole repository against a fixed checklist (structure, entry points, dependency hygiene, dead code, test coverage, secrets and config, CI health) where every finding cites a path:line with a quoted snippet, and a bundled validator rejects findings whose citation does not resolve.yes
docs-truth-checkVerify that a repository's README, docs/, AGENTS.md and CLAUDE.md still match the code, checking file paths, links, CLI flags and defaults, environment variables, symbol names, config keys, npm and make targets and version strings against the working tree.yes
mcp-registry-publish-preflightCheck an MCP server repository offline before mcp-publisher publish: a bundled script reads server.json and the local package.json, pyproject.toml and README, Cargo.toml, .csproj and Dockerfile, and reports what the official MCP Registry's documented rules would reject (name, description, version ranges, registry URLs, ownership markers, _meta size), plus DNS or HTTP proof record format.yes
plan-grillStress-test an implementation plan before anyone writes code: put a fixed set of questions to the author (scope, interfaces, data, failure modes, rollout, tests, open questions), fold the answers into the plan, then run a bundled script that checks the Markdown for the required sections, placeholders, a missing rollback and questions with no owner or answer, listing each gap with its line.yes
readme-who-what-whyCheck whether a README's first screen answers six questions (what it is, who it is for, why it exists, how to install, one example, where to ask), flag hype words, list the gaps as a to-do list, then fix them with verified text.yes
release-notes-verifierCheck a release's notes against what changed between two tags, flagging notes that match no commit, commits with no note (chores excluded by a pattern), manifest versions that disagree with the tag, and missing compare links; pull request titles are read only when asked.yes
repo-hygiene-bundleRun one offline hygiene pass over a repository and report findings with severity as a table, JSON or SARIF with a CI exit code, covering manifests without lockfiles, lockfile drift, version splits across workspaces, missing licence or SPDX fields, redacted secret-shaped strings, actions pinned by tag, write-all workflows, missing SECURITY.md, and large or built files.yes
repo-onboarding-guideWrite an onboarding guide for a repository (how to run and test it, where things live, which services it needs, who owns what) only from facts a bundled script extracted with a path:line citation each, then lint the guide so every command, path, variable, service or owner matches a fact.yes
restructure-plannerPlan a repository restructure (split or merge packages, fix module boundaries) from the real import dependency graph of Python, JavaScript and TypeScript files, reporting the most coupled files, import cycles and god modules, and proposing a move plan with blast radius and git mv commands it prints and never runs.yes
stale-branch-sweepClean up a repository's branch list safely: a bundled script joins saved gh and git exports (remote branches, for-each-ref dates and committers, merged refs, PR list) and reports merged branches never deleted, branches idle for N days, branches with an open PR and protected ones, with the last committer as owner, then writes the exact git push --delete commands as a list to review and never runs them.yes
untested-entry-pointsFind public functions, classes and CLI entry points that no test mentions in Python, JavaScript and TypeScript code, rank them (entry points first, then size and fan-in), and write characterisation test stubs in the project's framework.yes

Plugin README

Thirteen skills for repository audits, documentation, release checks, branch clean-up, plan reviews and MCP Registry publishing, each with a tested standard-library Python script. Install with /plugin marketplace add basitalisandhu/repo-engineering-skills and then /plugin install repo-engineering@repo-engineering-skills. Skills appear as /repo-engineering:<skill>, and Claude also invokes them on its own when a request matches a skill's description.

SkillScriptUse it to
docs-truth-checkskills/docs-truth-check/scripts/docs_truth_check.pyverify README, docs/, AGENTS.md and CLAUDE.md claims against the working tree; exit 1 on drift
cited-codebase-auditskills/cited-codebase-audit/scripts/repo_facts.py, skills/cited-codebase-audit/scripts/audit_validate.pyaudit a repository from a deterministic inventory, and reject findings whose path:line citations do not resolve
agent-context-writerskills/agent-context-writer/scripts/context_lint.pywrite AGENTS.md or CLAUDE.md with only what code cannot say, and lint out what a parser can see
readme-who-what-whyskills/readme-who-what-why/scripts/readme_check.pyscore whether a README's first screen says what, who, why, install, example and where to ask
untested-entry-pointsskills/untested-entry-points/scripts/test_gaps.pyrank untested public functions and entry points and write characterisation test stubs
repo-onboarding-guideskills/repo-onboarding-guide/scripts/onboarding_facts.py, skills/repo-onboarding-guide/scripts/onboarding_lint.pyextract cited facts, write an onboarding guide only from them, and flag sentences no fact supports
restructure-plannerskills/restructure-planner/scripts/restructure_plan.pybuild the import graph, find cycles, coupling and god modules, and print a move plan with git mv commands (never run)
adr-minerskills/adr-miner/scripts/adr_mine.py, skills/adr-miner/scripts/adr_lint.pydraft MADR stubs from decision commits, config changes and rationale comments, and lint an ADR folder
repo-hygiene-bundleskills/repo-hygiene-bundle/scripts/hygiene.pyoffline hygiene findings with severities, as a table, JSON or SARIF, with a CI exit code
release-notes-verifierskills/release-notes-verifier/scripts/release_notes_verify.pycompare release notes with the commits between two tags, and version fields with the tag
stale-branch-sweepskills/stale-branch-sweep/scripts/stale_branch_sweep.pyreport merged, stale, open-PR and protected branches with their last committer, and print git push --delete commands for review (never run)
plan-grillskills/plan-grill/scripts/plan_grill.pyask a fixed question set about an implementation plan, then check the Markdown for required sections, placeholders, rollback, failure modes, test kinds and unanswered questions
mcp-registry-publish-preflightskills/mcp-registry-publish-preflight/scripts/registry_preflight.pycheck an MCP server's server.json, package ownership markers, Dockerfile label and proof record offline against the official MCP Registry's documented publish rules

Requirements: Python 3.11 or newer on PATH as python3, and git for adr-miner and release-notes-verifier. No network access (except release_notes_verify.py --gh), no third-party packages.

Use it for technical due diligence before taking over or acquiring a codebase (cited-codebase-audit), to see a package's internal dependency graph of imports before a split (restructure-planner; it does not graph third-party packages), or to record who owns what from CODEOWNERS in an onboarding guide (repo-onboarding-guide). No skill measures bus factor from commit history.

Find this when you search for: stale docs, technical due diligence, import dependency graph, ADR backfill, repository hygiene, delete stale branches, merged branches cleanup, review an implementation plan, design review checklist, MCP registry publish, server.json validation, mcp-name marker.