Git Workflow and Versioning
addyosmani/agent-skills
Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.
Steps for opening a pull request in the Fallout repo — picking the right base branch, creating it as a draft, applying the target/vCurrent-or-vNext and changelog-category labels, and handling…
$ npx skills add Fallout-build/Fallout --skill creating-a-pr -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Fallout-build/Fallout creating-a-pr --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Fallout-build/Fallout.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/creating-a-pr .claude/skills/creating-a-pr && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "creating-a-pr" agent skill from https://github.com/Fallout-build/Fallout/tree/develop/.agents/skills/creating-a-pr into .claude/skills/creating-a-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-a-pr", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Fallout-build/Fallout/tree/develop/.agents/skills/creating-a-prType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Fallout-build/Fallout --skill creating-a-pr -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Fallout-build/Fallout creating-a-pr --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Fallout-build/Fallout.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/creating-a-pr .agents/skills/creating-a-pr && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "creating-a-pr" agent skill from https://github.com/Fallout-build/Fallout/tree/develop/.agents/skills/creating-a-pr into .agents/skills/creating-a-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-a-pr", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Fallout-build/Fallout --skill creating-a-pr -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Fallout-build/Fallout creating-a-pr --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Fallout-build/Fallout.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/creating-a-pr .cursor/skills/creating-a-pr && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "creating-a-pr" agent skill from https://github.com/Fallout-build/Fallout/tree/develop/.agents/skills/creating-a-pr into .cursor/skills/creating-a-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-a-pr", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Fallout-build/Fallout.git --path .agents/skills/creating-a-pr--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Fallout-build/Fallout --skill creating-a-pr -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Fallout-build/Fallout creating-a-pr --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Fallout-build/Fallout.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/creating-a-pr .gemini/skills/creating-a-pr && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "creating-a-pr" agent skill from https://github.com/Fallout-build/Fallout/tree/develop/.agents/skills/creating-a-pr into .gemini/skills/creating-a-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-a-pr", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Fallout-build/Fallout creating-a-prInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Fallout-build/Fallout --skill creating-a-pr -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Fallout-build/Fallout.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/creating-a-pr .github/skills/creating-a-pr && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "creating-a-pr" agent skill from https://github.com/Fallout-build/Fallout/tree/develop/.agents/skills/creating-a-pr into .github/skills/creating-a-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-a-pr", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Fallout-build/Fallout --skill creating-a-pr -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Fallout-build/Fallout creating-a-pr --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Fallout-build/Fallout.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/creating-a-pr .opencode/skills/creating-a-pr && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "creating-a-pr" agent skill from https://github.com/Fallout-build/Fallout/tree/develop/.agents/skills/creating-a-pr into .opencode/skills/creating-a-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-a-pr", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
creating-a-prSteps for opening a pull request in the Fallout repo — picking the right base branch, creating it as a draft, applying the target/vCurrent-or-vNext and changelog-category labels, and handling…
Creating A PR is an agent skill from Fallout-build/Fallout. Steps for opening a pull request in the Fallout repo — picking the right base branch, creating it as a draft, applying the target/vCurrent-or-vNext and changelog-category labels, and handling breaking changes. Trigger whenever you are about to run gh pr create, decide a branch/base, write commit messages, or write a PR/issue description.
Its SKILL.md is about 820 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/pr-creation-flow.md`).
It sits in Development, covering Changelog and release notes, Commit messages and Pull requests. The repository describes itself as: ☢️ Fallout — The C/.NET Build System.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 8333cc8. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
gitghFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Creating A PR loads about 823 tokens when it runs, and up to ~1.4k if it reads all its reference files. Until then it costs about 89 tokens; SKILL.md has 364 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 364 words (~823 tokens).
“Follow this exactly when opening a PR. Don't skip the labelling — it's easy to drop because it's just flags on the same gh pr create call.”
SKILL.md and 1 other file (references) in .agents/skills/creating-a-pr of Fallout-build/Fallout.
Open the folder on GitHubat commit 8333cc8
Creating A PR next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Creating A PR this skillFallout-build/Fallout | 165 | — | ~823 | Automated safety check: Pass | Custom licence | |
| Git Workflow and Versioningaddyosmani/agent-skills | 103k | 2 repos | ~3.5k | Automated safety check: Notes | MIT | |
| Verdaccio Pull Request Workflowverdaccio/verdaccio | 18k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Commit And PR Messagessuperplanehq/superplane | 7.7k | — | ~1.6k | Automated safety check: Pass | Custom licence | |
| Plane Release Notes Generatormakeplane/plane | 61k | — | ~2.5k | Automated safety check: Pass | AGPL-3.0 | |
| PR Pushicebear0828/codex-proxy | 1.8k | — | ~2.2k | Automated safety check: Notes | Custom licence |
addyosmani/agent-skills
Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.
verdaccio/verdaccio
Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.
superplanehq/superplane
Write Git commit messages and pull request titles/descriptions using the Chris Beams / Tim Pope conventions (subject/body split, ~50-char subject, imperative mood, why-not-how body) plus ASD-STE100…
makeplane/plane
Builds categorized release notes for a Plane release pull request from its commits and writes them into the PR description, for both the plane-cloud and plane-ee repos.
icebear0828/codex-proxy
Package the current working changes into a standards-compliant codex-proxy pull request: branch hygiene, commit message linting, CHANGELOG prompt, conventional commit, push, and gh pr create against…
icebear0828/codex-proxy
Package the current working changes into a standards-compliant codex-proxy pull request: branch hygiene, commit message linting, CHANGELOG prompt, conventional commit, push, and gh pr create against…
Fallout-build/Fallout
Write clear, plain English for developer-facing prose aimed at an international audience.
Fallout-build/Fallout
How to mark a public API as not-yet-stable with [Experimental("FALLOUT0xx")], or deprecate one with [Obsolete(..., DiagnosticId = "FALLOUTOBS0xx")], including diagnostic-ID allocation.
Fallout-build/Fallout
Invariants to preserve when touching .github/workflows/, build/Build.CI.GitHubActions.cs, or anything about which branches/tags trigger CI or publish packages.
Fallout-build/Fallout
Restructure the commits on an existing PR into focused, reviewable commits
Fallout-build/Fallout
How to make fallout-migrate handle a new rename, removal, or rewrite by extending an existing IMigrationStep, and when a genuinely new step is warranted.
Fallout-build/Fallout
Procedure for tagging, publishing, promoting, or cutting a new release/vX.Y branch, hotfixing a production line, or cutting the eventual v11 major.
Categories
Steps for opening a pull request in the Fallout repo — picking the right base branch, creating it as a draft, applying the target/vCurrent-or-vNext and changelog-category labels, and handling…. Creating A PR is an agent skill from Fallout-build/Fallout. Steps for opening a pull request in the Fallout repo — picking the right base branch, creating it as a draft, applying the target/vCurrent-or-vNext and changelog-category labels, and handling breaking changes.
Creating A PR fits situations like: ever you are about to run gh pr create; decide a branch/base; write commit messages; write a PR/issue description.
Run `npx skills add Fallout-build/Fallout --skill creating-a-pr -a claude-code`. Or copy the skill folder (.agents/skills/creating-a-pr in Fallout-build/Fallout) into .claude/skills/creating-a-pr in your project. Claude Code loads it when a task matches its description.
Run `npx skills add Fallout-build/Fallout --skill creating-a-pr -a codex`. Or copy the skill folder (.agents/skills/creating-a-pr in Fallout-build/Fallout) into .agents/skills/creating-a-pr in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Fallout-build/Fallout --skill creating-a-pr -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/creating-a-pr, .gemini/skills/creating-a-pr, .github/skills/creating-a-pr and .opencode/skills/creating-a-pr in your project.
Going by SKILL.md and its folder, Creating A PR needs the command-line tools its instructions call (git and gh).
SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Creating A PR has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
About 823 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 597 tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Creating A PR: Git Workflow and Versioning (addyosmani/agent-skills, 103k stars), Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars), Commit And PR Messages (superplanehq/superplane, 7.7k stars) and Plane Release Notes Generator (makeplane/plane, 61k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Fallout-build (a GitHub organization) maintains it in Fallout-build/Fallout, which has 165 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 3, 2026.
Source: Fallout-build/Fallout on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.