# Github Developer

> GitHub Developer

- Skill: `spindizzy5/github-developer` (Agent Skill)
- Install (CLI): `npx skillmds@latest add spindizzy5/github-developer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/spindizzy5/github-developer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: spindizzy5 (https://skillmd.com/u/spindizzy5)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/spindizzy5/github-developer

---


# GitHub Developer

Operate as a pragmatic GitHub power-user. Prefer `gh` + local git for reliability; drop to API calls only when needed.

## Defaults

- If the user has a primary GitHub account, use it as the default owner (e.g. `spindizzy5`) unless they specify another org/user.
- Prefer minimal-permission auth. Never ask for or print tokens in logs/output.

## Workflow (run every time)

1. Identify the target:
   - Repo (`owner/name`) and default branch
   - Task type: PR work, issue triage, release, CI/Actions, automation/reporting
2. Confirm constraints:
   - Must it be done via `gh`, via API, or purely local git?
   - Any required conventions (branch naming, PR template, labels, semantic release)?
3. Execute with the safest path:
   - Prefer read-only inspection first (status, diff, checks)
   - Make small, reviewable changes (focused commits, clear PR description)
4. Validate:
   - Ensure CI passes (or explain failures), links are correct, and permissions are appropriate

## Command patterns (preferred)

- Repo + auth:
  - `gh auth status`
  - `gh repo view owner/name --web`
  - `gh repo clone owner/name`
- Branch/commit inspection:
  - `git status`, `git diff`, `git log --oneline --decorate -n 20`
  - `gh pr status`, `gh pr view <num> --comments --checks`
- PR creation + review:
  - `gh pr create --fill`
  - `gh pr edit <num> --title ... --body ...`
  - `gh pr review <num> --approve|--comment -b "…"`
  - `gh pr checkout <num>`
- Issue triage:
  - `gh issue list --label ... --state open`
  - `gh issue view <num> --comments`
  - `gh issue edit <num> --add-label ... --remove-label ...`
- Actions:
  - `gh run list --limit 20`
  - `gh run view <id> --log`

## PR quality bar

- Title: imperative, specific, scoped.
- Description: context + what changed + how tested + risks.
- Keep diffs tight; avoid drive-by formatting unless requested.
- If changes are risky, add a rollback plan and/or feature flag guidance.

## Repo hygiene (when asked)

- Add/adjust: CODEOWNERS, PR templates, issue templates, labels, CI checks, branch protections.
- Prefer documenting conventions in `CONTRIBUTING.md` and enforcing with CI where feasible.

## API usage (only when needed)

- Use GitHub REST/GraphQL for bulk operations (labels across many repos, org-wide reports, analytics).
- Store secrets in env vars (e.g. `GITHUB_TOKEN`) and keep scopes minimal (`repo`, `read:org`, etc. as required).
- For scripts, make them idempotent and rate-limit aware; print summaries, not secrets.