cmaintain

Name: cmaintain
Availability: InStock
Author: josh

Evaluate pull requests for merge viability across scope, conventions, and maintenance burden.

65|2|Updated Mar 27, 2026

Search Tags:#security #maintenance #conventions #risk-assessment #code-review #pull-request #maintainer-review

Ready to run

npx skills add https://github.com/joshft/correctless --skill cmaintain

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cmaintain
Source: https://github.com/joshft/correctless/tree/main/correctless/skills/cmaintain
Command: npx skills add https://github.com/joshft/correctless --skill cmaintain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Before executing, you should determine whether a contribution should be merged by evaluating scope, conventions, and maintenance burden, rather than judging code quality alone.

Core Features & Use Cases

Structured PR review process: evaluates standards, scope, conventions, quality, maintenance burden, and security to decide merge viability.
Context-aware assessment: uses PR context, linked issues, contributor history, and code diff to inform the decision.
Generated maintainer review: outputs a clear recommendation and suggested comments for PR discussion.

Quick Start

Invoke with: /cmaintain {PR number} to generate a maintainer review.

Frequently Asked Questions about cmaintain

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

FAQPage Schema

How do I assess maintenance burden and conventions for a pull request before merging?▼

To assess maintenance burden and conventions, a structured code review evaluates scope, convention compliance, quality, security, and contributor context to determine merge viability. This prevents approving changes that introduce long-term technical debt.

What should a maintainer review check before approving a PR?▼

A maintainer review should check standards compliance, scope alignment, quality, maintenance burden, and security risks. Analyzing linked issues and contributor history alongside the code diff provides a complete assessment to decide merge viability.

Does maintainer review work with contributor context and linked issues?▼

Yes, context-aware assessment uses linked issues, contributor history, and code diffs to inform the merge decision. Evaluating this context ensures the pull request aligns with project conventions and minimizes maintenance burden.

When should I use an automated risk assessment for a pull request?▼

Use an automated risk assessment when you need to evaluate scope, convention compliance, and security before merging. It provides a step-by-step check process to ensure the PR does not introduce excessive maintenance burden or vulnerabilities.

Why does code quality alone not determine if a PR should be merged?▼

Code quality alone does not determine if a PR should be merged because maintenance burden, scope alignment, and convention compliance also dictate long-term project health. A structured review evaluates all these factors to generate a reliable merge recommendation.