- onboard: new contributor onboarding with --issues/--tag support
- compliance: license audit, secret scan, PII check, sensitive vocab scan
- contrib: contribution report generation
- Update register.go to register all three shortcut groups
- Add skills/gitlink-onboard and skills/gitlink-compliance skill docs
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- resolve conflicts in register.go, release/release.go, repo/repo.go, SKILL.md
- keep milestone/team/webhook registrations from zk_branch
- incorporate batch_create/batch_update from master
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
- Add wiki +lint: check empty pages, missing H1, short content, dead links, broken images
- Fix lint to use sub_url for fetching page content instead of title
- Skip system pages (_Sidebar, _Footer, _Header) in lint checks
- Add CHANGELOG.md for wiki module
- Add dry-run support to branch, ci, issue, org, pr, release, repo commands
- Add batch operations for org and repo members
- Add gitlink-wiki skill definition
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Add a convenience command to comment on pull requests directly,
without needing to look up the underlying issue ID first.
Internally resolves the PR's issue ID via pr +view, then posts
to the issues journals API.
- 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
Donkey_kevin
wbtiger
Zhang Jinnan