GitHub Ecosystem
GitHub is the repository coordination route when the task involves PRs, issues, checks, releases, repository metadata, code review comments, or CI state. Source: Ecosystem Capability Coverage, 2026-06-27; Skill Resolver, 2026-06-27
When To Use This
Use GitHub when work needs repository state or collaboration evidence. Use local git for the current checkout. Use Linear for planning state and Slack for conversation state. Source: Skill Resolver, 2026-06-27
Decision Matrix
| Need | Route | Verification |
|---|---|---|
| PR/issue/checks | gh CLI |
URL, ID, or check result |
| CI repair | Security and Review Skills | Before/after check state |
| Review comments | Security and Review Skills | Comment links resolved |
| Create issue | Cloud, Data, and Service Skills skill | Issue URL and body |
Core Model
GitHub is the code collaboration ledger. It does not replace local tests or worktree inspection. Trust current files and command output first, then use GitHub for remote state. Source: Git Workflow, 2026-06-27
Routing Summary
Preferred order: local git/files for current state, gh CLI for remote GitHub state, then GitHub workflow skills for issues, PRs, CI, comments, and release operations. Source: Skill Resolver, 2026-06-27; config/capability-harvest-seeds.json
Failure Modes
- Assuming GitHub remote state matches the dirty local tree.
- Mixing unrelated changes into a PR.
- Treating a green check as proof of untested behavior.
- Mutating issues/branches without confirming repository and branch.
Verification Path
Use gh auth status, gh repo view, gh pr status, gh pr checks, or targeted gh api reads. For writes, return URLs and IDs. Source: config/capability-harvest-seeds.json; Skill Resolver, 2026-06-27
Timeline
- 2026-06-27 | Canonical ecosystem page created after the ecosystem audit showed GitHub had broad coverage but no expected product-level page. Source: User request, 2026-06-27; Ecosystem Capability Coverage