Conversation
…ription
The frontmatter description still listed publishing-related trigger
phrases ("push extension", "publish extension", "extension push",
"release extension", "bump version", "publish to registry", "prepare
for publishing") even though those queries should route to
swamp-extension-publish. This mismatch causes ambiguity in trigger
routing. Remove the stale phrases to align the description with the
evals and the swamp-extension-publish skill.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
Blocking Issues
None.
Suggestions
None — this is a clean, well-scoped fix.
Verification:
- Confirmed all 7 removed trigger phrases ("push extension", "publish extension", "extension push", "release extension", "bump version", "publish to registry", "prepare for publishing") are already present in
swamp-extension-publish/SKILL.mdwhere they belong. - Confirmed
trigger_evals.jsonalready correctly marks publishing-related queries asshould_trigger: falsewith notes pointing toswamp-extension-publish— the description now aligns with the evals. - Frontmatter follows CLAUDE.md conventions (
name+descriptiononly). - No domain code changes; DDD review not applicable.
LGTM — resolves the trigger routing ambiguity cleanly.
stack72
deleted the
fix/remove-stale-publish-triggers-from-extension-model
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
swamp-extension-modelskill descriptionswamp-extension-publishand were causing ambiguity in trigger routingshould_trigger: false, but the description still advertised themTest Plan
deno fmt --checkpassesdeno lintpassesdeno run testpasses (4310 tests)🤖 Generated with Claude Code