Verify code fixes against prior feedback and git diff HEAD~1.
npx skills add https://github.com/apokamo/kaji --skill issue-verify-code
Please help me install this Agent Skill. Skill: issue-verify-code Source: https://github.com/apokamo/kaji/tree/main/.claude/skills/issue-verify-code Command: npx skills add https://github.com/apokamo/kaji --skill issue-verify-code
This skill verifies that code fixes have been properly applied and that no new issues were introduced, supporting reliable review convergence.
Run the verify-code step after applying fixes to confirm that all previous issues are resolved and no new regressions were introduced.
High-intent search queries and answers about installing and using this skill.
To verify code fixes without introducing new issues, run a verify-code step after applying fixes to confirm previous review feedback is resolved and no regressions exist. It performs a git diff against HEAD~1 and emits a standardized Approve or Changes Requested verdict.
The best way to check if a code fix introduced regressions is to perform a baseline check against previous review feedback and a git diff against HEAD~1. This detects unintended changes and emits a Changes Requested verdict if new issues are found.
Git diff verification against HEAD~1 for issue tracking works by comparing the latest commit to its predecessor to detect unintended changes. It retrieves prior feedback, confirms fixes address stated issues, and outputs a standardized verdict for review convergence.
Yes, you can use automated code review verification in CI workflows to confirm fix convergence. The verification process checks applied fixes against prior feedback and git diffs, outputting a standardized Approve or Changes Requested verdict suitable for CI-based checks.
You need to run a baseline check during the code review workflow after the implement and fix-code stages, right before verify-code. It ensures applied fixes properly address previous review feedback and confirms no new issues were introduced before final approval.
Code review verification may still request changes after fixes are applied if the git diff against HEAD~1 detects unintended changes or the baseline check finds previous review feedback unresolved. The system emits a Changes Requested verdict until all issues converge.
erfanzarAutomate pre-commit code review with static checks, linting, and auto-fixes.
phillip-hirschCategorize issues and manage workflow states in software project trackers.
Sridhar-RanganaboinaReview code diffs and design docs to generate structured feedback and a commit.
matteocervelliRun rustfmt, clippy, cargo check, test, and audit for Rust quality gates.
