fix-bug
Fix Bugs With Structured Triage
Debugging across backend and frontend can lose context and miss regression tests. This skill guides root cause analysis, minimal fixes, validation, and pull request handoff.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "fix-bug" from https://skillstore.io/skills/crearize-fix-bug.md and its manifest at https://skillstore.io/api/skills/crearize-fix-bug/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 "fix-bug". A null user identifier causes a server error during profile lookup.
Expected outcome:
A root cause report, a minimal validation fix, focused regression tests, QA results, and a pull request summary.
Using "fix-bug". A frontend component logs an error after the user leaves the page.
Expected outcome:
An investigation summary, a lifecycle-safe state update fix, a component test, and verification notes.
Using "fix-bug". A release blocker affects both API behavior and screen rendering.
Expected outcome:
A coordinated backend and frontend fix plan with impact notes, test coverage, quality checks, and reviewer handoff.
Security Audit
SafeStatic findings were false positives caused by Markdown fences, inline path formatting, and safe grep examples. I found no actual backtick command execution, obfuscation, reconnaissance, prompt injection, or malicious intent. The visible local commands should still follow normal user-confirmation policies.
Risk Factors
⚙️ External commands (41)
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/crearize-fix-bug/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/crearize-fix-bug?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/crearize-fix-bug?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/crearize-fix-bug/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/crearize-fix-bug.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
Crearize. (2026). fix-bug security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/crearize-fix-bug/audits/8BibTeX citation
@techreport{crearize-crearize-fix-bug-2026,
author = {Crearize},
title = {fix-bug security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/crearize-fix-bug/audits/8},
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: "fix-bug security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "Crearize"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/crearize-fix-bug/audits/8"
identifiers:
- type: other
value: "skillstore:crearize-fix-bug:audit:8"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Backend regression fix
Trace a failing backend path, add missing validation, create regression tests, and prepare a concise pull request summary.
Frontend behavior bug
Investigate component behavior, isolate the UI cause, apply a small fix, and verify the problem no longer appears.
Release triage workflow
Coordinate bug investigation, quality checks, and handoff notes when a release issue needs a controlled fix.
Try These Prompts
Use fix-bug for this issue: [bug description]. Issue number: [number]. Target area: [backend, frontend, or both].
Use fix-bug with suspected files [file list]. Confirm the root cause before making the smallest safe change.
Use fix-bug to reproduce this bug, implement the fix, and add regression tests for the failing path and edge cases.
Use fix-bug end to end. Include root cause, impact, tests, QA results, review notes, and the pull request summary.
Best Practices
- Provide the bug description, target area, issue number, and any suspected files at the start.
- Ask for the root cause report before approving code changes in high-impact areas.
- Run regression tests and QA checks before creating the pull request summary.
Avoid
- Do not use it for unrelated refactoring during a small bug fix.
- Do not skip regression tests after a reproduction path is identified.
- Do not run project server commands without checking local environment requirements.