| name | coding-workflow |
| description | Use this skill for any coding task that involves working with repositories, writing code, creating branches, or opening pull requests. Covers the full development workflow from cloning to PR. |
Coding Workflow
GitHub CLI (gh)
Always use the gh CLI for all GitHub operations. Both gh and git are authenticated automatically through the agent proxy.
Use gh for: cloning repos, discovering repos across orgs, creating/viewing/editing PRs, checking PR status, and viewing PR comments.
Do NOT use unauthenticated git clone https://github.com/... — use gh repo clone instead.
Forking Workflow
When you don't have write access to a repository (push fails with 403/permission denied):
- Fork it:
gh repo fork --remote=true (this adds your fork as the origin remote and renames the original to upstream)
- Push your branch to the fork:
git push -u origin <branch-name>
- Open a PR from your fork to the upstream repo:
gh pr create --repo <upstream-owner>/<repo>
To avoid wasted time, check write access early. If the repo belongs to an organization you're unlikely to have push access to, fork before starting work.
Git Workflow
- Always start by pulling the latest default branch (
main or master)
- Create a feature branch for every task
- Branch names: short, lowercase, hyphenated (e.g.,
fix-login-redirect, add-csv-export)
- NEVER push directly to the default branch
Commits
