Professional GitHub workflows via gh CLI. Use for repos, branches, PRs, CI/CD, releases, versioning, secrets, issues. Trigger on: GitHub, git, repo, PR, bran...
Security Analysis
high confidenceThis is a coherent GitHub CLI workflow guide, but it can use GitHub credentials to perform powerful repository actions that users should review carefully.
The documented capabilities match the stated GitHub workflow purpose, including PRs, issues, CI, releases, secrets, and branch protection. Some actions are high-impact but are disclosed.
The skill documents broad gh CLI/API operations. Many destructive or publishing operations explicitly say to confirm with the user first, which keeps the behavior purpose-aligned.
There is no install spec and no code files, so there is no hidden executable payload in the provided artifacts. However, the metadata does not declare the gh binary or GitHub credential requirement even though SKILL.md expects them.
GitHub authentication via gh auth or GITHUB_TOKEN is expected for this skill, and the instructions include safeguards not to print or log tokens.
No background persistence or autonomous worker is present, but the skill can make persistent changes to GitHub repositories, such as merges, releases, branch protection, secrets, workflow settings, or deletion when directed.
Guidance
This skill appears benign and purpose-aligned for GitHub work. Before installing or using it, make sure the active GitHub account/token has only the permissions needed, verify the target repository for every command, and require explicit confirmation before merges, releases, workflow changes, secret updates, branch-protection changes, or deletion/archive actions.
Latest Release
v1.2.0
# Changed - Split into `SKILL.md` (core) + 6 reference files — only the relevant section is loaded - ~70% token reduction on typical tasks # Added - `⚠️ CONFIRM WITH USER` warnings before all write/delete operations - Git Flow branching strategy: `main → develop → feature/fix/hotfix/release` - Branch protection via `gh api` - Semantic versioning with MAJOR/MINOR/PATCH table - Full 10-step workflow: issue → branch → PR → merge → release - CI best practices checklist for `.github/workflows/` - Security rules: no token exposure, `gh auth login --web` only # Removed - Monolithic single-file structure
More by @kretkas
Published by @kretkas on ClawHub
