Review TypeScript code changes against local coding standards with evidence-backed findings.
npx skills add https://github.com/dmmulroy/skills --skill code-review-dmmulroy
Please help me install this Agent Skill. Skill: code-review Source: https://github.com/dmmulroy/skills/tree/main/code-review Command: npx skills add https://github.com/dmmulroy/skills --skill code-review-dmmulroy
It helps you review code changes against local standards and catch correctness, boundary, safety, and test integrity issues before they ship.
Ask me to review the current code changes against the project standards and report only evidence-backed findings.
High-intent search queries and answers about installing and using this skill.
Review TypeScript code changes against project coding standards by loading relevant standards for the touched areas and reporting evidence-backed findings with concrete proof. This approach catches correctness, boundary, safety, and test integrity issues across branch diffs, staged changes, or pull requests.
Yes, you can analyze a branch diff for evidence-backed code issues by requiring concrete proof for every finding, including code location, value flow, or reproducible failures. This prevents generic style opinions and focuses on actual correctness, safety, and test integrity problems.
The best way to find correctness and test integrity issues in a pull request is applying a review-only workflow that loads local coding standards by topic and demands concrete proof. This identifies real defects in boundary conditions and test logic before shipping.
Yes, this code review approach works on staged and unstaged changes in TypeScript repositories. It applies standards-backed analysis to targeted file sets, commits, and branch diffs, requiring concrete evidence like code location or value flow for every reported issue.
Evidence-based code review requires loading standards by topic to ensure findings are backed by relevant local coding rules instead of generic style opinions. This targets the specific areas touched by a change and provides concrete proof for every reported safety, boundary, or correctness issue.
bcmcpherAutomate code review of git diffs to detect correctness issues and guideline violations.
nuurproAnalyze pull request diffs for SQL safety, LLM trust boundary violations, and side effects.
KimjimanAutomate build, static analysis, tests, security scans, and diff review for Spring Boot projects.
tillysosoIdentify high-confidence issues in local code changes and diffs.
