| name | github-ops |
| description | GitHub issue, PR, and release operations via gh CLI. Not for code review or release builds. |
| version | 2.1.0 |
| allowed-tools | ["Bash","Read"] |
GitHub Operations Skill
Use this skill when working with GitHub issues, PRs, and releases for Pake. It carries the project facts and boundaries; standard gh usage is assumed.
Golden Rule
Always use gh CLI and query live state before acting. Never assume state from memory or a previous turn.
Project Facts
- Repo:
tw93/Pake. Workflows: release.yml (V* tag, builds app assets), npm-publish.yml (npm Trusted Publishing; also workflow_dispatch from main for npm-only hotfixes), quality-and-test.yml (push and PR CI), pake-cli.yaml / single-app.yaml (public build surfaces external users trigger from forks).
- Poll CI with
gh run view <run-id> --json status,conclusion. Never pipe gh run watch or build output through tail/head; pipes swallow the real exit code and misreport failures as green.
- Verify npm state with
npm view pake-cli@<version> version gitHead dist.tarball --json; gitHead ties the published package to the intended commit. Check the latest pointer separately with npm view pake-cli version; it can point at a different commit than the fix under review.
- Inline PR review comments live at
gh api repos/tw93/Pake/pulls/<n>/comments; gh pr view does not show them.
- App-release truth is
gh release view <tag> --json assets (asset count/state), not workflow names or source state.
Safety Rules
- Prepare and review the exact reply before sending. If the user has explicitly authorized the write action or a batch containing it, complete that scope without another approval checkpoint; otherwise show the draft and ask before writing. Approval of wording alone does not authorize posting, merging, closing, or publishing.
- NEVER merge, close, or modify without explicit user request.
- Before replying to an issue or PR, read the body to confirm the author's language; match their language in the reply. This applies to the author, not to arbitrary thread commenters.
- Before replying that a CLI fix is released, verify the exact artifact with
npm view pake-cli@<version> version gitHead dist.tarball --json and confirm gitHead contains the fix. Check npm view pake-cli version separately for the latest pointer. For app releases, use gh release view <tag> --json assets.
- Before closing an issue after release, confirm the target with
gh issue view <id> --json number,title,state,author,url and include the concrete version or upgrade command in the comment.
