Evaluate pull requests for merge viability across scope, conventions, and maintenance burden.
npx skills add https://github.com/joshft/correctless --skill cmaintain
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
Before executing, you should determine whether a contribution should be merged by evaluating scope, conventions, and maintenance burden, rather than judging code quality alone.
Invoke with: /cmaintain {PR number} to generate a maintainer review.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
benthamiteAudit GitHub Pull Requests with build, test, commit, and diff checks.
pydanticResolve unresolved GitHub pull request review comments on the current branch.
icartshAnalyze .NET solutions for code quality, security, and dependency issues.
ajsai47Analyze git diffs for SQL injection, race conditions, and shell injection risks.
