routine-maintenance

Inspect codebases and generate categorized findings reports with historical debt context.

2|1|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/msieurthenardier/mission-control --skill routine-maintenance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: routine-maintenance
Source: https://github.com/msieurthenardier/mission-control/tree/main/.claude/skills/routine-maintenance
Command: npx skills add https://github.com/msieurthenardier/mission-control --skill routine-maintenance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Routine Maintenance addresses the risk of hidden decay in a codebase by performing an aviation-style health inspection after missions or on-demand, ensuring issues are surfaced, prioritized, and tracked across cycles.

Core Features & Use Cases

  • Exhaustive aviation-style codebase inspection that identifies structural issues, debt, and opportunities for improvement.
  • Generates a findings report with categorized issues and recommended actions.
  • Optional scaffolding of a maintenance mission (flights and legs) to resolve prioritized findings.
  • Integrates prior debriefs and artifact configurations to distinguish new issues from previously acknowledged debt.
  • Useful after completing a mission to validate the codebase and inform the next maintenance cycle.

Quick Start

Trigger the maintenance workflow after a mission or on-demand to generate a findings report and optionally scaffold a maintenance mission.

Frequently Asked Questions about routine-maintenance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit my codebase for technical debt and hidden structural issues?

Codebase audits identify structural issues and technical debt by combining automated checks with historical maintenance records. This process surfaces and prioritizes hidden decay to ensure software quality and risk management across project cycles.

What is the best way to track technical debt across multiple software maintenance cycles?

Tracking technical debt across maintenance cycles is done by loading prior debriefs and artifact configurations. This distinguishes new findings from previously acknowledged debt, ensuring structured and continuous risk management for your codebase.

How do I automate codebase health inspections after completing a development mission?

Automated codebase health inspections run on-demand or after a mission to validate software quality. The process generates a categorized findings report with recommended actions and optionally scaffolds a maintenance mission to resolve prioritized issues.

Does routine maintenance require prior debriefs to identify new codebase risks?

Prior debriefs are not strictly required but are integrated to distinguish new findings from known debt. Loading artifact configurations and mission history ensures the maintenance assessment accurately differentishes new risks from previously acknowledged issues.

Can I scope and delegate codebase maintenance tasks for a structured software quality assessment?

Codebase maintenance tasks can be scoped and delegated through a structured assessment process. The workflow includes scoping, delegation planning, specialist reviews, and a final maintenance report to systematically address identified codebase health issues.

What are the limitations of using aviation-style maintenance cycles for software quality audits?

Aviation-style maintenance cycles rely on loading artifact configurations and mission history to function effectively. The assessment is limited by the availability of prior debriefs, meaning untracked or unconfigured project artifacts may not be fully evaluated.