git-delivery
Skill13 starsChanged 4 days agoMITView on GitHub
Commit, push, and release with Conventional Commits; branches, worktrees, conflicts, and hook fixes.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- fmind/dotword for word, first seen Nov 8, 2026
- TylerAkins/ai-agent-skillstheir own version, first seen Oct 15, 2026
- z-Zihan/Evirtheir own version, first seen Oct 13, 2026
Other versions3 projects use a version of this.
Word for word · 1
- fmind/dot★ 13100% same
Edited · 0
None found.
Wrote their own version · 2
- z-Zihan/Evir★ 11same name
- TylerAkins/ai-agent-skills★ 1same 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 repository67 other files it gives its agents.
- AGENTS.mdAGENTS.md
- dot_agents/AGENTS.mdAGENTS.md
- skills/repository-docs/references/agents.mdAGENTS.md
- chezmoiSkill
- dot-developmentSkill
- dot-releaseSkill
- dot-skillsSkill
- dot-verifySkill
- acliSkill
- agent-evaluationSkill
- agent-frameworksSkill
- agent-harnessesSkill
- agent-projectSkill
- agent-protocolsSkill
- agySkill
- airflowSkill
- auth-statusSkill
- awsSkill
- bfSkill
- chrome-devtoolsSkill
- clipboardSkill
- cloud-runSkill
- code-securitySkill
- colabSkill
- databricksSkill
- diagrams-as-codeSkill
- dockerSkill
- documentation-siteSkill
- dot-cliSkill
- dprintSkill
- draft-docSkill
- draft-mailSkill
- duckdbSkill
- fmind-visualsSkill
- full-reviewSkill
- gcloudSkill
- ghSkill
- github-actionsSkill
- github-issuesSkill
- github-pull-requestSkill
- github-repositorySkill
- google-developerSkill
- gwsSkill
- hfSkill
- infra-as-codeSkill
- kaggleSkill
- kubernetesSkill
- lesson-learnedSkill
- mcp-setupSkill
- miseSkill
- model-providersSkill
- playwrightSkill
- project-scaffoldingSkill
- python-mlopsSkill
- python-stackSkill
- python-webSkill
- repository-docsSkill
- scheduled-jobsSkill
- skillifySkill
- <name>Skill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
Follow requested branch and release modes: if the user requests a branch or PR, follow git-worktree and github-pull-request.
- Distinctive: line 27
Commit only the staged selection: never auto-stage unrelated changes.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Git Delivery
Deliver only the authorized changes while preserving the index, branch intent, and enabled hooks. Branching, pushing, and release publication are separate modes of the same workflow.
Workflow
- Resolve delivery authority and target branch: take both from the request; inspect the current branch and unmerged work before switching. Never overwrite an existing branch or move unrelated commits. History investigation is read-only: fetch missing objects into an isolated clone and bisect in a disposable worktree; pulling into the working tree or rewriting history needs authority.
- Match work to the request: a commit-only request preserves the staged selection and stops after committing. A delivery request includes staging and pushing only its intended changes; neither implies release publication.
- Follow requested branch and release modes: if the user requests a branch or PR, follow git-worktree and github-pull-request. A later release instruction selects the release mode; use the repository's native release task where present.
- Verify the delivery: the exact commit, remote destination, and requested publication level. Keep published tags immutable and preserve enabled hooks.
Commit messages
- Write one Conventional Commits subject:
<type>(<scope>): <description>with typefeat,fix,chore,docs,refactor,test,perf,ci,build,style, orrevert; imperative, under 72 characters,!after the type or scope for a breaking change, and no AI attribution or co-author trailers. - Commit only the staged selection: never auto-stage unrelated changes; on a hook failure or an empty index, report it and do not amend.
Task guides
<!-- guides:start -->- git-add-commit-push: Stage, commit, push, and recover hook failures within the authorized scope.
- git-worktree: Create Git branches, worktrees, or isolated snapshots of uncommitted work.
- release: Prepare, publish when requested, or verify versioned releases.
- resolve-conflicts: Resolve Git merge or rebase conflicts by both sides' intent; verify the result.
<!-- guides:end -->Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.