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
- Gogo-Bytes/blogtheir own version, first seen Nov 8, 2026
- yaqob3653/vlypse-skillstheir own version, first seen Nov 8, 2026
- MMACABRE/SKILLStheir own version, first seen Nov 8, 2026
- AlvaroVFon/skillstheir own version, first seen Nov 1, 2026
- MattoYuzuru/yuzuru-skillstheir own version, first seen Oct 25, 2026
- lcx9451/dsh-engineering-skill-packtheir own version, first seen Oct 25, 2026
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.
SentrySkillmarketing-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
SupabaseSkillcopywriting
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 AzureSkillgit-workflow
Squad branching model: dev-first workflow with insiders preview channel
Also in 3 projects that use this
SentrySkillskill-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
GoogleSkillcode-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
BlockSkillfrontend-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
Other versions24 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 24
- massCodeIO/massCode★ 7.1ksame name
- huynhsontung/Screenbox★ 4.7ksame name
- Mindrally/skills★ 275same name
- amanning3390/hermeshub★ 48same name
- zajca/pohunek★ 9same name
- drewid74/ai_skills★ 8same name
- rloisell/rl-agents-n-skills★ 8same name
- berkeley-humanoids/skills★ 4same name
- berkeley-humanoids/Skills★ 4same name
- Kur1sulab/blackbox★ 3same name
14 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository83 other files it gives its agents.
- AGENTS.mdAGENTS.md
- aes-docsSkill
- aes-fixSkill
- aes-layerSkill
- aes-migrationSkill
- aesSkill
- android-emulator-linux-gpsSkill
- computer-useSkill
- flatpak-chromium-automationSkill
- qwen-webSkill
- computer-useSkill
- grok-buildSkill
- hermes-agentSkill
- omnirouteSkill
- orcaSkill
- account-managerSkill
- brave-automationSkill
- brave-provider-authSkill
- brave-setupSkill
- brave-sync-managementSkill
- password-managerSkill
- codegraphSkill
- deep-cleanSkill
- dogfoodSkill
- reviewSkill
- systematic-debuggingSkill
- blender-arwakySkill
- comfyuiSkill
- llm-writingSkill
- vision-arwakySkill
- playwright-toolingSkill
- setup-ci-quality-gatesSkill
- statuslineSkill
- systemd-headless-serviceSkill
- xdg-spec-complianceSkill
- figcraft-builderSkill
- figcraft-iconsSkill
- figcraft-motionSkill
- figcraft-prototyperSkill
- figcraft-reviewSkill
- figcraftSkill
- figcraft-svgSkill
- figcraft-typographySkill
- issue-makerSkill
- issue-workerSkill
- mergifySkill
- pr-babysitSkill
- releasingSkill
- ascii-artSkill
- ascii-videoSkill
- gif-searchSkill
- media-acquisitionSkill
- docxSkill
- emailSkill
- google-workspaceSkill
- notionSkill
- pdfSkill
- pptxSkill
- xlsxSkill
- competitor-news-monitorSkill
- The first 60 shown.
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
- Very specific: line 15
Prefer
gh: Use gh commands; fall back to git + curl only where gh lacks coverage. - Very specific: line 26
gh authenticated: use gh for everything.
- Very specific: line 60
Merge: only when ship is true and ship-ready gates pass.
“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.
Files
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.shfor auth and repo detection rather than re-implementing the fallback chain. - Prefer
gh: Useghcommands; fall back togit+curlonly whereghlacks 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
--shipis 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
ghfor 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.nameanduser.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>andgh 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, thengh repo syncto 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 -vto 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
shipis 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 *overgit push/git rebase -i/gh pr edit. - Credential auth:
--token/--repository(MERGIFY_TOKEN,MERGIFY_API_URLdefaulthttps://api.mergify.com). - CI Insights keys: different key split (
civsadminapplication 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 -visMergifyio/mergify-cliand 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 createor 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
| Topic | File | Purpose |
| Auth detect | references/step-0-detect.md | Check git, gh, auth status; choose git-only or gh-cli path. |
| Auth gh-cli | references/step-1-gh-cli-auth.md | gh login: browser, device flow, hosts.yml fallback. |
| Auth git-only | references/step-2-git-only-auth.md | HTTPS PAT or SSH key setup. |
| Clone | references/clone.md | git clone and gh repo clone. |
| Create | references/create.md | gh repo create. |
| Fork | references/fork.md | gh repo fork and sync. |
| Settings | references/setting.md | gh repo edit + branch protection. |
| Actions | references/action.md | gh workflow / gh run / gh secret / gh release. |
| Gitignore | references/gitignore-audit.md | Three-way diff + git check-ignore -v. |
| Info | references/info.md | gh repo view / gh repo list / gh search repos. |
| Issue triage | references/hermes/step-0-triage-and-spawn.md | Verify at HEAD, decision quiz, spawn worktree. |
| Issue verify | references/hermes/step-1-wait-and-verify.md | Wait for Grok, verify commits and repro. |
| Issue ship | references/hermes/step-2-ship-and-close.md | Push branch, open draft PR, close/reopen issues. |
| Issue report | references/hermes/step-3-final-report.md | Final report: verdicts, PRs, closed issues. |
| PR watch | references/hermes/step-0-watch-and-spawn.md | Verify auth, fetch PR, register, check CI. |
| PR reverify | references/hermes/step-1-wait-and-reverify.md | Wait for fix pass, re-run CI. |
| PR merge | references/hermes/step-2-merge.md | Merge when ship-ready gates pass. |
| PR report | references/hermes/step-3-final-report.md | Final report to user. |
| Mergify stack | references/stack.md | Stacked PRs via mergify stack *. |
| Mergify queue | references/merge-queue.md | Queue/dequeue, diagnose dequeued PRs. |
| Mergify protections | references/merge-protections.md | Depends-On, Merge-After, freezes. |
| Mergify CI | references/ci.md | JUnit upload, quarantines, scopes. |
| Mergify config | references/config.md | Validate, simulate, write .mergify.yml. |
| Mergify events | references/events.md | Timeline of Mergify actions. |
| Release bump | references/step-0-version-bump.md | Version bump and changelog generation. |
| Release prep | references/step-1-prep-pr.md | Release prep PR: branch, CI green, merge. |
| Release preflight | references/step-2-preflight.md | Verify main clean, report what ships. |
| Release build | references/step-3-build-draft.md | Trigger release.yml, verify seven assets. |
| Release publish | references/step-4-publish.md | Publish draft, confirm PyPI + Homebrew. |
| Release verify | references/step-5-verify.md | Verify after publishing. |
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
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.

