Open source maintainer automation skills for Claude Code. Full pipeline from morning issue flood to clean repo. Skills: /triage, /review-prs, /mstack-release, /health, /respond, /maintain (orchestrator), /mstack-setup.
Generate a repo health report: stale issues, PR status, CI health, dependency alerts, and community metrics. Writes a dated report to .mstack/reports/ and presents a summary with prioritized action items. Use when asked for "repo health", "project status", "health check", "stale issues", or "check the repo".
Full maintenance pipeline orchestrator: triage → PR review → response drafting → health check. Chains all MStack skills with human checkpoints between each phase. Use when asked to "run maintenance", "morning maintenance", "full pipeline", "process everything", or "run all skills".
Release automation: analyze merged PRs since the last tag, generate a changelog entry, determine the version bump, create a git tag, and publish a GitHub release. Human approves every destructive action. Use when asked to "ship a release", "cut a release", "create a release", "bump the version", or "publish a new version".
Draft tone-matched maintainer responses for open issues and pull requests. Uses project response templates, learns the maintainer's voice from recent comments, and requires human approval before posting anything. Use when asked to "respond to issues", "draft replies", "handle issue responses", "write PR responses", or "respond to contributors".
Pre-screen open pull requests: diff analysis, security scan, test coverage, breaking change detection, bot detection. Human approves all review comments. Use when asked to "review PRs", "check pull requests", "screen PRs", or "pre-review open PRs".
Configure MStack for the current repository. Scans repo conventions, creates .mstack/config.yml. Use when asked to "setup mstack", "configure mstack", or when any skill finds REPO_CONFIGURED: false.
Triage open issues: categorize, detect duplicates, flag bots/spam, suggest labels and responses. Human approves every action. Use when asked to "triage issues", "process issues", "label issues", or "handle the issue backlog".