- Home
- Skills
- Code Quality & Review
- BuildBuddy
BuildBuddy
Evidence-based code review tool that identifies reachable runtime defects, security risks, and logic failures.
$1.90
Works with the AI Agents you already use
BuildBuddy
Example session with this skill installed
Review the src/ directory for evidence-backed security and logic defects. Only report confirmed bugs with realistic execution paths. Return JSON findings only.
- Read your context and instructions
- Compiled the buildbuddy
I have completed the scan of the /src directory. No style issues were recorded; findings are restricted to confirmed runtime and logic defects.
Findings Report
[
{
"bugId": "BUG-001",
"severity": "High",
"category": "security",
"file": "src/middleware/auth.ts",
"lines": "22-25",
"claim": "Insecure JWT signature validation.",
"description": "The middleware checks for the presence of a token but fails to verify the cryptographic signature against the secret key, allowing forged headers.",
"evidence": "src/middleware/auth.ts:24",
"runtimeTrigger": "POST /api/admin with 'Authorization: Bearer [unsigned_token]'",
"impact": "Full authentication bypass for administrative endpoints.",
"crossReferences": ["src/routes/admin.ts:12"],
"confidenceScore": 98,
"confidenceLabel": "high",
"classification": "confirmed-bug"
},
{
"bugId": "BUG-002",
"severity": "Medium",
"category": "logic",
"file": "src/services/payment.ts",
"lines": "104-110",
"claim": "Race condition in balance deduction.",
"description": "The balance check and update are not atomic, allowing multiple concurrent requests to overdraw the account.",
"evidence": "src/services/payment.ts:105",
"runtimeTrigger": "Simultaneous POST /pay requests from same user ID.",
"impact": "Account balance can drop below zero without restriction.",
"crossReferences": ["src/models/user.ts:45"],
"confidenceScore": 85,
"confidenceLabel": "medium",
"classification": "confirmed-bug"
}
]
Next steps
- Update
src/middleware/auth.tsto implementjwt.verify()with the environment secret. - Wrap the balance check and update in
src/services/payment.tswithin a database transaction or use atomic increments. - Run a targeted scan on
src/models/to check for similar state management issues.
Connects securely to your tools. The creator never sees your data.
About this skill
Code reviews often drown developers in noise, surface-level linting, and style nitpicks. This skill ignores aesthetics to hunt for actual runtime defects, security vulnerabilities, and logic failures backed by hard evidence.
What it does
- Defect discovery identifies runtime, logic, and data integrity bugs that actually break execution.
- Security auditing scans for authentication gaps, injection risks, and unauthorized data exposure.
- Boundary analysis inspects data flow across trust boundaries and service integrations.
- Evidence mapping provides specific trigger paths and line numbers for every reported issue.
- Contract verification checks for API and cross-file mismatches that cause production failures.
How it works
- Reconnaissance maps entry points, trust boundaries, and persistence layers to build a system model.
- Deep Review analyzes inputs, validation logic, and error propagation paths in high-risk files.
- Verification tests each potential finding against a zero-false-positive principle to confirm reachability.
- JSON Reporting outputs findings in a structured format including severity, CWE mapping, and confidence scores.
Frameworks & tools
This skill is language-agnostic and focuses on architectural patterns, state management, and execution logic. It is particularly effective for complex systems using REST/GraphQL APIs, distributed state, or sensitive data persistence.
Why this beats prompting it yourself
Generic prompts often hallucinate bugs or focus on const vs let style preferences. This skill enforces a strict non-destructive scan that rejects speculative findings, ensuring every report represents a reachable, observable defect with a concrete trigger path.
Use cases
- Auditing a pull request for high-impact security or concurrency defects before merge.
- Mapping trust boundaries in a legacy codebase to identify data leakage risks.
- Verifying cross-service API contracts and error handling gaps in distributed systems.
Known limitations
Does not report on code style, naming conventions, or missing tests. Findings are limited by context window capacity, and partial coverage is reported if the repo is too large.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Code Quality & Review.
Focuses solely on logic and security; ignores style, linting, and formatting. Limited by context window for large repos. Requires reachable execution paths to confirm bugs.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 27 days ago