find-bugs

Identify security vulnerabilities and code quality issues in local git branch diffs.

Updated Dec 29, 2025
One-click install
npx skills add https://github.com/AmidVoshakul/chatorai --skill find-bugs-amidvoshakul
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: find-bugs
Source: https://github.com/AmidVoshakul/chatorai/tree/main/assets/skills/find-bugs
Command: npx skills add https://github.com/AmidVoshakul/chatorai --skill find-bugs-amidvoshakul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of identifying security vulnerabilities and logic bugs in code changes before they are merged, ensuring higher software reliability.

Core Features & Use Cases

  • Security Checklist: Systematically evaluates code against common threats like injection, XSS, and authorization flaws.
  • Diff-based Auditing: Focuses specifically on the changes within a branch to minimize noise and maximize relevance.
  • Use Case: Use this during a pull request review to ensure that new features do not introduce critical security regressions or logic errors.

Quick Start

Invoke the find-bugs skill to perform a comprehensive security audit on the current branch changes.

Frequently Asked Questions about find-bugs

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

FAQPage Schema
How do I audit git branch diffs for security vulnerabilities?

Security auditing of git branch diffs involves systematically evaluating code changes against common threats like injection, XSS, and authorization flaws before merging. This minimizes noise by focusing only on pending changes within the branch.

What is the best way to automate code review for logic bugs in pull requests?

Automating code review for logic bugs in pull requests is best achieved by analyzing local git branch differences to identify security vulnerabilities and logic errors. This ensures new features do not introduce critical security regressions before merging.

Do I need GitHub CLI to perform diff-based security auditing on local branches?

Yes, you need GitHub CLI and git command-line tools to perform diff-based security auditing on local branches. These tools are required to analyze branch differences and verify code integrity during the review process.

Can I check my code changes for XSS and injection flaws before merging a branch?

You can check code changes for XSS and injection flaws before merging by applying a security checklist to the branch diff. This proactive auditing method evaluates pending changes against common security threats to ensure software reliability.

What are the limitations of using git diffs for code quality auditing?

A limitation of using git diffs for code quality auditing is that it focuses specifically on changes within a branch, meaning it does not evaluate the entire codebase history, only pending modifications in the current local branch context.