Review code diffs for correctness, security, and regression risks.
npx skills add https://github.com/mathiasbourgoin/roster --skill reviewer-mathiasbourgoin
Please help me install this Agent Skill. Skill: reviewer Source: https://github.com/mathiasbourgoin/roster/tree/main/.agents/skills/reviewer Command: npx skills add https://github.com/mathiasbourgoin/roster --skill reviewer-mathiasbourgoin
Unstructured code reviews often miss critical correctness regressions, security vulnerabilities, and high-risk issues that lead to production bugs, security breaches, and costly technical debt.
Use the reviewer skill to perform a structured risk-oriented review of the latest code diff for the user authentication module, and return findings ordered by severity with an overall approve, changes required, or block recommendation.
High-intent search queries and answers about installing and using this skill.
A structured code review identifies correctness regressions and security vulnerabilities in code diffs by checking for language-specific antipatterns, missing tests, and maintainability risks. It delivers severity-ranked findings with concrete fix directions and an overall merge recommendation.
Reviewing a code diff for regression risks involves analyzing the changes for correctness issues, security abuse paths, and missing tests across all files in scope. The process outputs findings ordered by severity from critical to low to guide necessary fixes before merging.
Yes, automated risk-oriented code review covers all languages within the diff scope and explicitly checks for language-specific antipatterns. It validates all review dimensions and issues an approve, changes required, or block recommendation based on the findings.
To get actionable feedback, a code review must provide severity-ranked findings that include the exact location, risk explanation, and concrete fix direction for each issue. This eliminates vague feedback and clearly communicates what must be fixed.
You need a risk-oriented code review workflow after a developer completes a feature implementation but before merging. It acts as a post-implementation check for tech leads to catch high-risk issues, security vulnerabilities, and technical debt.
Yes, a structured code review explicitly checks for missing tests and maintainability risks alongside correctness regressions and security vulnerabilities. It validates all review dimensions across the entire diff scope before issuing a final recommendation.
rnbenAutomates pre-commit verification with security scans, baseline tests, and an auto-fix loop.
jpoleyValidate security patch quality and regression risk for code changes.
JHostalekCoordinate parallel worktree reviews across eleven audit dimensions for software scopes.
Codagent-AIResolve CI failures and review comments on GitHub pull requests.
