Detect functional bugs in source code files with line numbers and proposed fixes.
npx skills add https://github.com/valorisa/Claude-Skills --skill find-bugs-valorisa
Please help me install this Agent Skill. Skill: Find Bugs Source: https://github.com/valorisa/Claude-Skills/tree/main/skills/find-bugs Command: npx skills add https://github.com/valorisa/Claude-Skills --skill find-bugs-valorisa
Most code review tools mix critical bugs with style issues, performance suggestions, and warnings, making it hard to prioritize urgent defects that cause incorrect behavior. This Skill eliminates the noise by focusing exclusively on real, impactful bugs in a single target file, with no irrelevant clutter.
Ask Claude to find bugs in your target source file, review the full list of proposed fixes, and confirm which corrections you want to apply.
High-intent search queries and answers about installing and using this skill.
To find functional bugs in a source file before a pull request, use single-file static analysis to detect unhandled null values, race conditions, and security vulnerabilities. This process returns a numbered bug list with line numbers, impact assessments, and proposed code fixes requiring explicit user confirmation before modifying files.
Detecting race conditions and security vulnerabilities during code review is best achieved through focused single-file bug detection. This approach isolates high-priority defect categories like unhandled null values and resource leaks, eliminating style warnings to provide actionable fix proposals with clear impact assessments.
Yes, you can get ready-to-apply code fixes for unhandled null values and resource leaks. The single-file bug detection process analyzes target source code and returns proposed corrections with affected line numbers and impact assessments, requiring your explicit confirmation before applying modifications.
Yes, single-file bug detection works for debugging unexpected production behavior by analyzing the misbehaving source file. It identifies high-priority functional bugs causing incorrect runtime behavior across seven categories, including logical errors and race conditions, and provides actionable code fixes to resolve issues.
The limitation of single-file static analysis for bug detection is that it analyzes one source file at a time, meaning it cannot detect cross-file dependency issues or project-wide architectural flaws. It focuses exclusively on seven high-priority bug categories within the target file, omitting style issues and performance suggestions.
AidenSbVevoRun parallelized Semgrep static analysis and merge SARIF results.
MesteriisApply targeted patches to fix a single security vulnerability.
ajsai47Analyze git diffs for SQL injection, race conditions, and shell injection risks.
timbuchingerAnalyze large codebases exceeding context limits using Gemini CLI.
