Github workflow

Skill byronxlg/skillfold/library/skills/github-workflow

Declarative skill manager for Claude Code and Codex. Declare skills in YAML, pin exact revisions in a lockfile, install them reproducibly into .claude/skills.

Install

npx -y skills add byronxlg/skillfold --skill github-workflow

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

11 stars11 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Work with GitHub branches, PRs, issues, and reviews via the gh CLI.

SKILL.md

1.9 KB, as published. Nobody here has run it

GitHub Workflow

You use GitHub as part of your development workflow, primarily through the gh CLI. You work with branches, pull requests, issues, and code review.

Branches and Pull Requests

Create a feature branch for each unit of work: git checkout -b <branch-name>
Keep branch names descriptive and lowercase with hyphens (e.g., fix-validation-error)
Open pull requests with a clear title and description: gh pr create --title "..." --body "..."
View PR details: gh pr view <number>
View PR diff: gh pr diff <number>
Check CI status: gh pr checks <number>
Merge approved PRs: gh pr merge <number>

Code Review

Review a PR by reading its diff: gh pr diff <number>
Approve: gh pr review <number> --approve --body "..."
Request changes: gh pr review <number> --request-changes --body "..."
Comment without approval decision: gh pr review <number> --comment --body "..."
View existing review comments: gh api repos/{owner}/{repo}/pulls/{number}/comments

Issues

List open issues: gh issue list
View an issue: gh issue view <number>
Create an issue: gh issue create --title "..." --body "..."
Close an issue: gh issue close <number>
Add labels: gh issue edit <number> --add-label "bug"

Workflow

Check for existing issues or PRs related to your work before starting
Create a feature branch from the latest main branch
Make focused commits with clear messages
Push early and often to keep the remote up to date
Open a PR when the work is ready for review
Address review feedback with additional commits
Merge after approval and passing CI checks

Output

Use gh commands to interact with GitHub. Prefer the CLI over the web interface for automation and reproducibility. Always verify CI status before merging.