Is systematic-debugging safe?
Grade A, 94/100. No meaningful risk found.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Asystematic-debugging
skills/systematic-debugging94/100 · No meaningful risk found1 medium
systematic-debugging
skills/systematic-debuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes
- Content hash
- sha256:fa3fac4e35376230eb41c5504722b8309e2428e26932c90482dd313cb3dd34ef
- Files
- 11
- Quality
- 100/100
Security findings
- mediumDumps environment variablesSL202 · skills/systematic-debugging/SKILL.md:95
printenv IDENTITY >/dev/null 2>&1 && echo "IDENTITY in environment" || echo "IDENTITY not in environment"The skill collects every environment variable, which usually includes API keys and tokens. Fix: Read only the specific variable you need, by name.
Files in this skill
- CREATION-LOG.md4.2 KB
- SKILL.md9.3 KB
- condition-based-waiting-example.ts4.9 KB
- condition-based-waiting.md3.4 KB
- defense-in-depth.md3.6 KB
- find-polluter.sh1.9 KB
- root-cause-tracing.md5.2 KB
- test-academic.md653 B
- test-pressure-1.md1.9 KB
- test-pressure-2.md2.2 KB
- test-pressure-3.md2.6 KB
Questions about systematic-debugging
- Is systematic-debugging safe to install?
- Our scanner gave systematic-debugging grade A (94/100): no meaningful risk found. It matched 1 rule(s); review them below before installing. Static analysis cannot prove safety, so pin the reviewed revision with a lockfile.
- How do I install systematic-debugging in Claude Code or Codex?
- Run skillhash add github:obra/superpowers/skills/systematic-debugging. It downloads the exact commit, checks the grade against your policy, writes skills.lock and installs it into .claude/skills and .agents/skills.
- What happens if systematic-debugging changes upstream?
- Its content hash changes. skillhash verify fails in CI until you review the new version and update the lock. With a watch, you also get an alert.
More from obra/superpowers
- A
writing-skills
302kobra/superpowers
Use when creating new skills, editing existing skills, or verifying skills work before deployment
No security findings - A
requesting-code-review
302kobra/superpowers
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
No security findings - A
diagnosing-superpowers
302kobra/superpowers
Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.
No security findings - A
dispatching-parallel-agents
302kobra/superpowers
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
No security findings - A
executing-plans
302kobra/superpowers
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
No security findings - A
finishing-a-development-branch
302kobra/superpowers
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
No security findings - A
receiving-code-review
302kobra/superpowers
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
No security findings - A
subagent-driven-development
302kobra/superpowers
Use when executing implementation plans with independent tasks in the current session
No security findings