Install
$ agentstack add skill-danielvm-git-bigpowers-fix-bug ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Fix Bug
Boundary: Orchestrator flow — chains investigate-bug (entry point + RCA via diagnose-root) → develop-tdd → validate-fix. Does not implement RCA or write bug files directly.
Orchestrates fix_bug flow without mixing epic build state.
> HARD GATE — Set specs/state.yaml active_flow: fix_bug and bug_cycle.current_step: 1 before starting.
Five steps (bug_cycle in state.yaml)
| Step | Skill / action | |------|----------------| | 1 | investigate-bug — create BUG-*.md with RCA | | 2 | diagnose-root — 4-phase root cause analysis | | 3 | develop-tdd — red-green against bug file verify steps | | 4 | validate-fix — re-run failing test, full suite, lint | | 5 | release-branch — PR or solo land the fix |
Checkpoint / resume
Track progress via specs/state.yaml bug_cycle:
bug_cycle.current_step: current step (1–5)bug_cycle.completed_steps: completed step numbershandoff.next_skill: skill for the current step- On resume, read
bug_cycle.current_stepand continue from there
Process
- Step 1 — investigate-bug: If no
specs/bugs/BUG-*.md, runinvestigate-bugfirst — it handles history check, RCA (viadiagnose-root), fix approach, and writes the bug file. Incrementbug_cycle.current_stepto 2 on completion. - Step 2 — diagnose-root: Run 4-phase RCA (reproduce → isolate → hypothesize → verify). Record findings in the bug file. Increment to step 3.
- Step 3 — develop-tdd:
develop-tddagainst the bug file's verify steps. Increment to step 4 on all-green. - Step 4 — validate-fix:
validate-fix— re-run failing test, full suite, typecheck, lint. Increment to step 5. - Step 5 — release-branch: Land the fix via
release-branch. Clearbug_cycleandactive_flowwhen done.
Bug file SoT
One markdown file per bug with frontmatter:
bug_id: BUG-001
status: open
severity: high
scope: api
title: Short title
Verify
→ verify: test -d specs/bugs && bash scripts/sync-bugs-registry.sh
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: danielvm-git
- Source: danielvm-git/bigpowers
- License: MIT
- Homepage: https://github.com/danielvm-git/bigpowers
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.