skills.rest
spike-land-ai
spike-land-aiOFFICIAL
Explore all skills by this author →
GitHub

find-bugs

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

Updated Aug 23, 2026
Search Tags:#code-quality#threat-modeling#static-analysis#bug-detection#security-review#attack-surface#diff-analysis
One-click install
npx skills add https://github.com/spike-land-ai/spike.land --skill find-bugs-spike-land-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: find-bugs
Source: https://github.com/spike-land-ai/spike.land/tree/main/.agents/skills/find-bugs
Command: npx skills add https://github.com/spike-land-ai/spike.land --skill find-bugs-spike-land-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams identify bugs, security vulnerabilities, and code quality issues in changes on a branch before merging, reducing risk and manual review time.

Core Features & Use Cases

  • Comprehensive diff analysis to capture all changes between branches and surface potential defects.
  • Systematic attack surface mapping for changed files, listing inputs, queries, auth checks, sessions, external calls, and cryptography.
  • A structured security checklist and verification process to guide code reviews and ensure consistent quality.
  • Use case: Apply during a pull request to surface critical security risks and quality gaps before merging.

Quick Start

Run this skill on a branch with changes to receive a structured security-focused review of the modified files.

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 in a pull request diff?▼

Static analysis of branch changes detects bugs and security gaps by mapping the attack surface of modified files, examining inputs, auth checks, and external calls against a structured security checklist.

How do I review code quality issues in a feature branch before merging?▼

Detecting bugs in branch changes requires analyzing the full diff to capture all modifications, mapping inputs and external calls, and verifying potential issues against a structured security checklist to ensure code quality.

What is attack surface mapping for changed files?▼

Attack surface mapping lists inputs, queries, auth checks, sessions, external calls, and cryptography for changed files to surface potential defects and guide security reviews during branch changes.

Can I use this for a code audit across multiple branches?▼

Yes, branch change analysis applies to code review scenarios such as pull requests, feature branches, or code audits by analyzing the full diff and applying a rigorous security checklist to verify potential issues.

What is the best way to run a security review on branch changes?▼

The best way to run a security review on branch changes is applying comprehensive diff analysis, systematic attack surface mapping, and a structured security checklist to verify potential issues in modified files.

Related Skills

Explore More Software Engineering Skills→
Fandry96Fandry96
27

find-bugs

Analyze code diffs to identify security vulnerabilities and produce structured findings.

Community
Advanced
SeifBenayedSeifBenayed
114

review-pr

Review pull request changes and report bugs, vulnerabilities, and merge verdicts.

Community
Intermediate
SaturateSaturate

security-deep-dive

Analyze software security to identify vulnerabilities and attack surfaces.

Community
Advanced
petrSimonidesXartpetrSimonidesXart

security-audit

Scan code, configurations, and deployments to generate vulnerability reports with remediation steps.

Community
Advanced