kitbash / skills
#Skills catalog
First-party skills, dogfooded on this repo. The selection rule is deliberately strict: if a frontier model already does it well from a bare prompt, it is not a skill. Skills earn their place through project grounding, enforcement, or composition — everything else is prompt-pack filler.
Status, plainly. One skill ships today: prereview, in examples/skills/. The other six below are designed in detail — problem, workflow, artifacts, failure modes, success criteria — but not yet built. They are listed so the design is public and reviewable, not to imply you can install them.
#Available now
Runs your team's actual review standards against a diff before it ships — standards grounded in what reviewers on this repo really flag, not a generic checklist. Emits findings@1; in gate mode it fails on severity high or above.
kitbash install gh:singhharsh1708/kitbash/examples/skills/prereview
kitbash compilePreview exactly what each of your agents would receive, before installing:
kitbash preview gh:singhharsh1708/kitbash/examples/skills/prereview#Designed, not yet built
Full specifications for each live in the catalog document — internal workflow, commands, configuration, prompt core, success criteria, failure cases, and extensibility.
Answers “why is this code like this?” with evidence — the commit, the PR discussion, the issue that made it so — then offers to record the answer durably so it is never excavated twice.
Turns a red CI run into a classified verdict — flake, environment, or real regression — with the evidence, and either a retry, a quarantine PR, or a bisected culprit.
Turns an issue into a file-level implementation plan: touchpoints, files deliberately not touched, ordered steps, risks, test plan, rollback. Emits plan@1 for downstream skills to consume.
Proves a change actually works by driving it, and produces the evidence as verify@1 rather than asserting success.
Runs checkpointed migration campaigns across a codebase — resumable, with progress that survives interruption.
Writes a living codebase tour: how a request flows end to end with file:line waypoints, five files to read in order, and the conventions that will surprise a newcomer — every cited path verified at generation time.
They are designed to compose rather than stand alone — /excavate feeds repo memory, /plan emits the contract that /verify and /prereview check against, and /triage closes the loop from CI. Typed artifacts are how they hand off: stdin and stdout for agents, instead of one enormous prompt chain.
Read the full catalog, including the section on skills that were explicitly rejected and why.
#Install a skill from anywhere
Skills are folders in a git repo. There is no central index yet — sources are explicit, which is a feature while trust tooling is young.
| Source | Example |
|---|---|
| GitHub repo | kitbash install gh:owner/repo |
| Subfolder of a repo | kitbash install gh:owner/repo/skills/my-skill |
| Pinned to a ref | kitbash install gh:owner/repo@v1.2.0 |
| Shorthand | kitbash install owner/repo |
| Local path | kitbash install file:./my-skill |
Every install shows a review block first — permissions, network and write access, budget, and lint warnings — and asks before writing anything. Org-wide rules live in [policy].
#Already have skills?
A plain SKILL.md folder — the skills.sh and Claude Skills convention — installs directly. It is KSF without the manifest, so Kitbash applies conservative defaults and marks it unmanifested, because nobody declared a budget or permissions for it. You still get compilation to all nine targets, the lockfile, and the standing-cost warning.
kitbash install owner/repo
kitbash lint owner/repo # or lint it before installing#Publish your own
Write the skill, put it in a public repo, and anyone can install it by URL. There is no registry to submit to — kitbash search and kitbash publish are on the roadmap, not shipped, and a public index is not worth building until the trust primitives around it are proven.
Start with write your first skill, then run kitbash lint and kitbash test before you share it.