Command
add-new-provider
Add a new AI provider "$ARGUMENTS" to the OpenUsage TUI dashboard.
@janekbaraniewskiView CommandMonitoring
Command
/validate-feature
Validate the feature "$ARGUMENTS" implementation.
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/validate-feature
Context preview
What this command does when you run it.
Validate the feature "$ARGUMENTS" implementation.
Command definition
validate-feature.mdValidate the feature "$ARGUMENTS" implementation.
Read and follow the full skill specification in docs/skills/validate-feature/SKILL.md.
Follow all phases:
1. **Phase 0 — Load**: Find design doc, extract tasks, get changed files. 2. **Phase 1 — Build**: `make build`, `make vet`, `make fmt`, `make lint`. 3. **Phase 2 — Tests**: Run tests for changed packages. 4. **Phase 3 — Compliance**: Cross-reference design tasks vs actual changes. 5. **Phase 4 — Quality**: Scan for debug artifacts, unused code, secrets. 6. **Phase 5 — Smoke Test**: Final build and combined tests. 7. **Phase 6 — Report**: Verdict: READY FOR REVIEW or NEEDS ITERATION.
Ships withopenusage
The one dashboard you’ve been looking for — track spend and usage across Claude, Cursor, OpenRouter, Copilot, Gemini, Codex, and more.
Get the whole plugin
Other commands on openusage.
@janekbaraniewskiView CommandCommand
Command
design-feature
Design a new feature "$ARGUMENTS" for the OpenUsage TUI dashboard.
@janekbaraniewskiView CommandCommand
dev-workflow-improveme…
Audit and improve the development workflow for OpenUsage.
@janekbaraniewskiView CommandCommand
develop-feature
Develop the feature "$ARGUMENTS" end-to-end — from design to pull request.
@janekbaraniewskiView CommandCommand
finalize-feature
Finalize the feature "$ARGUMENTS" — create branch, commit, and open PR.
@janekbaraniewskiView Command