-
Notifications
You must be signed in to change notification settings - Fork 0
Commands Reference
/helix [phase]
Without arguments — shows the interactive phase menu.
With a phase name — invokes that skill directly.
Opens the interactive phase selection menu.
Runs the complete workflow from start to finish:
Step 0: intake → Step 1: repo check → Step 2: analyze →
Step 3: plan → Step 4: execute → Step 5: test →
Step 6: deploy → Step 7: finalize
Asks for the repo and feature description before starting. Each phase waits for user confirmation before proceeding to the next.
Requirements breakdown and risk analysis.
Produces:
- 5-dimension requirement breakdown (Functional / Non-functional / Technical / Constraints / Out-of-scope)
- Risk table with Severity, Probability, Impact, Mitigation, Cost columns
Asks: repo location + what to build
Example output:
Requirement Breakdown — Payment Integration
Functional: process card payments, send confirmation email, update order status
Non-functional: p95 < 200ms, 99.9% uptime, PCI-DSS compliant
Out of scope: refunds, subscription billing
Risk Register:
| Risk | Severity | Probability | Score | Mitigation |
|-----------------------|----------|-------------|-------|--------------------|
| Payment provider down | High (4) | Low (2) | 8 | Circuit breaker |
| Hardcoded API keys | High (4) | Medium (3) | 12 | secrets management |
Creates a structured development plan using the team's MD template.
Produces: a Markdown plan file with 5 phases (Setup, Development, Testing, Review, Deployment) + Risk Register + Cost Analysis
Process: 3-round internal review before presenting to user — Completeness → Technical soundness → Risk & cost
Requires: user approval + path to commit plan before continuing
Implements the approved plan.
Behaviors:
- Asks which phase to start from
- Creates a feature branch automatically
- Reports progress every 10 minutes as a table
- Runs a mandatory 3-round bug-fix loop after implementation (Logic → Integration → Security)
Will not proceed to tests without completing the bug-fix loop.
Opens the test type selection menu. Test types follow ISO/IEC 25010 (SQuaRE) classification — run Tier 1 first.
Tier 1 — Functional Testing (ISO 25010: Functional Suitability — what the system does)
| Command | Type | Wiki |
|---|---|---|
/helix test-unit |
Unit tests (Jest / Vitest / pytest / Go test) | Test-Unit |
/helix test-integration |
Integration tests — real DB, auth flows | Test-Integration |
/helix test-contract |
API contract tests (Pact) | Test-Contract |
/helix test-e2e |
E2E via Playwright — full browser flows | Test-E2E |
Tier 2 — Non-Functional Quality Testing (ISO 25010: Security + Usability — run after Tier 1 passes)
| Command | Type | Wiki |
|---|---|---|
/helix test-security |
OWASP Top 10 + static analysis + CVE scan | Test-Security |
/helix test-a11y |
Accessibility — WCAG 2.1 AA via axe-core | Test-A11y |
/helix test-visual |
Visual regression via Playwright snapshots | Test-Visual |
Tier 3 — Non-Functional Performance Testing (ISO 25010: Performance Efficiency — requires running environment)
| Command | Type | Wiki |
|---|---|---|
/helix test-perf |
Performance orchestrator — routes to sub-type | Test-Perf-Overview |
/helix test-perf-load |
Load test — p95/p99 at expected concurrent users | Test-Perf-Load |
/helix test-perf-stress |
Stress test — find breaking point + verify recovery | Test-Perf-Stress |
/helix test-perf-soak |
Soak test — detect memory/connection leaks (30–60 min) | Test-Perf-Soak |
/helix test-perf-frontend |
Core Web Vitals (LCP, CLS, INP) + bundle size | Test-Perf-Frontend |
/helix test-perf-db |
Slow queries, missing indexes, N+1 patterns | Test-Perf-DB |
/helix test-perf-profile |
CPU flamegraph + heap snapshot | Test-Perf-Profile |
Each sub-command checks the repo's existing test structure and adds to it rather than replacing it.
Staging-first deployment workflow.
Flow:
- Pre-deploy checklist (tests pass, lint clean, migrations ready, rollback plan)
- Deploy to staging
- Run smoke tests
- Show results + wait for explicit production approval
- Deploy to production
- Post-deploy verification + environment separation audit
Never deploys to production without user confirmation.
Code review and security audit.
Covers: Code quality, security (OWASP), performance, breaking changes, test coverage, architecture
Output format: ✅ Good / 🚫 Must Fix / ⚠️ Should Fix / 💡 Suggestions + metrics table + go/no-go decision
All phases accept the short form as an argument to /helix:
/helix analyze → invokes helix:analyze
/helix plan → invokes helix:plan
/helix execute → invokes helix:execute
/helix test → invokes helix:test
/helix test-unit → invokes helix:test-unit
/helix test-integration → invokes helix:test-integration
/helix test-e2e → invokes helix:test-e2e
/helix test-security → invokes helix:test-security
/helix test-contract → invokes helix:test-contract
/helix test-a11y → invokes helix:test-a11y
/helix test-visual → invokes helix:test-visual
/helix test-perf → invokes helix:test-perf
/helix test-perf-load → invokes helix:test-perf-load
/helix test-perf-stress → invokes helix:test-perf-stress
/helix test-perf-soak → invokes helix:test-perf-soak
/helix test-perf-frontend → invokes helix:test-perf-frontend
/helix test-perf-db → invokes helix:test-perf-db
/helix test-perf-profile → invokes helix:test-perf-profile
/helix deploy → invokes helix:deploy
/helix review → invokes helix:review
/helix full → invokes helix:full