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

story-kit: queue 220_story_acceptance_gates_in_current_stage_should_use_script_test_instead_of_hardcoded_cargo_clippy for QA

Browse Source
This commit is contained in:
Dave
2026-02-26 19:28:02 +00:00
parent 129de50856
commit 65776620db
1 changed files with 0 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
.story_kit/work/2_current/220_story_acceptance_gates_in_current_stage_should_use_script_test_instead_of_hardcoded_cargo_clippy.md
View File

@@ -1,20 +0,0 @@
---
name: "Acceptance gates in Current stage should use script/test instead of hardcoded cargo clippy"
---
# Story 220: Acceptance gates in Current stage should use script/test instead of hardcoded cargo clippy
## User Story
As a developer using Story Kit with a non-Rust project, I want the acceptance gates that run after a coder agent completes to use script/test and project.toml components instead of hardcoded cargo clippy, so that my Go/Python/Node project doesn't fail gates for missing Rust tooling.
## Acceptance Criteria
- [ ] run_acceptance_gates uses script/test as the primary quality gate instead of hardcoded cargo clippy
- [ ] run_acceptance_gates does not invoke cargo clippy unless the project has a Cargo.toml
- [ ] Default coder prompt in config.rs no longer mentions cargo clippy (uses generic 'quality gates' language)
- [ ] MCP merge_agent_work tool description no longer hardcodes cargo clippy/pnpm references
## Out of Scope
- TBD