- Fix batch-label: use issue_tag_ids instead of tracker_id
- Fix parseTracker: support Chinese label names (缺陷/功能/疑问 etc.)
- Add workflow skill menu (workflows/SKILL.md) with 5 automation options
- Add workflow reference files: community-ops, contributor-growth, multi-repo
- Fix PowerShell scripts: Invoke-GL array syntax, remove ConvertFrom-Json
- Fix wiki +create flag from --body to --content
- Update contributor-growth doc with known issues and field corrections
- Add contributor leaderboard HTML report
Co-Authored-By: Claude Opus 4.6 <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
Donkey_kevin
wbtiger