Repository navigation
docs(context): start routine update triggers with a plain line, not a slash command - #111
Merged
Merged
Conversation
… slash command Some schedulers expand a leading slash command into the Skill text and drop everything after it, so a routine run never saw its paragraph and ROUTINE_POLICY. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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
The routine update procedure showed a scheduled task whose content starts with the slash command
/c4a:context routine update. Some schedulers expand a leading slash command into the Skill text and drop everything after it. The run then never sees the task paragraph orROUTINE_POLICY, treats the request as a generic Context start, and stops to ask what to do.Changes
c4a:contextSkill and follow its routine update procedure."plugins/context/repo-installcopies; CHANGELOG Unreleased entry.Tests
bun run build:plugin; plugin tests (57) pass.Compatibility
Text only. Existing triggers keep working where the scheduler passes the text after a slash command.
🤖 Generated with Claude Code