Reviews staged or recent git diffs to find edge cases, logic errors, and integration risks before merging.
npx skills add https://github.com/arndvs/ctrlshft --skill code-review-arndvs
Please help me install this Agent Skill. Skill: code-review Source: https://github.com/arndvs/ctrlshft/tree/main/skills/code-review Command: npx skills add https://github.com/arndvs/ctrlshft --skill code-review-arndvs
git diff --staged. - Adversarial stress-testing: Walks the change through null inputs, wrong types, concurrency, ordering, scale, and error-path scenarios. - Blast-radius assessment: Selectively invokes an explore sub-agent when the diff touches shared utilities, type shapes, exported signatures, or shared state. - Prioritized findings: Reports results as Must Fix, Edge Cases, Integration Risks, and Nits, each with file:line references and concrete fixes. - Use Case: Before merging a feature branch, ask for a review of git diff main...HEAD and receive a TL;DR summary plus actionable findings, then hand off to test-writing or fixing workflows. ## Quick Start Ask the agent to review my staged changes before I merge this PR.High-intent search queries and answers about installing and using this skill.
Run the review on your staged changes, which the Skill retrieves with git diff --staged. It analyzes only the diff, stress-tests it against edge cases like null inputs and concurrency, and reports findings grouped by severity with file:line references.
Paste the PR description and diff into chat, or point the reviewer at a branch using git diff main...HEAD. The review covers logic errors, unhandled edge cases, and integration risks, ending with a summary and concrete suggested fixes.
It checks null and empty inputs, wrong types, concurrent calls, out-of-order execution, large-input degradation, error-path coverage, shared-state mutations, and broken caller contracts. Findings are classified as Must Fix, Edge Cases, Integration Risks, or Nits.
Exploration triggers only when the diff modifies shared utilities, changes type or schema shapes, alters exported signatures, or writes shared state in new ways. Purely additive changes or new files with no callers skip exploration to keep reviews fast.
It intentionally does not audit the full codebase, report style or formatting issues, or flag missing documentation. It also avoids theoretical risks requiring unlikely failure chains, focusing only on plausible production scenarios in the changed code.
theslashdojoIdentify and review exact changes across git states with unified diff output.
nntoanGuides test-first development using the RED-GREEN-REFACTOR cycle across any language or test framework.
ruskicoderAnalyze codebase structure, call flows, and change impact using the GitNexus knowledge graph.
kiminmonacoGuide TDD-based improvements to existing ClaudeBar functionality.