dave/storkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 7 Wiki Activity

story-kit: queue 253_bug_watcher_and_auto_assign_do_not_reinitialize_when_project_root_changes for merge

Browse Source
This commit is contained in:
Dave
2026-03-16 23:23:45 +00:00
parent 7c3a756a5c
commit 2e25e2a46b
10 changed files with 124 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
.story_kit/work/5_done/240_story_btw_side_question_slash_command.md
View File

@@ -1,6 +1,5 @@
---
name: /btw Side Question Slash Command
merge_failure: "Squash-merge resulted in an empty diff after auto-resolving a conflict in frontend/src/components/Chat.tsx. The feature branch has no code changes beyond master — the changes may have already been incorporated into master via another merge, or the conflict resolution cancelled out the feature's additions. Human investigation needed to determine whether the feature code is already on master or needs to be re-implemented."
---
## User Story

1
.story_kit/work/5_done/242_story_status_slash_command.md
View File

@@ -1,6 +1,5 @@
---
name: "/status Slash Command"
merge_failure: "Squash-merge resulted in an empty diff — the feature branch (feature/story-242_story_status_slash_command) has no code changes beyond master. The coder agent's work may not have been committed to the feature branch, or the changes were already merged via another path."
---
# Story 242: /status Slash Command

1
.story_kit/work/5_done/246_story_enforce_cryptographic_identity_verification_for_matrix_commands.md
View File

@@ -1,6 +1,5 @@
---
name: "Enforce cryptographic identity verification for Matrix commands"
merge_failure: "Cherry-pick of squash commit onto master failed with \"fatal: bad revision 'merge-queue/246_story_enforce_cryptographic_identity_verification_for_matrix_commands'\". The merge-queue branch was created and the squash commit succeeded, but the branch reference was not accessible during the cherry-pick step. This appears to be an infrastructure/git reference issue in the merge pipeline, not a code conflict. Master is untouched."
---
# Story 246: Enforce cryptographic identity verification for Matrix commands

22
.story_kit/work/5_done/252_story_coder_agents_must_find_root_causes_for_bugs.md Normal file
View File

@@ -0,0 +1,22 @@
---
name: "Coder agents must find root causes for bugs"
---
# Story 252: Coder agents must find root causes for bugs
## User Story
As a project owner, I want coder agents to always investigate and fix the root cause of bugs rather than layering new code on top, so that fixes are surgical, minimal, and don't introduce unnecessary complexity.
## Acceptance Criteria
- [ ] When a coder agent picks up a bug, it must first investigate to find the root cause (e.g. using `git bisect`, `git log`, reading the relevant code history)
- [ ] The coder's commit message must explain what broke and why, not just what was changed
- [ ] Coders must not add new abstractions, wrappers, or workarounds when a targeted fix to the original code is possible
- [ ] The system prompt or agent instructions for coder agents include clear guidance: "For bugs, always find and fix the root cause. Use git bisect to find breaking commits. Do not layer new code on top of existing code when a surgical fix is possible."
- [ ] If a coder cannot determine the root cause, it must document what it tried and why it was inconclusive, rather than guessing and shipping a speculative fix
## Out of Scope
- Changes to how stories (non-bugs) are handled
- Automated enforcement (this is guidance/instruction, not a gate)