agentleFS
rakaarwakyrakaarwaky/agents-arwaky/skills/git/github-workflow/SKILL.md

github-workflow

Skill0 starsChanged 8 days agoMITView on GitHub

Umbrella for GitHub auth, repo management, issues, PRs, Mergify, and releases. Subsumes github-auth and repo-manager.

  • Reads credentials
  • Commits and pushes

24 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use marketing-psychology, copywriting and 4 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SentrySkill

    marketing-psychology

    When the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,' 'behavioral science,' 'why people buy,' 'decision-making,' or 'consumer behavior.' This skill provides 70+ mental models organized for marketing application.

    Also in 3 projects that use this

  • SupabaseSkill

    copywriting

    Write or audit UI copy (buttons, labels, empty states, error messages, tooltips, form text) anywhere in the monorepo. Load it before shipping or reviewing any user-facing text — including when copy is incidental to the task, like a new feature that adds buttons, toasts, dialogs, or validation messages.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    git-workflow

    Squad branching model: dev-first workflow with insiders preview channel

    Also in 3 projects that use this

  • SentrySkill

    skill-creator

    Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.

    Also in 4 projects that use this

  • GoogleSkill

    code-review

    Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.

    Also in 3 projects that use this

  • BlockSkill

    frontend-design

    Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Prefer gh: Use gh commands; fall back to git + curl only where gh lacks coverage.

    line 15
  2. Very specific:

    gh authenticated: use gh for everything.

    line 26
  3. Very specific:

    Merge: only when ship is true and ship-ready gates pass.

    line 60

“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

GitHub Workflow

One umbrella for GitHub repository and PR lifecycle work. Split by job: auth, repo management, issue-to-PR, PR babysitting, Mergify, releasing. The Global Rules govern every job.

Global Rules

  • Auth prerequisite: Authenticated with GitHub first (auth job). Source gh-env.sh for auth and repo detection rather than re-implementing the fallback chain.
  • Prefer gh: Use gh commands; fall back to git + curl only where gh lacks coverage.
  • Lane is determined by physical signal, not self-identification. HERMES_AGENT=1 → Hermes lane; GROK_AGENT=1 → Grok lane; unset → stop and report. Never guess.
  • Takes EXISTING issues to PRs; does not create issues. Issue creation is a separate job.
  • Never merges automatically unless --ship is active and ship-ready gates pass on a live re-query.
  • CI must run green on the release branch before merge; tag created only on the merge commit. Never bump version directly to main or push a tag outside the prep PR flow.

Jobs (labeled subsections)

1. Auth — GitHub authentication setup

HTTPS tokens, SSH keys, gh CLI login (browser and device flow). Run git --version, gh --version, gh auth status, git config --global credential.helper before choosing a path.

  • gh authenticated: use gh for everything.
  • gh installed but not authenticated: gh auth login (browser or device flow).
  • gh not installed: git-only method (HTTPS PAT or SSH key, no sudo needed).
  • Token scopes: repo, workflow, read:org (90-day expiration recommended).
  • Git identity: configure user.name and user.email; required for commits.

Auth helper scripts live in scripts/: gh-env.sh (auth + repo detection, exports GH_AUTH_METHOD, GITHUB_TOKEN, GH_OWNER_REPO, etc.) and git-credential-token.py (extracts a token from the git credential store). Source gh-env.sh rather than re-implementing the fallback chain.

2. Repo — clone, create, fork, configure

Clone/create/fork repos; manage remotes, releases, settings, secrets, Actions CI via gh.

  • Clone: git clone <url> and gh repo clone owner/repo (HTTPS, SSH, shallow, branch).
  • Create: gh repo create NAME --public|--private --clone (user, org, template).
  • Fork: gh repo fork owner/repo --clone, then gh repo sync to keep in sync.
  • Settings: gh repo edit (description, visibility, topics, default branch) + branch protection REST.
  • Actions & releases: gh workflow / gh run / gh secret / gh release.
  • .gitignore: three-way diff (tracked / untracked / on-disk) + git check-ignore -v to find gaps.
  • Info: gh repo view, gh repo list, gh search repos.

3. Issue — issue to PR

Analyze open GitHub issues and take each from backlog to a PR opened to main. Verify at HEAD, run the decision quiz, 1 issue → 1 Orca worktree → Grok Build implements → Hermes verifies → Hermes pushes branch + opens a (draft) PR to main → close/reopen per result. Never merges.

  • Verify at HEAD per issue; ask the decision quiz.
  • Spawn one Grok worktree per still-broken issue and drop the brief.
  • Wait for each Grok session; verify commits, code, re-run symptom repro.
  • Push each verified branch, open one draft PR per issue.
  • Close verified-on-main issues with evidence; rebase still-open branches.

