git-github-workflow
Skill1 starsChanged 23 days agoApache-2.0View on GitHub
Perform Git or GitHub operations, including publication, branches, pull requests, and CI inspection.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- d-o-hub/github-template-ai-agentstheir own version, first seen Nov 3, 2026
- HyperVon/agent-guidance-kittheir own version, first seen Nov 1, 2026
- Flairstech-AIMY/coolify-skillstheir own version, first seen Sep 19, 2026
- yiweiwan/skillstheir own version, first seen May 12, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- d-o-hub/github-template-ai-agents★ 2same name
- HyperVon/agent-guidance-kit★ 1same name
- yiweiwan/skills★ 1same name
- Flairstech-AIMY/coolify-skills★ 0same name
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 repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- add-testSkill
- audit-fixissuesSkill
- autoresearchSkill
- benchmark-optimizeSkill
- circleci-job-resultsSkill
- citation-verifierSkill
- cli-designSkill
- codebase-auditSkill
- code-cleanupSkill
- deep-code-cleanupSkill
- doc-updateSkill
- emendSkill
- fix-issueSkill
- goal-modeSkill
- inspect-datasetSkill
- manage-pr-lifecycleSkill
- medcognetics-brandSkill
- notify-wakeSkill
- repo-maintenanceSkill
- review-fix-loopSkill
- standardize-ciSkill
- token-file-authSkill
- whats-nextSkill
- yeetSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use local git for checkout state, branches, staging, commits, and pushes.
- Very specific: line 9
Prefer the GitHub connector for remote operations.
- Distinctive: line 18
Ask before changing branch protection or its rulesets, or risking unrecoverable data or important history loss.
- Distinctive: line 48
Read only the relevant sections of Git procedures for publication, worktrees, review replies, or recovery.
“Common” is measured: kept by at least 6 in 10 of the 4 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
Git and GitHub Workflow
Use local git for checkout state, branches, staging, commits, and pushes.
Prefer the GitHub connector for remote operations. If it lacks the operation
or fails, use authenticated gh within existing authority.
Scope and Authorization
Task-related reads and writes on TidalPaladin and medcognetics have standing
authorization. Match owner names case-insensitively. Other owners require
authorization in the current request. Tool availability is not an approval gate.
Ask before changing branch protection or its rulesets, or risking unrecoverable data or important history loss. Also ask before direct workflow dispatch or rerun when a GitHub-hosted job is known to exceed 30 minutes. Self-hosted jobs and indirectly triggered workflows are exempt. Unknown runtime does not meet that condition. Protection reads are authorized.
Permission does not expand task scope. Loading this skill for a read does not authorize its default publication flow.
Explicit Invocation
A bare $git-github-workflow or $skill invocation requests commit, push,
and a draft pull request. Apply user modifiers:
| Modifier | Action |
commit only | Commit without pushing |
no pr | Commit and push |
push only | Push without committing |
pr only | Create or update the PR without committing or pushing |
For conflicting modifiers, use the most restrictive interpretation and state it.
Execution
Inspect current state before mutations. Preserve unrelated work and stage only
task files. Do not commit or push directly to main or master without
explicit authorization for the current task. Use new follow-up commits on
published branches. Do not rewrite published history without authorization.
Read only the relevant sections of Git procedures for publication, worktrees, review replies, or recovery. Use its required PR body format when publishing. For CI inspection or scheduled workflows, read Actions validation.
Complete the requested operations and verify their results. Run applicable repository gates before publication. Report unavailable checks accurately. Report commits, PRs, validation, and remaining blockers as relevant to the task.
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.