maintenance-orchestration
Technical debt management including branch cleanup, doc verification, TODO scanning, and dependency auditing
npx skills add a5c-ai/babysitter --skill maintenance-orchestration --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Maintenance Orchestration ## Capabilities Orchestrates comprehensive technical debt management. Performs branch cleanup, knowledge graph synchronization, documentation verification, TODO/FIXME scanning, test coverage analysis, and dependency auditing. ## Tool Use Instructions - Use **Bash** to run git commands for branch analysis and cleanup - Use **Grep** to scan for TODO, FIXME, HACK, WORKAROUND markers - Use **Glob** to find documentation files for verification - Use **Read** to examine docs and configuration files - Use **Write** to generate maintenance reports ## Process Integration - Used in `maestro-maintenance.js` (All maintenance operations) - Agent: Maintenance Engineer - Triggered after every N specifications (configurable via `maintenanceFrequency`) - Focus areas configurable: branches, knowledge, docs, todos, coverage, dependencies - Generates health score and remediation recommendations
- Capabilities
- Tool Use Instructions
- Process Integration
What does the maintenance-orchestration skill do?
Technical debt management including branch cleanup, doc verification, TODO scanning, and dependency auditing
How do I install it?
Run `npx skills add a5c-ai/babysitter --skill maintenance-orchestration --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From a5c-ai/babysitter, a repository with 1,642 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.