amnafarzy/ravie/github-operator
Claude Code and agent skill by amnafarzy/ravie
- community
- ext:[{"type":"hook","description":"Pre/post lifecycle hooks"}]
Checking that the SKILL.md file is still in the repository.
Use this for standalone git/GitHub operations — branch management, commit hygiene, PR creation or cleanup, CI failure triage, releases, remotes — when the work is NOT implementing an approved Linear issue end-to-end (that's issue-to-pr). Never push to main.
Install
npx vskill@latest install amnafarzy/ravie/github-operatorSemi-extensibleMentions customization, but needs skill-specific knowledge. Read the extensible skills standard
SKILL.md
The same SKILL.md was published earlier as amnafarzy/ravie/github-operator.
github-operator
Manage GitHub as the source of truth for code. Branches, commits, PRs, repo docs, releases — all governed by the same conventions.
Purpose
Treat GitHub as authoritative for code, migrations, repo documentation, and automation source. Maintain clean Git hygiene. Connect PRs to Linear issues. Resist treating chat as more authoritative than committed files.
Stack integration
Reads from:
- GitHub: repo state, branches, PRs, commits, checks, comments
- Local Git: working tree, staged/unstaged changes, branch state
- Linear: issues to link
- Notion: PRDs and decisions to reference
- Vercel: deployment status for previews
- Supabase: migrations and types files
CLAUDE.md: branch naming, commit conventions, PR template
Writes to:
- Branches (locally and remotely)
- Commits
- PR descriptions and comments
- Repo docs (README, ADRs, .env.example, etc.)
- Release notes
- Local draft changes only until pushed
Inputs required
- Repo (path or URL)
- Branch / issue key
- Work completed or to be completed
- Check status
- Linked Linear issue
- Linked Notion doc (if relevant)
- Write approval level
Process
0. Read the Git rule reference first
Before branch, commit, push, PR, or release work, read rules/git.md and follow its branch, commit, and merge discipline.
Inspecting state
Always start with current Git state:
For PR work, also check:
- What's the base branch state?
- Have there been recent merges that might conflict?
- Is CI passing on
main?
Branch naming
Default: [ISSUE-KEY]-[short-slug]
PROJ-42-dashboard-cardsSOR-89-fix-auth-redirect
Override per CLAUDE.md if project specifies different.
For non-issue work:
chore/[what]docs/[what]spike/[what]
Branch creation
Never create branches off stale main. Always pull first.
Commit conventions
Default: prefix with Linear issue key.
For multi-issue or non-issue work:
- Conventional commits:
feat:,fix:,chore:,docs:,refactor: - Group commits by intent, not by file
Coherent commits
Each commit should:
- Have one clear purpose
- Compile and pass checks (or be marked WIP)
- Have a message that explains why, not just what
- Stay under ~300 lines of changes when possible
Bad: "Updates" / "WIP" / "Fix stuff" Good: "PROJ-42: extract StatCard variants from prototype" / "Fix race condition in checkout submit by awaiting promise resolution"
Pre-push checks
Always run before pushing:
If any fail: fix them, don't ignore. Don't --no-verify your way past hooks.
Pushing
For first push, set upstream. After that, just git push.
Force-pushing
Avoid. Only acceptable on:
- Your own unmerged branch (not shared)
- After explicit approval
- Never on shared/main branches
Pull request creation
PR description template (override per CLAUDE.md):
PR review (your own or others')
Checklist:
- [ ] Summary matches what code actually does
- [ ] Acceptance criteria match Linear issue
- [ ] All checks pass
- [ ] Preview deploys cleanly (run
vercel-preview-qa) - [ ] No commented-out code, console.logs, or debug artifacts
- [ ] No commits with secrets / API keys / credentials
- [ ] No
// TODOwithout a Linear issue linked - [ ] Tests added for non-trivial logic
- [ ] No new dependencies without justification
- [ ] Migrations reviewed via
supabase-guardianif DB touched - [ ] Repo docs updated if commands/behavior changed
Merging
This is always Tier 4 — explicit approval each time, naming the exact PR.
When approved:
- Use squash merge by default (clean history)
- Use merge commit for major features (preserved history)
- Use rebase only for small chains (advanced)
Default per CLAUDE.md. Don't decide unilaterally.
Repo docs
Update when behavior changes:
README.md— setup commands, getting started, deployment.env.example— new env vars (without values)docs/adr/[date]-[title].md— architectural decisionsCHANGELOG.md— if maintained
Don't duplicate Notion content in repo docs. Repo docs are technical / setup. Product context lives in Notion.
Release notes
When tagging a release:
Then edit to:
- Group by feature / fix / chore
- Link Linear issues
- Highlight breaking changes
- Note migration steps if any
Stale branch cleanup
Weekly check:
- List branches with no PR, >14 days old
- List merged branches that weren't deleted
- Delete merged branches (locally and remotely):
``bash git fetch -p git branch -vv | grep ': gone' | awk '{print $1}' | xargs git branch -D ``
- Comment on stale unmerged branches asking if still active
Output format
Approval gates
Tier 1 (read-only) — inspecting repos, branches, PRs, checks: always allowed.
Tier 2 (draft) — local edits, drafts, plan files: always allowed.
Tier 3 — needs approval:
- Pushing branches
- Opening PRs
- Updating PR comments and body
- Updating repo docs
- Creating tags
Tier 4 — needs explicit approval naming exact target:
- Merging PRs
- Force-pushing (any branch)
- Deleting branches
- Changing branch protection
- Creating / modifying GitHub Actions secrets
- Publishing packages
- Creating releases
- History rewrites (rebase, amend, filter-branch)
Tier 5 — always blocked:
- Committing secrets
- Falsifying check status
- Bypassing pre-commit hooks
- Pushing directly to main (use PRs)
Hard rules
- Never commit secrets or
.envfiles - Never merge with failing checks
- Never force-push without approval (and never on shared branches)
- Never make huge mixed commits — split by intent
- Never leave issue-based PRs unlinked from Linear
- Never treat chat conclusions as authoritative over what's in the repo
- Never skip pre-push checks
- Never bypass hooks with
--no-verify - Never push to main directly
- Never delete branches without confirming they're merged
Connects to
issue-to-pr— the daily driver that calls this for branch / PR worklinear-operator— for issue linking and status updatescurrent-docs-guard— invoked before changing version-sensitive codesupabase-guardian— invoked when migrations are part of the PRvercel-preview-qa— invoked after push, before PR finalizeddeploy-ready— invoked before mergingPERMISSION-MODEL.md(repo root) — for tier escalation requestsdecision-log-adr— when decisions get committed as ADRs
Common failure modes
Pushing without baseline checks — CI fails, you scramble to fix in public. Always run checks locally first.
Mixed commits — One commit with a bug fix, a refactor, and a typo correction. Reviewer can't tell what's what. Split intent.
Stale main — Branch from week-old main, conflicts everywhere. Always git pull origin main before branching.
Bypassing hooks — --no-verify to skip pre-commit. Don't. Hooks exist to catch issues before push.
Lost work via force-push — Force-pushing over teammate's commits = deleted work. Use --force-with-lease and only on your own branches.
Untracked branch sprawl — 30 branches, half abandoned. Weekly cleanup. Delete merged branches.
PR body is empty — "see commits" is not a PR description. Reviewers need context, summary, risks, testing notes.
Linear/PR drift — PR merged but Linear still In Progress. Update Linear immediately, not after lunch.
Security
- Security scanPassed, 95 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/github-operator/SKILL.md
Popularity
- Repository stars
- 3
- 7-day trend score
- 7
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Extension points
hookPre/post lifecycle hooks
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/amnafarzy/ravie/github-operator)