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 <noreply@anthropic.com>
Co-authored-by: multica-agent <github@multica.ai>
This commit is contained in:
Naiyuan Qing
2026-06-03 14:39:24 +08:00
parent 75250774af
commit 635f653f71

View File

@@ -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 <child-id> 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):