maintenance-orchestration
Scannednpx machina-cli add skill a5c-ai/babysitter/maintenance-orchestration --openclawMaintenance 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
Source
git clone https://github.com/a5c-ai/babysitter/blob/main/plugins/babysitter/skills/babysit/process/methodologies/maestro/skills/maintenance-orchestration/SKILL.mdView on GitHub Overview
Maintenance Orchestration coordinates technical debt cleanup across branches, docs, tests, and dependencies. It combines branch cleanup, knowledge graph synchronization, doc verification, and TODO/FIXME scanning with dependency auditing to keep codebases healthy. The process generates a health score and actionable remediation recommendations.
How This Skill Works
It uses Bash to run git commands for branch analysis and cleanup, Grep to surface markers such as TODO and FIXME, and Glob to locate documentation files for verification. Read inspects docs and configuration files, while Write generates comprehensive maintenance reports. All steps integrate into maestro-maintenance.js to produce a health score and remediation recommendations.
When to Use It
- Before a release to verify branch cleanup, docs, and test coverage
- During documentation verification to ensure accuracy and configuration alignment
- While scanning for TODO, FIXME, HACK, and WORKAROUND markers to surface debt
- When auditing dependencies and test coverage to improve reliability
- After sprint cycles to refresh the knowledge graph and remediation plan
Quick Start
- Step 1: Run maestro-maintenance.js with a configured maintenanceFrequency to start the cycle
- Step 2: Use Bash to analyze branches and cleanup stale ones; use Grep to find markers
- Step 3: Review the generated report and health score, then implement remediation
Best Practices
- Use Bash for branch analysis and cleanup commands
- Run Grep to consistently scan for TODO, FIXME, HACK, and WORKAROUND markers
- Use Glob to locate documentation files for verification
- Read documentation and config files to validate correctness before applying changes
- Write clear maintenance reports with an explicit health score and remediation recommendations
Example Use Cases
- Clean up stale branches after a milestone and sync the knowledge graph
- Verify documentation against current configuration and generate a doc verification report
- Scan codebase for TODO/FIXME markers to surface unresolved tasks
- Audit dependencies and assess test coverage to improve reliability
- Produce a remediation plan after a maintenance run and track progress
