From 95eac2b5cfaca70837fdba80fc684e10d4087b97 Mon Sep 17 00:00:00 2001 From: qiansc Date: Sun, 15 Nov 2026 01:30:55 +0000 Subject: [PATCH] docs(context): start routine update triggers with a plain line, not a 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 --- CHANGELOG.md | 4 ++++ .../claude/resources/context/routine-update.md | 7 +++++-- .../codex/skills/context/references/routine-update.md | 7 +++++-- .../cursor/resources/context/routine-update.md | 7 +++++-- .../skills/context/references/routine-update.md | 7 +++++-- .../context/skills/context/references/routine-update.md | 7 +++++-- 6 files changed, 29 insertions(+), 10 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 78c40e78..af5f9076 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,6 +2,10 @@ All notable changes to Context are documented here. +## Unreleased + +- The routine update example now starts the scheduled task content with a plain line naming the Context Skill instead of a slash command. Some schedulers expand a leading slash command into the Skill text and drop the rest, so the run never saw its paragraph and `ROUTINE_POLICY` and stopped to ask what to do. + ## 0.7.99 - 2026-11-13 - `context task rollback` no longer gets stuck with an unfinished production stage: `context close` and the build accept the active rollback, and the rollback cleanup removes the stage. Previously close stopped with `production-not-complete` and the cleanup could not run. diff --git a/plugins/context/repo-install/claude/resources/context/routine-update.md b/plugins/context/repo-install/claude/resources/context/routine-update.md index 30789d8e..dfed7ee7 100644 --- a/plugins/context/repo-install/claude/resources/context/routine-update.md +++ b/plugins/context/repo-install/claude/resources/context/routine-update.md @@ -13,7 +13,7 @@ instance configuration may also define `ROUTINE_POLICY` defaults; keys in the trigger take precedence. For example, a scheduler's task content: ```text -/c4a:context routine update +Routine update: use the `c4a:context` Skill and follow its routine update procedure. This is the routine update of the Billing knowledge base. Refresh it from the latest registered code and documents, revise the affected articles so they @@ -29,7 +29,10 @@ ROUTINE_POLICY: time_budget_minutes: 90 # stop starting new batches after this ``` -Start the trigger with one short paragraph naming the knowledge base and what the +Begin the content with a plain line that names this Skill and the routine +update, not with a slash command: some schedulers expand a leading command into +the Skill text and drop everything after it, so the run never sees its settings. +Then write one short paragraph naming the knowledge base and what the run should achieve, including any team-specific guidance; it tells the agent which workspace and what matters. The paragraph may also set the reviews in plain language: an explicit statement that the whole run is managed and reviewed diff --git a/plugins/context/repo-install/codex/skills/context/references/routine-update.md b/plugins/context/repo-install/codex/skills/context/references/routine-update.md index 30789d8e..dfed7ee7 100644 --- a/plugins/context/repo-install/codex/skills/context/references/routine-update.md +++ b/plugins/context/repo-install/codex/skills/context/references/routine-update.md @@ -13,7 +13,7 @@ instance configuration may also define `ROUTINE_POLICY` defaults; keys in the trigger take precedence. For example, a scheduler's task content: ```text -/c4a:context routine update +Routine update: use the `c4a:context` Skill and follow its routine update procedure. This is the routine update of the Billing knowledge base. Refresh it from the latest registered code and documents, revise the affected articles so they @@ -29,7 +29,10 @@ ROUTINE_POLICY: time_budget_minutes: 90 # stop starting new batches after this ``` -Start the trigger with one short paragraph naming the knowledge base and what the +Begin the content with a plain line that names this Skill and the routine +update, not with a slash command: some schedulers expand a leading command into +the Skill text and drop everything after it, so the run never sees its settings. +Then write one short paragraph naming the knowledge base and what the run should achieve, including any team-specific guidance; it tells the agent which workspace and what matters. The paragraph may also set the reviews in plain language: an explicit statement that the whole run is managed and reviewed diff --git a/plugins/context/repo-install/cursor/resources/context/routine-update.md b/plugins/context/repo-install/cursor/resources/context/routine-update.md index d3a4a5d7..dfed7ee7 100644 --- a/plugins/context/repo-install/cursor/resources/context/routine-update.md +++ b/plugins/context/repo-install/cursor/resources/context/routine-update.md @@ -13,7 +13,7 @@ instance configuration may also define `ROUTINE_POLICY` defaults; keys in the trigger take precedence. For example, a scheduler's task content: ```text -/c4a-context routine update +Routine update: use the `c4a:context` Skill and follow its routine update procedure. This is the routine update of the Billing knowledge base. Refresh it from the latest registered code and documents, revise the affected articles so they @@ -29,7 +29,10 @@ ROUTINE_POLICY: time_budget_minutes: 90 # stop starting new batches after this ``` -Start the trigger with one short paragraph naming the knowledge base and what the +Begin the content with a plain line that names this Skill and the routine +update, not with a slash command: some schedulers expand a leading command into +the Skill text and drop everything after it, so the run never sees its settings. +Then write one short paragraph naming the knowledge base and what the run should achieve, including any team-specific guidance; it tells the agent which workspace and what matters. The paragraph may also set the reviews in plain language: an explicit statement that the whole run is managed and reviewed diff --git a/plugins/context/repo-install/skills/context/references/routine-update.md b/plugins/context/repo-install/skills/context/references/routine-update.md index 30789d8e..dfed7ee7 100644 --- a/plugins/context/repo-install/skills/context/references/routine-update.md +++ b/plugins/context/repo-install/skills/context/references/routine-update.md @@ -13,7 +13,7 @@ instance configuration may also define `ROUTINE_POLICY` defaults; keys in the trigger take precedence. For example, a scheduler's task content: ```text -/c4a:context routine update +Routine update: use the `c4a:context` Skill and follow its routine update procedure. This is the routine update of the Billing knowledge base. Refresh it from the latest registered code and documents, revise the affected articles so they @@ -29,7 +29,10 @@ ROUTINE_POLICY: time_budget_minutes: 90 # stop starting new batches after this ``` -Start the trigger with one short paragraph naming the knowledge base and what the +Begin the content with a plain line that names this Skill and the routine +update, not with a slash command: some schedulers expand a leading command into +the Skill text and drop everything after it, so the run never sees its settings. +Then write one short paragraph naming the knowledge base and what the run should achieve, including any team-specific guidance; it tells the agent which workspace and what matters. The paragraph may also set the reviews in plain language: an explicit statement that the whole run is managed and reviewed diff --git a/plugins/context/skills/context/references/routine-update.md b/plugins/context/skills/context/references/routine-update.md index 30789d8e..dfed7ee7 100644 --- a/plugins/context/skills/context/references/routine-update.md +++ b/plugins/context/skills/context/references/routine-update.md @@ -13,7 +13,7 @@ instance configuration may also define `ROUTINE_POLICY` defaults; keys in the trigger take precedence. For example, a scheduler's task content: ```text -/c4a:context routine update +Routine update: use the `c4a:context` Skill and follow its routine update procedure. This is the routine update of the Billing knowledge base. Refresh it from the latest registered code and documents, revise the affected articles so they @@ -29,7 +29,10 @@ ROUTINE_POLICY: time_budget_minutes: 90 # stop starting new batches after this ``` -Start the trigger with one short paragraph naming the knowledge base and what the +Begin the content with a plain line that names this Skill and the routine +update, not with a slash command: some schedulers expand a leading command into +the Skill text and drop everything after it, so the run never sees its settings. +Then write one short paragraph naming the knowledge base and what the run should achieve, including any team-specific guidance; it tells the agent which workspace and what matters. The paragraph may also set the reviews in plain language: an explicit statement that the whole run is managed and reviewed