klh-find-bugs

Review local branch changes for bugs, security vulnerabilities, and code quality issues.

1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/klh/skills --skill klh-find-bugs-klh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: klh-find-bugs
Source: https://github.com/klh/skills/tree/main/.well-known/agent-skills/klh-find-bugs
Command: npx skills add https://github.com/klh/skills --skill klh-find-bugs-klh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing branch changes for bugs and security vulnerabilities is error-prone when done ad hoc, and reviewers often miss injection flaws, authorization gaps, or race conditions hidden in diffs. ## Core Features & Use Cases - Structured Five-Phase Review: Gathers the full branch diff, maps attack surfaces, runs an 11-point security checklist, verifies findings, and audits completeness before concluding. - Five Failure Modes Check: Explicitly screens for hallucinated actions, scope creep, cascading errors, context loss, and tool misuse in changed code. - Prioritized Reporting: Outputs findings ranked by severity (security > bugs > quality) with file, line, evidence, and concrete fix suggestions. - Use Case: Before merging a feature branch, ask for a security review and receive a complete audit of every changed file against OWASP-style categories without modifying any code. ## Quick Start Review the changes on this branch for bugs, security vulnerabilities, and code quality issues.

Frequently Asked Questions about klh-find-bugs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review branch changes for security vulnerabilities?

Run a structured review that gathers the full diff against the default branch, maps attack surfaces like user inputs and database queries, then checks each file against an eleven-item security checklist covering injection, XSS, auth, CSRF, and more.

How to find bugs in a git diff before merging?

Get the complete diff with git diff against the default branch, read every changed file fully, and verify each potential issue against surrounding context and existing tests before reporting it as a real finding.

What security issues should a code review checklist cover?

A thorough checklist covers injection, XSS, authentication, authorization/IDOR, CSRF, race conditions, session handling, cryptography, information disclosure, denial of service, and business logic edge cases for every changed file.

Does this review modify my code automatically?

No, the review only reports findings with severity, evidence, and fix suggestions. It explicitly does not make changes, leaving you to decide which issues to address.

What are the five failure modes in AI code review?

They are hallucinated actions, scope creep, cascading errors, context loss, and tool misuse. Each review explicitly checks whether there is evidence any of these occurred in the changed code.