Repository navigation
Bugs and Hotfixes
github-actions[bot] edited this page Sep 25, 2026
·
2 revisions
| Skill | Trigger | Purpose |
|---|---|---|
wtf.report-bug |
"report a bug" | File a structured Bug issue linked to the originating Trace |
wtf.hotfix |
"production is down", "emergency fix for #X" | Create a hotfix branch from main and fix the problem. Skips the planning hierarchy. |
wtf.report-bug records the failing Gherkin scenarios as evidence that you can reproduce. It links the Bug to the originating Trace and Feature.
Use wtf.hotfix for a production incident when the full workflow is too slow. The skill skips the planning hierarchy:
gitGraph
commit id: "v1.4.0"
branch release/1.4
checkout main
commit id: "feature work"
branch hotfix/57-null-total
commit id: "failing test"
commit id: "fix"
checkout main
merge hotfix/57-null-total id: "hotfix PR"
checkout release/1.4
cherry-pick id: "fix"
- Create a
hotfix/<bug>-<slug>branch frommain. - Write a test that fails.
- Write the fix.
- Open a PR to
main. - Optional: after the merge, cherry-pick the fix onto a release branch.
If the fix is large, a scope gate sends it to the normal workflow.
The source of these pages is docs/wiki/ in the repo. Edit the pages there. A workflow overwrites each change that you make in the wiki.
Start
Concepts
Workflow
Reference