From 635f653f71ea2260bb8fa3f187bcb5263264ccb1 Mon Sep 17 00:00:00 2001 From: Naiyuan Qing <145280634+NevilleQingNY@users.noreply.github.com> Date: Wed, 3 Jun 2026 14:39:24 +0800 Subject: [PATCH] refactor(skills): drop CLI-only rule from working-on-issues The "Platform data goes through the CLI" section duplicated the runtime brief's `## Important: Always Use the multica CLI` section verbatim (and the attachment-via-CLI note duplicated the brief's `## Attachments`). The CLI-only rule is universal and must be known before any skill loads, so the brief is its single source of truth; the skill copy was pure redundancy and a drift risk. Remove it and the matching intro clause. Co-Authored-By: Claude Opus 4.8 Co-authored-by: multica-agent --- .../builtin_skills/multica-working-on-issues/SKILL.md | 11 ++--------- 1 file changed, 2 insertions(+), 9 deletions(-) diff --git a/server/internal/service/builtin_skills/multica-working-on-issues/SKILL.md b/server/internal/service/builtin_skills/multica-working-on-issues/SKILL.md index c1bfa6474b..bea557d4a7 100644 --- a/server/internal/service/builtin_skills/multica-working-on-issues/SKILL.md +++ b/server/internal/service/builtin_skills/multica-working-on-issues/SKILL.md @@ -8,8 +8,8 @@ allowed-tools: Bash(multica *), Bash(git *), Bash(gh *) # Working on Multica issues Product contracts the runtime brief does not fully encode: PR linking vs close -intent, reading linked-PR state, metadata keys, status side effects, sub-issue -enqueue behavior, and the CLI-only rule for platform data. +intent, reading linked-PR state, metadata keys, status side effects, and +sub-issue enqueue behavior. For building mention links, load `multica-mentioning` instead — not this skill. @@ -139,13 +139,6 @@ multica issue status todo # promote when the previous step is truly Creating every serial step as `todo` enqueues the whole chain at once. -## Platform data goes through the CLI - -Use the `multica` CLI for all Multica resources. Do not fetch Multica resource -URLs with curl, wget, or any direct HTTP client — they require authenticated -access only the CLI provides. For issue/comment attachments, inspect the -attachment CLI help and use that authenticated path. - ## Incorrect → correct PR title (link the issue):