swamp-club/swamp-extensions
Watch
8
0
Fork
You've already forked swamp-extensions
 0
Code Pull requests 3 Activity Actions

fix(gatorwalk-factory): keep swamp-extensions stages off issue-lifecycle's driver (swamp-club #2768) #380

Merged
seth merged 1 commit from cue/2768-gatorwalk-factory-swamp into main 2026-09-30 15:46:42 +00:00
Conversation 0 Commits 1 Files changed 3 +102 -8
seth commented 2026-09-30 15:44:24 +00:00
Owner
Copy link

Fixes swamp-club #2768.

Problem

gatorwalk-factory/lifecycles/swamp-extensions.yaml listed skills: [issue-lifecycle] on triage, plan and implement, and the conformance-review prompt cited .claude/skills/issue-lifecycle/references/code-conformance-review.md. Both tell the agent to run @swamp/issue-lifecycle methods on an issue-<N> instance. Under gatorwalk that instance never exists, so an agent following its own stage would start a second driver on the Lab issue, and two interleaved histories would spoil the dogfood audit trail.

Change

  • Remove the issue-lifecycle skill from triage, plan and implement. Their prompts already carry what they need (the regression procedure, the agent-constraints conventions).
  • Rewrite the conformance-review prompt to state its procedure directly instead of citing the skill's reference.
  • Add one guard sentence to all 12 agent-run stages (interactive and dispatch): gatorwalk drives this issue, so do not use the issue-lifecycle skill or run any @swamp/issue-lifecycle method. The skill also triggers on its own ("triage issue", "review plan", "ready to ship").
  • Two tests in lifecycles_test.ts: no stage lists the skill or cites a file that mentions issue-lifecycle, and every agent-run prompt carries the exact guard sentence.
  • One sentence in swamp-extensions.md.

Out of scope, by decision: a write-time guard on publish, and any change to issue-lifecycle itself.

Verification

Attested at 7621982b6 (attestation 0e016a86-70c1-441e-bd6d-272130429dcc): verify-build and verify-reviews both passed, 12/12 steps, 2 skipped by guard. gatorwalk-factory: 508 unit and 25 integration tests pass.

🤖 Generated with Claude Code

Fixes swamp-club #2768. ## Problem `gatorwalk-factory/lifecycles/swamp-extensions.yaml` listed `skills: [issue-lifecycle]` on triage, plan and implement, and the conformance-review prompt cited `.claude/skills/issue-lifecycle/references/code-conformance-review.md`. Both tell the agent to run `@swamp/issue-lifecycle` methods on an `issue-<N>` instance. Under gatorwalk that instance never exists, so an agent following its own stage would start a second driver on the Lab issue, and two interleaved histories would spoil the dogfood audit trail. ## Change - Remove the issue-lifecycle skill from triage, plan and implement. Their prompts already carry what they need (the regression procedure, the agent-constraints conventions). - Rewrite the conformance-review prompt to state its procedure directly instead of citing the skill's reference. - Add one guard sentence to all 12 agent-run stages (interactive and dispatch): gatorwalk drives this issue, so do not use the issue-lifecycle skill or run any `@swamp/issue-lifecycle` method. The skill also triggers on its own ("triage issue", "review plan", "ready to ship"). - Two tests in `lifecycles_test.ts`: no stage lists the skill or cites a file that mentions issue-lifecycle, and every agent-run prompt carries the exact guard sentence. - One sentence in `swamp-extensions.md`. Out of scope, by decision: a write-time guard on `publish`, and any change to issue-lifecycle itself. ## Verification Attested at 7621982b6 (attestation 0e016a86-70c1-441e-bd6d-272130429dcc): verify-build and verify-reviews both passed, 12/12 steps, 2 skipped by guard. gatorwalk-factory: 508 unit and 25 integration tests pass. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
fix(gatorwalk-factory): keep swamp-extensions stages off issue-lifecycle's driver (swamp-club #2768)
All checks were successful
CI / Review Integrity (pull_request) Successful in 41s
Details
CI / Validate Attestation (pull_request) Successful in 52s
Details
7621982b61
 
The swamp-extensions lifecycle listed the issue-lifecycle skill on triage,
plan and implement, and conformance-review cited its code-conformance
reference. Both tell the agent to run @swamp/issue-lifecycle methods on an
issue-<N> instance, which never exists under gatorwalk, so an agent following
its own stage would start a second driver on the Lab issue.

Drop the skill from the three stages, state the conformance procedure in the
prompt instead of citing the reference, and tell every agent-run stage not to
use the skill or run its methods, since it also triggers on its own. Two tests
in lifecycles_test.ts pin this: no stage lists the skill or cites a file that
mentions issue-lifecycle, and all twelve agent-run prompts carry the guard.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
seth merged commit d92d1f1927 into main 2026-09-30 15:46:42 +00:00
seth deleted branch cue/2768-gatorwalk-factory-swamp 2026-09-30 15:46:43 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
swamp-club/swamp-extensions!380
No description provided.