ShaheerKhawaja/productionos-debug
codex-skills/productionos-debug/SKILL.md
Systematic debugging with hypothesis tracking — reproduce, hypothesize, test, narrow, fix. Never guess-and-check.
$ install --global
skillsauthnpx skillsauth add ShaheerKhawaja/ProductionOS productionos-debugInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 23, 2026, 2:09 AM33.3s1 file scanned
SKILL.md
- name:
- productionos-debug
- description:
- Systematic debugging with hypothesis tracking — reproduce, hypothesize, test, narrow, fix. Never guess-and-check.
- argument-hint:
- [bug, failing behavior, or repro path]
productionos-debug
Use this alias when you want the same workflow through a top-level Codex-safe name without the productionos: namespace.
Overview
Use this as the Codex-first debugging workflow. It should reproduce the problem, gather evidence, rank hypotheses, test them one by one, and only fix the bug once the root cause is actually identified.
Source references:
.claude/commands/debug.mdagents/self-healer.mdagents/test-architect.md
Inputs
- required bug description or failing behavior
- optional reproduction command or failing test
- optional
max_hypotheses
Codex Workflow
- Reproduce the issue first.
- if you cannot reproduce it, say so and stop
- Gather evidence.
- recent changes
- logs
- failing commands or tests
- Generate ranked, testable hypotheses.
- Test the hypotheses in order.
- Once the root cause is confirmed:
- make the smallest effective fix
- re-run the original reproduction
- add or update a regression test
Expected Output
- confirmed reproduction
- ranked hypotheses with evidence
- identified root cause
- targeted fix
- regression-proof verification
Guardrails
- never guess-and-check blindly
- never claim a fix before reproducing and re-testing
- do not confuse symptom suppression with root-cause repair
Related Skills
ShaheerKhawaja/writing-plans
tools
VerifiedTrustedCommunity
Implementation planning workflow that turns approved ideas into dependency-aware execution plans.
7SKILL.mdUpdated Apr 23, 2026
ShaheerKhawaja/wiki-rag
development
VerifiedTrustedCommunity
Local RAG and Graph RAG over the SecondBrain wiki vault. Progressive context loading (hot cache -> index -> domain -> entity). Graph traversal via wikilink resolution. Use when agents need cross-project context, when answering questions that span multiple domains, or when building context for planning tasks. Triggers on: "wiki context", "cross-project context", "what do we know about", "check the wiki", "graph context", "/wiki-rag".
7SKILL.mdUpdated Apr 23, 2026
ShaheerKhawaja/ux-genie
devops
VerifiedTrustedCommunity
UX improvement pipeline — creates user stories from UI guidelines, maps user journeys, identifies friction, dispatches fix agents. The user-experience equivalent of /production-upgrade.
7SKILL.mdUpdated Apr 23, 2026
ShaheerKhawaja/tdd
development
VerifiedTrustedCommunity
Test-driven development workflow that writes failing tests first, implements minimally, and refactors safely.
7SKILL.mdUpdated Apr 23, 2026