| name | repo-maintenance |
| description | Use when maintaining a local repository: checking status, triaging stale generated assets, refreshing indexes, running focused validation, or preparing a small reviewable maintenance change. |
| version | 1.0.0 |
| triggers | ["maintain this repo","refresh generated assets","triage repo health","prepare a maintenance change"] |
| negative_triggers | ["redesign the product","write marketing copy"] |
| allowed_tools | [] |
| required_tools | [] |
| trust_level | local |
| safety_class | standard |
| examples | ["Check repository health, identify stale assets, and propose a small maintenance diff."] |
| tests | ["sb skills validate --path skills --strict"] |
| performance | {"notes":"Best for scoped local maintenance with explicit verification commands."} |
Repository Maintenance
Purpose
Keep a local codebase healthy through small, auditable maintenance work.
Instructions
- Start with repository status and local contributor instructions.
- Identify the narrow maintenance target: generated assets, docs indexes, stale fixtures, dependency metadata, or validation failures.
- Read the source of truth before changing derived files.
- Keep changes mechanical and reviewable. Do not fold unrelated cleanup into the diff.
- Run the smallest command that proves the maintenance result.
- Report changed files, commands run, and any remaining manual follow-up.
Guardrails
- Never delete local state, caches, branches, or database files unless the user explicitly asks.
- Do not overwrite unrelated working-tree edits.
- Prefer offline-safe validation unless the task requires an external service.