4. PR — watch and babysit

Watch a standalone GitHub PR end to end: register it, keep it green, merge it when --ship is active. Event-driven — CI re-runs and new review threads trigger fresh passes.

  • Register the PR, fetch it, check CI once.
  • If red or open threads: spawn a Grok worktree on the head branch and drop the fix brief.
  • Wait for the fix pass; re-run CI on the live head SHA.
  • Merge only when ship is true and ship-ready gates pass.

5. Mergify — stacked PRs, merge queue, CI

Mergify CLI surface: git push, commits, branches, PR create/update, rebase/fixup/squash/reword. Queue/dequeue via PR comments; diagnose dequeued PRs. Depends-On: / Merge-After: headers, scheduled freezes. CI Insights (JUnit upload, quarantines, scopes). Validate .mergify.yml. Browse Mergify events.

  • Prefer mergify stack * over git push / git rebase -i / gh pr edit.
  • Credential auth: --token / --repository (MERGIFY_TOKEN, MERGIFY_API_URL default https://api.mergify.com).
  • CI Insights keys: different key split (ci vs admin application keys).

6. Release — cut a release

Cut a CalVer release of the mergify CLI autonomously: bump via bump script, open and merge release prep PR, build and publish draft through GitHub workflows, recover failed release runs.

  • Repo guard: confirm git remote -v is Mergifyio/mergify-cli and CalVer scheme (YYYY.M.D.N) targeting PyPI + Homebrew.
  • Prep PR mandatory: CI must run green on release branch before merge; tag created only on merge commit.
  • Never gh release create or push a tag by hand. A release outside the workflow has no binaries.
  • Step 4 (Publish) is irreversible: locks the release and pushes to PyPI.

References

TopicFilePurpose
Auth detectreferences/step-0-detect.mdCheck git, gh, auth status; choose git-only or gh-cli path.
Auth gh-clireferences/step-1-gh-cli-auth.mdgh login: browser, device flow, hosts.yml fallback.
Auth git-onlyreferences/step-2-git-only-auth.mdHTTPS PAT or SSH key setup.
Clonereferences/clone.mdgit clone and gh repo clone.
Createreferences/create.mdgh repo create.
Forkreferences/fork.mdgh repo fork and sync.
Settingsreferences/setting.mdgh repo edit + branch protection.
Actionsreferences/action.mdgh workflow / gh run / gh secret / gh release.
Gitignorereferences/gitignore-audit.mdThree-way diff + git check-ignore -v.
Inforeferences/info.mdgh repo view / gh repo list / gh search repos.
Issue triagereferences/hermes/step-0-triage-and-spawn.mdVerify at HEAD, decision quiz, spawn worktree.
Issue verifyreferences/hermes/step-1-wait-and-verify.mdWait for Grok, verify commits and repro.
Issue shipreferences/hermes/step-2-ship-and-close.mdPush branch, open draft PR, close/reopen issues.
Issue reportreferences/hermes/step-3-final-report.mdFinal report: verdicts, PRs, closed issues.
PR watchreferences/hermes/step-0-watch-and-spawn.mdVerify auth, fetch PR, register, check CI.
PR reverifyreferences/hermes/step-1-wait-and-reverify.mdWait for fix pass, re-run CI.
PR mergereferences/hermes/step-2-merge.mdMerge when ship-ready gates pass.
PR reportreferences/hermes/step-3-final-report.mdFinal report to user.
Mergify stackreferences/stack.mdStacked PRs via mergify stack *.
Mergify queuereferences/merge-queue.mdQueue/dequeue, diagnose dequeued PRs.
Mergify protectionsreferences/merge-protections.mdDepends-On, Merge-After, freezes.
Mergify CIreferences/ci.mdJUnit upload, quarantines, scopes.
Mergify configreferences/config.mdValidate, simulate, write .mergify.yml.
Mergify eventsreferences/events.mdTimeline of Mergify actions.
Release bumpreferences/step-0-version-bump.mdVersion bump and changelog generation.
Release prepreferences/step-1-prep-pr.mdRelease prep PR: branch, CI green, merge.
Release preflightreferences/step-2-preflight.mdVerify main clean, report what ships.
Release buildreferences/step-3-build-draft.mdTrigger release.yml, verify seven assets.
Release publishreferences/step-4-publish.mdPublish draft, confirm PyPI + Homebrew.
Release verifyreferences/step-5-verify.mdVerify after publishing.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.