adr-writer
Use when capturing an architecture decision so it survives turnover — produces an ADR-NNNN.md from context, options considered,…
Use before opening a PR to audit the changes for stale comments, unused imports, missing tests, and inconsistencies with neighboring code.
$ npx -y skills add oxbshw/LLM-Agents-Ecosystem-Handbook --skill repo-auditor --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/repo-auditorContext preview
The summary Claude sees to decide when to auto-load this skill.
Use before opening a PR to audit the changes for stale comments, unused imports, missing tests, and inconsistencies with neighboring code.
name: repo-auditor description: Use before opening a PR to audit the changes for stale comments, unused imports, missing tests, and inconsistencies with neighboring code. version: 0.1.0
| Name | Type | Required | Notes | |---|---|---|---| | `base` | string | no | base ref (default `origin/main`) | | `paths` | list | no | restrict to specific paths |
1. **Diff**: `git diff <base>...HEAD --name-only` and `git diff <base>...HEAD` 2. **For each changed file**: load `references/audit-checklist.md` and walk it 3. **Check tests**: any new public function without a corresponding test → flag 4. **Check imports**: unused imports / missing imports → flag 5. **Check style fit**: does the new code match neighboring code's idioms? 6. **Check docs**: did this change require an `AGENTS.md` / `MEMORY.md` / README update? → flag if missed 7. **Produce report**: structured output (see Outputs)
## Audit report
- ✅ {{N}} files reviewed
- 🟡 {{N}} warnings
- 🔴 {{N}} blockers
### Blockers
- {{file:line}} — {{issue}}
### Warnings
- {{file:line}} — {{issue}}A practical operating manual for building, evaluating, securing, and shipping modern LLM agent systems. Modern agents are not "a prompt + a tool."
Use when capturing an architecture decision so it survives turnover — produces an ADR-NNNN.md from context, options considered,…
Use when reviewing a proposed REST or GraphQL API change before merge — checks contract clarity, backwards compatibility, errors,…
Use when first encountering a new dataset — produces a structured profile (schema, missingness, distributions, outliers, gotchas)…
Use after an incident is resolved — drafts a blameless postmortem from timeline notes, alerts, and chat threads.
Use when opening a PR — produces a clean PR description (what / why / how to verify / risks) from a branch diff against base.
Use when planning the next sprint — turns ticket intake + team capacity into a planned sprint with explicit non-goals.