find-bugs
Find Bugs and Security Risks in Branch Changes
Incomplete code reviews can miss exploitable flaws and behavior regressions. This skill examines the full branch diff, verifies each issue, and reports prioritized fixes.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "find-bugs" from https://skillstore.io/skills/davila7-find-bugs.md and its manifest at https://skillstore.io/api/skills/davila7-find-bugs/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "find-bugs". Review this branch for significant bugs and security vulnerabilities.
Expected outcome:
- High severity: An order update verifies login but does not verify resource ownership.
- Evidence: The caller can provide another account's order identifier, and no later ownership check exists.
- Fix: Scope the lookup to the authenticated account and add a cross-account access test.
Using "find-bugs". Audit the changes for race conditions and business logic errors.
Expected outcome:
- Medium severity: Two concurrent requests can consume the same remaining quota.
- Evidence: The quota is checked before a separate update, without an atomic condition.
- Fix: Use one conditional update and test simultaneous requests.
Using "find-bugs". Report only verified issues and disclose any review gaps.
Expected outcome:
No significant verified issues were found. Runtime behavior remains unverified because the required integration environment was unavailable.
Security Audit
SafeThe single static finding is a false positive caused by Markdown inline-code formatting around a fixed Git diff command. The command is read-only and contains no user-controlled interpolation. No prompt injection, exfiltration intent, or other semantic security issue was found.
Risk Factors
⚙️ External commands (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/davila7-find-bugs/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/davila7-find-bugs?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/davila7-find-bugs?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/davila7-find-bugs/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/davila7-find-bugs.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
davila7. (2026). find-bugs security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/davila7-find-bugs/audits/9BibTeX citation
@techreport{davila7-davila7-find-bugs-2026,
author = {davila7},
title = {find-bugs security audit report (audit version 9)},
institution = {Skillstore},
year = {2026},
number = {9},
url = {https://skillstore.io/skills/davila7-find-bugs/audits/9},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "find-bugs security audit report (audit version 9)"
version: "unspecified"
type: report
authors:
- name: "davila7"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/davila7-find-bugs/audits/9"
identifiers:
- type: other
value: "skillstore:davila7-find-bugs:audit:9"
description: "Skillstore immutable audit report identifier"
Compare variants
3 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
sickn33-find-bugs
2026-08-21
getsentry-find-bugs
2026-08-21
davila7-find-bugs
2026-08-21
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Review a Feature Branch
Inspect proposed changes for regressions, security flaws, and missing tests before opening a pull request.
Audit Sensitive Changes
Examine authentication, authorization, sessions, external calls, and data handling for exploitable weaknesses.
Assess a Release Candidate
Identify significant branch risks, verify evidence, and prioritize fixes before a release decision.
Try These Prompts
Review the current branch against master. Find significant bugs and security vulnerabilities, verify each finding, and skip style-only comments.
Audit the current branch for injection, access control, session, cryptography, disclosure, denial-of-service, and business logic risks. Provide evidence and fixes.
Review every changed authorization and state transition. Check ownership, role boundaries, race conditions, invalid transitions, and test coverage before reporting findings.
Read every changed file completely, map the attack surface, apply the full checklist, verify each issue in context, and disclose unresolved review gaps.
Best Practices
- Provide the intended base branch when it is not master.
- Make all changed files and relevant tests available for complete verification.
- Share expected behavior for business rules that code alone cannot establish.
Avoid
- Do not request style-only feedback when the goal is risk discovery.
- Do not treat an unverified suspicion as a confirmed vulnerability.
- Do not use the review as a substitute for tests or runtime security controls.