find-bugs

Analyze Git branch diffs for bugs, security vulnerabilities, and code quality issues.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/DITEKmax/rutcampustrack --skill find-bugs-ditekmax
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: find-bugs
Source: https://github.com/DITEKmax/rutcampustrack/tree/main/.agents/skills/find-bugs
Command: npx skills add https://github.com/DITEKmax/rutcampustrack --skill find-bugs-ditekmax

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured audit process to find bugs, security vulnerabilities, and code-quality regressions introduced on a Git branch by examining diffs, mapping attack surface, and verifying protections and tests.

Core Features & Use Cases

  • Diff-driven review: Obtain the full branch diff and inspect each changed file and changed line for issues.
  • Attack surface mapping: Identify user inputs, DB queries, auth checks, session/state operations, external calls, and cryptographic operations per file.
  • Security checklist and verification: Apply a per-file checklist (injection, XSS, CSRF, auth/authorization, race conditions, cryptography, DoS, information disclosure, business logic) and verify whether protections exist and tests cover scenarios.
  • Use Case: Run prior to merging a pull request or during a security audit to produce a prioritized, evidence-backed remediation plan.

Quick Start

Run the find-bugs skill to analyze the current branch diff and produce a prioritized security and bug report.

Frequently Asked Questions about find-bugs

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

FAQPage Schema
How do I find security vulnerabilities and bugs in a Git branch diff?▼

Audit a Git branch diff by inspecting changed files and lines to map the attack surface, verifying protections against a security checklist, and producing a prioritized list of findings with file:line locations and remediation suggestions.

What is attack surface mapping during a code review?▼

Attack surface mapping identifies user inputs, database queries, authentication checks, session operations, external calls, and cryptographic operations within changed files to verify protections and test coverage.

Can I use this for pre-merge checks on my pull request?▼

Yes, you can apply this to pre-merge checks on a pull request by analyzing the current branch diff, verifying test coverage, and generating an evidence-backed, prioritized remediation plan before merging.

What's the best way to audit code quality and regressions before merging?▼

Audit code quality regressions before merging by obtaining the full branch diff, inspecting each changed line, applying a per-file security checklist, and verifying that tests cover necessary scenarios.

What security issues are checked during a branch diff analysis?▼

A branch diff analysis applies a per-file checklist checking for injection, XSS, CSRF, authentication and authorization flaws, race conditions, cryptography issues, DoS, information disclosure, and business logic errors.