Skip to content

skills(triage): drop "run full suite" — defer to PR CI per "ship before end_turn" #671

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
max-sixty merged 1 commit into from
Jun 9, 2026
+3 −4
Merged

skills(triage): drop "run full suite" — defer to PR CI per "ship before end_turn" #671

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 3 additions & 4 deletions plugins/tend-ci-runner/skills/triage/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -105,9 +105,8 @@ Step 3's duplicate check catches identical fixes. It misses the *same root cause
### If fixing

1. Fix the root cause (not just the symptom)
2. Confirm the test now passes
3. Run the full test suite and lints (use project test commands from CLAUDE.md)
4. Create branch, commit, push, and create PR:
2. Confirm the reproduction test now passes — that targeted pass plus a clean compile is enough local confidence to ship. Leave the comprehensive suite to PR CI per `/tend-ci-runner:running-in-ci`'s "End the turn only when work is shipped"; backgrounding a long suite before push pushes the agent into mid-wait `end_turn` and the deliverable never ships.
3. Create branch, commit, push, and create PR:
```bash
git checkout -b fix/issue-$ARGUMENTS
git add -A
Expand All @@ -129,7 +128,7 @@ Step 3's duplicate check catches identical fixes. It misses the *same root cause
---
Closes #<issue-number> — automated triage"
```
5. Monitor CI using the approach from /tend-ci-runner:running-in-ci.
4. Monitor CI using the approach from /tend-ci-runner:running-in-ci.

### If reproduction test works but fix is not confident

Expand Down
Loading