github-workflow
Skill48 starsChanged 5 months agoMITView on GitHub
Complete GitHub workflow — repos, branches, commits, PRs, issues, code review, and releases. Use when the user mentions GitHub, git, pull requests, issues, or repository management.
- Commits and pushes
23 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
- 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
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 versions23 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 23
- massCodeIO/massCode★ 7.1ksame name
- huynhsontung/Screenbox★ 4.7ksame name
- Mindrally/skills★ 275same name
- drewid74/ai_skills★ 8same name
- rloisell/rl-agents-n-skills★ 8same name
- zajca/pohunek★ 8same name
- berkeley-humanoids/skills★ 4same name
- berkeley-humanoids/Skills★ 4same name
- Kur1sulab/blackbox★ 3same name
- lcx9451/dsh-engineering-skill-pack★ 3same name
13 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 repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-hardeningSkill
- api-builderSkill
- arxiv-watcherSkill
- data-analystSkill
- diagram-makerSkill
- docker-managerSkill
- google-workspaceSkill
- hermeshub-reviewerSkill
- hermes-workspaceSkill
- notion-integrationSkill
- paperclipSkill
- project-plannerSkill
- react-reasoningSkill
- relay-for-telegramSkill
- scraplingSkill
- security-auditorSkill
- Skill FactorySkill
- slack-botSkill
- synapse-swarmSkill
- test-runnerSkill
- web-researcherSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 2 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 34
Create feature branch: git checkout -b feature/name
- Very specific: line 36
Commit with conventional message: git commit -m "type: description"
- Distinctive: line 65
Always check current branch before committing
- Very specific: line 67
Use --force-with-lease instead of --force
- Distinctive: line 68
Verify PR base branch is correct
- Very specific: line 72
Verify merge status: gh pr status
- Very specific: line 73
Check CI status: gh run list
“Common” is measured: kept by at least 6 in 10 of the 16 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
Full GitHub lifecycle management through the gh CLI.
When to Use
- User mentions GitHub, repos, branches, commits, or pull requests
- User wants to manage issues, labels, or milestones
- User needs code review assistance
- User wants to set up CI/CD or manage releases
Procedure
Repository Operations
- Clone:
gh repo clone owner/repo - Create:
gh repo create name --public/--private - Fork:
gh repo fork owner/repo
Branch Workflow
- Create feature branch:
git checkout -b feature/name - Stage changes:
git add -A - Commit with conventional message:
git commit -m "type: description" - Push:
git push -u origin feature/name
Pull Request Workflow
- Create PR:
gh pr create --title "..." --body "..." --base main - List PRs:
gh pr list - Review PR:
gh pr review <number> --approve/--request-changes - Merge:
gh pr merge <number> --squash
Issue Management
- Create:
gh issue create --title "..." --body "..." --label bug - List:
gh issue list --state open - Close:
gh issue close <number> - Assign:
gh issue edit <number> --add-assignee @me
Release Workflow
- Tag:
git tag -a v1.0.0 -m "Release v1.0.0" - Push tags:
git push --tags - Create release:
gh release create v1.0.0 --generate-notes
Commit Message Convention
- feat: new feature
- fix: bug fix
- docs: documentation
- refactor: code restructuring
- test: adding tests
- chore: maintenance
Pitfalls
- Always check current branch before committing
- Pull before push to avoid conflicts
- Use --force-with-lease instead of --force
- Verify PR base branch is correct
Verification
- Confirm PR was created:
gh pr view <number> - Verify merge status:
gh pr status - Check CI status:
gh run list
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.