**WORKFLOW SKILL** — Full GitHub contribution lifecycle: branches, conventional commits, issues, PRs, Actions, releases. gh CLI-first with MCP fallback. WHEN: "commit", "push", "open PR", "create branch", "create issue", "cut release", "GitHub operation". DO NOT USE FOR: Azure infrastructure, Bicep/Terraform code, architecture decisions. INVOKES: gh CLI (primary), GitHub MCP (fallback).
66
78%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.github/skills/github-operations/SKILL.mdFull contribution lifecycle — from branch creation to PR merge.
gh CLI preferred (always available in this dev container); MCP tools as
fallback for operations with no gh equivalent (rich PR review thread
management, bulk GraphQL queries).
1. Create branch (naming convention) →
2. Make changes →
3. Commit (conventional commits) →
4. Push (pre-push hooks validate branch + scope) →
5. Create PR (gh CLI) →
6. Review + Mergegh CLI by default — always available in this dev container; the more stable primitivegh cannot satisfy the operation (rich PR review threads, bulk GraphQL, Copilot review requests)git rev-parse --abbrev-ref HEAD; if invalid, stop and rename via git branch -mgh auth login; GH_TOKEN is set via VS Code User Settings (terminal.integrated.env.linux)--no-verify) unless the user explicitly asks| Type | Prefixes | File Scope |
|---|---|---|
| Domain-scoped | docs/, agents/, skills/, infra/, scripts/, instructions/ | Restricted to domain paths |
| Cross-cutting | feat/, fix/, chore/, ci/, refactor/, perf/, test/, build/, revert/ | Any files |
For scope tables, validation commands, and enforcement layers, read
references/branch-strategy.md.
Format: <type>[optional scope]: <description>.
Types: feat, fix, docs, refactor, perf, test, build, ci,
chore, revert.
Scopes: agents, skills, instructions, bicep, terraform, mcp,
docs, scripts.
For staging, breaking changes, and safety protocol, read
references/commit-conventions.md.
gh issue ... and gh pr ... are the default for both. MCP tools are
available as a fallback for operations the CLI does not cover well (rich
PR review threads, Copilot review requests, bulk GraphQL).
Default merge method:
squashunless the user specifies otherwise.
For tool tables, creation pre-flight checks, and the gh-vs-MCP decision
lattice, read references/issues-and-prs.md.
For PR lifecycle states, auto-labels, and auto-merge conditions, read
references/smart-pr-flow.md.
For complete gh CLI commands covering repos, Actions, releases, secrets,
API, and auth, read
references/detailed-commands.md.
IMPORTANT:
gh api -fdoes not support object values. Use multiple-fflags with hierarchical keys and string values instead.
| Flag | Description |
|---|---|
--repo OWNER/REPO | Target specific repository |
--json FIELDS | Output JSON with fields |
--jq EXPRESSION | Filter JSON output |
--web | Open in browser |
--paginate | Fetch all pages |
| Condition | Label Applied |
|---|---|
| CI passes | infraops-ci-pass |
| CI fails | infraops-needs-fix |
| Review approved | infraops-reviewed |
| Auto-merge (all gates pass) | PR merged via MCP |
Full state machine, watchdog pattern, and auto-merge gates in
references/smart-pr-flow.md.
| Reference | File | Content |
|---|---|---|
| Branch Strategy | references/branch-strategy.md | Naming convention, scope tables, enforcement layers |
| Commit Conventions | references/commit-conventions.md | Format, types, staging workflow, safety protocol |
| Issues & PRs | references/issues-and-prs.md | gh-vs-MCP decision lattice, tool tables, pre-flight |
| Smart PR Flow | references/smart-pr-flow.md | PR lifecycle states, auto-labels, auto-merge |
| CLI Commands | references/detailed-commands.md | Repos, Actions, Releases, Secrets, API, Auth |
05d7617
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.