将 skills/ 目录下 21 个文件中的 gitlink-cli api <METHOD> <PATH> 命令
替换为对应的 Shortcut 命令，修复因 Token 注入不完整导致的 HTML 响应问题。
主要替换:
- api GET /:owner/:repo/languages → repo +languages
- api GET /:owner/:repo/sub_entries → repo +files
- api GET /:owner/:repo/raw/... → repo +raw
- api POST /:owner/:repo/create_file → repo +create-file
- api POST /:owner/:repo/pulls/:id/reviews → pr +review
- api GET /:owner/:repo/pulls/:id → pr +view
- 等共 107 处替换
注: 6 处 pm 域命令暂留（pm 模块尚未构建）
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
- gitlink-shared: add 'PR Collaboration Workflow' section with Fork flow,
correct/incorrect examples, and self-owned repo exception
- gitlink-pr: replace single-path PR creation with two sections:
1. Fork flow for contributing to others' repos (mandatory)
2. Direct branch flow for self-owned repos (allowed)
Ensures AI agents follow standard open-source collaboration practices
instead of pushing branches directly to upstream repositories.
Problem:
AI agents (e.g., Claude Code) sometimes use `gh` (GitHub CLI) instead of
`gitlink-cli` when operating on GitLink repositories, causing 'command not
found' errors or targeting the wrong platform.
Solution:
- Add '⛔ Tool Boundary' section to gitlink-shared/SKILL.md with platform-
to-tool mapping table, judgment criteria, and dual-platform guidance
- Add CRITICAL one-liner to all 10 sub-skills ensuring agents see the
constraint even without reading shared
- Does NOT block `gh` for GitHub operations — only prevents misuse on
GitLink resources
Tested with 5 scenarios confirming:
1. GitLink operations correctly use gitlink-cli
2. GitHub operations still use gh when appropriate
3. Ambiguous cases default to gitlink-cli when skill is loaded
wbtiger
Surponess
Mengz
yangsai01
林迪文
Zhang Jinnan