- Add repo +delete-file shortcut command in shortcuts/repo/repo.go
- Add comprehensive unit tests for create-file, update-file, delete-file
(15 new test cases covering happy paths, optional params, missing args,
and HTTP error handling)
- Update gitlink-notification-digest Skill to v3.0.0 using notification
+list/+read/+read-all/+watch shortcuts
- Update gitlink-pm Skill to v1.1.0 using pm +dashboards/+sprints/+weekly
shortcuts
- Fix gitlink-shared/SKILL.md Raw API example (user +me → api GET /users/me)
- Update api-reference.md examples to use notification shortcuts
- Update gitlink-contributor-insight examples to reflect current
command availability
- Update CI config branch from wyx_branch to master
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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