Skip to content

docs(context): start routine update triggers with a plain line, not a slash command - #111

Merged
qiansc merged 1 commit into
mainfrom
fix/routine-trigger-plain-text
Nov 15, 2026
Merged

qiansc merged 1 commit into
mainfrom
fix/routine-trigger-plain-text

Conversation

@qiansc

@qiansc qiansc commented Nov 15, 2026

Copy link
Copy Markdown
Contributor

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 or ROUTINE_POLICY, treats the request as a generic Context start, and stops to ask what to do.

Changes

  • The example trigger starts with a plain line: "Routine update: use the c4a:context Skill and follow its routine update procedure."
  • The procedure says to begin the content with that plain line instead of a slash command, and why.
  • Regenerated plugins/context/repo-install copies; 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

… 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>
@qiansc
qiansc merged commit 0bbb2a7 into main Nov 15, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant