- Skills
- 36
- 仓库
- 1
- 职业覆盖
- 0
- 场景覆盖
- 0
- Stars
- ★ 2
Bang-isme 的 Skills 36
codex-test-driven-development
Fixture stub for TDD skill.
codex-subagent-execution
Fixture stub for subagent execution skill.
codex-runtime-hook
Fixture stub for runtime hook skill.
codex-plan-writer
Fixture stub for plan writer skill.
codex-execution-quality-gate
Fixture stub for quality gate skill.
codex-demo
Minimal fixture skill for Agency CLI skill-md parser tests.
codex-workflow-autopilot
Use after intent is known to route build, fix, review, debug, docs, or Scrum requests into ordered workflow steps with exit criteria.
codex-verification-discipline
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs — requires running verification commands and confirming output before making any success claims; evidence before assertions always
codex-test-driven-development
Use before feature, bugfix, or refactor implementation when behavior can be tested; enforces Red-Green-Refactor discipline.
codex-systematic-debugging
Use for bugs, test failures, broken behavior, or unexpected results; enforces 4-phase root-cause debugging before fixes.
codex-subagent-execution
Use when an approved plan has independent tasks ready for delegated execution with fresh subagents and two-stage review.
codex-spec-driven-development
Use for prototype, MVP, fullstack feature, from-scratch feature, or multi-domain work that needs a SPEC.md before planning or implementation. Do not use for tiny one-file edits.
codex-security-specialist
Use for security review, audit, hardening, compliance, DevSecOps, network, infrastructure, or application security with focused references.
codex-scrum-subagents
Use when work needs Scrum roles, ceremonies, backlog refinement, sprint planning, story delivery, release readiness, or role handoffs.
codex-runtime-hook
Use at the start of a Codex task to inspect repo readiness, project profile, monorepo shape, role docs, spec status, knowledge index, and recommend the next workflow.
codex-role-docs
Use for role-scoped FE/BE/DevOps/Admin/QA project docs under .codex/project-docs to preserve micro-context across long projects.
codex-reasoning-rigor
Use when work needs deeper thinking, less generic output, repo evidence, tradeoffs, monitoring signals, or stronger quality discipline.
codex-project-pulse
Use when asking project status, next priority, sprint health, blockers, deadlines, risk register, or daily brief generation.