Publish Pull Request for taskctl
taskctl/taskctl
Publishes the current branch and opens or updates a GitHub pull request for the taskctl repo, after a pre-publish gate and with a description template matched to the change.
Creates Conventional Commit messages and matching pull-request titles and branch names.
Install Conventional Git
$ npx skills add blackfyre/wga --skill conventional-git -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install blackfyre/wga conventional-git --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/blackfyre/wga.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/conventional-git .claude/skills/conventional-git && 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 "conventional-git" agent skill from https://github.com/blackfyre/wga/tree/main/.agents/skills/conventional-git into .claude/skills/conventional-git/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conventional-git", 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/blackfyre/wga/tree/main/.agents/skills/conventional-gitType 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 blackfyre/wga --skill conventional-git -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install blackfyre/wga conventional-git --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/blackfyre/wga.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/conventional-git .agents/skills/conventional-git && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "conventional-git" agent skill from https://github.com/blackfyre/wga/tree/main/.agents/skills/conventional-git into .agents/skills/conventional-git/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conventional-git", 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 blackfyre/wga --skill conventional-git -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install blackfyre/wga conventional-git --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/blackfyre/wga.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/conventional-git .cursor/skills/conventional-git && 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 "conventional-git" agent skill from https://github.com/blackfyre/wga/tree/main/.agents/skills/conventional-git into .cursor/skills/conventional-git/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conventional-git", 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/blackfyre/wga.git --path .agents/skills/conventional-git--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 blackfyre/wga --skill conventional-git -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install blackfyre/wga conventional-git --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/blackfyre/wga.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/conventional-git .gemini/skills/conventional-git && 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 "conventional-git" agent skill from https://github.com/blackfyre/wga/tree/main/.agents/skills/conventional-git into .gemini/skills/conventional-git/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conventional-git", 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 blackfyre/wga conventional-gitInstalls 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 blackfyre/wga --skill conventional-git -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/blackfyre/wga.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/conventional-git .github/skills/conventional-git && 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 "conventional-git" agent skill from https://github.com/blackfyre/wga/tree/main/.agents/skills/conventional-git into .github/skills/conventional-git/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conventional-git", 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 blackfyre/wga --skill conventional-git -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install blackfyre/wga conventional-git --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/blackfyre/wga.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/conventional-git .opencode/skills/conventional-git && 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 "conventional-git" agent skill from https://github.com/blackfyre/wga/tree/main/.agents/skills/conventional-git into .opencode/skills/conventional-git/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conventional-git", 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.
Facts
- Skill name
conventional-git- GitHub stars
- 194
- Token cost
- ~843 tokens
- SKILL.md length
- 389 words
- Files
- 1
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Creates Conventional Commit messages and matching pull-request titles and branch names.
- Works in 4 steps: Confirm the type matches the diff and… → Check that the subject and branch… → Confirm the PR title begins with one of… → …
- Preparing a commit
- SKILL.md covers Guardrails, Type, Commit and Pull-Request Title and Branch Name, plus 1 more section
- Calls git
What it does
Conventional Git is an agent skill from blackfyre/wga. Creates Conventional Commit messages and matching pull-request titles and branch names. Use when preparing a commit, pull request, or branch.
Its SKILL.md is about 840 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Pull requests, Commit messages and Git workflow. It works with Git and Go. The repository describes itself as: Jumping forward ~30 years. The licence is Apache-2.0.
When your agent uses it
- Preparing a commit
- Tasks that involve Pull requests
- Tasks that involve Commit messages
Example prompts
- “Use the conventional-git skill to create Conventional Commit messages and matching pull-request titles and branch names”
- “/conventional-git”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Confirm the type matches the diff and repository conventions.
- Check that the subject and branch summary describe the same outcome.
- Confirm the PR title begins with one of the repository-approved types.
- When the user asks only for suggestions, provide a proposed branch, commit, and PR title without running Git write operations.
What it can do on your machine
Read from SKILL.md and the folder at commit 8686358. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Conventional Git loads about 843 tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 389 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.
Safety
Auto-check passed
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.
SKILL.md
The full file from blackfyre/wga at commit 8686358, republished under its Apache-2.0 licence (© blackfyre). 389 words, ~843 tokens.
Download SKILL.mdSave it as
.claude/skills/conventional-git/SKILL.md (or your agent's skills folder).- name
- conventional-git
- description
- Creates Conventional Commit messages and matching pull-request titles and branch names. Use when preparing a commit, pull request, or branch.
Conventional Git Naming
Use this skill when proposing or creating a branch, commit, or pull request.
Guardrails
- Derive the name from the actual, intended change. Inspect
git status, the relevant diff, and recent log messages before naming it. - Do not create, commit, push, or switch branches unless the user explicitly requests that operation.
- Keep one commit focused on one coherent change. Split unrelated changes instead of hiding them behind a broad subject.
- Never include credentials, tokens, private URLs, or sensitive personal data in a branch name, commit subject, or pull-request title.
Type
Choose the narrowest supported Conventional Commit type:
| Type | Use for |
|---|---|
feat | New user-facing capability |
fix | Correcting faulty behaviour |
docs | Documentation only |
test | Tests only |
ci | Continuous-integration configuration |
refactor | Internal restructuring with unchanged behaviour |
perf | Measurable performance improvement |
chore | Maintenance not covered above |
revert | Reverting an earlier change |
build | Build system or dependency tooling |
This repository validates pull-request types against exactly this list.
Commit and Pull-Request Title
Use the same conventional subject for the commit and PR title unless the PR deliberately groups several independently named commits:
<type>(<optional-scope>): <imperative, lower-case summary>- Omit the scope unless it makes the affected area materially clearer.
- Start the summary with a verb, use lower case, avoid a trailing full stop, and keep it concise.
- State the outcome, not the implementation detail or ticket number.
- Use
!after the type or scope only for a deliberate breaking change; explain it in the commit body or PR description.
Examples:
feat(tours): add guided tour landing page
fix(postcard): preserve delivery retry state
docs: clarify local development setup
build: update frontend asset pipelineFor an issue-backed change, put the issue reference in the PR description or commit body unless the repository's established local convention requires it in the subject.
Show full SKILL.md (124 more words)Show less
Branch Name
Use a lower-case, slash-separated name:
<type>/<short-kebab-case-summary>Optionally prefix the summary with an issue identifier when one is authoritative:
<type>/<issue-id>-<short-kebab-case-summary>Examples:
feat/guided-tour-landing-page
fix/197-postcard-retry-state
docs/local-development-setup- Use the same type as the eventual commit and PR where practical.
- Keep the summary brief, specific, and free of dates, usernames, spaces, underscores, and punctuation.
- Do not use
main,master, release names, or a branch name that suggests completed work for an unfinished change.
Before Reporting or Creating
- Confirm the type matches the diff and repository conventions.
- Check that the subject and branch summary describe the same outcome.
- Confirm the PR title begins with one of the repository-approved types.
- When the user asks only for suggestions, provide a proposed branch, commit, and PR title without running Git write operations.
© blackfyre, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/conventional-git of blackfyre/wga.
Open the folder on GitHubat commit 8686358
Compare with similar skills
Conventional Git 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 |
|---|---|---|---|---|---|---|
| Conventional Git this skillblackfyre/wga | 194 | — | ~843 | Automated safety check: Pass | Apache-2.0 | |
| Publish Pull Request for taskctltaskctl/taskctl | 434 | — | ~979 | Automated safety check: Pass | GPL-3.0 | |
| Git Workflow and Versioningaddyosmani/agent-skills | 103k | 2 repos | ~3.5k | Automated safety check: Notes | MIT | |
| React Router Pull Request Creatorremix-run/react-router | 57k | — | ~2.5k | Automated safety check: Pass | MIT | |
| Emoji Commit ConventionsbaptisteArno/typebot.io | 11k | — | ~424 | Automated safety check: Pass | Custom licence | |
| Draft Pull Request Creatorwordpress-mobile/WordPress-Android | 3.2k | — | ~881 | Automated safety check: Notes | GPL-2.0 |
Similar skills
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.
React Router Pull Request Creator
remix-run/react-router
Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.
Emoji Commit Conventions
baptisteArno/typebot.io
Sets the repository's convention for commit messages and pull request titles: one emoji prefix for the main intent, a concise title and clean follow-up commits.
Draft Pull Request Creator
wordpress-mobile/WordPress-Android
Commits and pushes current changes, writes a pull request title and body from the branch history and template, and opens a draft PR on GitHub after you approve it.
- Official
Adk Git
google/adk-python
Writes commit messages and pull request descriptions for the adk-python repository: Conventional Commits types and scopes, subject lines that say why a change was made, and the linked-issue and…
More from blackfyre/wga
Htmx
blackfyre/wga
Implements HTMX interactions, configures swap behaviors, debugs hx- requests, and builds hypermedia-driven UI components.
Design Intake
blackfyre/wga
Turns new entries in the WGA Claude Design changelog into proposed OpenSpec changes, and checks implemented UI against the live prototype.
Related
Categories
Questions about Conventional Git
What does Conventional Git do?
Creates Conventional Commit messages and matching pull-request titles and branch names. Conventional Git is an agent skill from blackfyre/wga. Creates Conventional Commit messages and matching pull-request titles and branch names.
When should I use Conventional Git?
Conventional Git fits situations like: preparing a commit; tasks that involve Pull requests; tasks that involve Commit messages.
How do I install Conventional Git in Claude Code?
Run `npx skills add blackfyre/wga --skill conventional-git -a claude-code`. Or copy the skill folder (.agents/skills/conventional-git in blackfyre/wga) into .claude/skills/conventional-git in your project. Claude Code loads it when a task matches its description.
How do I install Conventional Git in Codex?
Run `npx skills add blackfyre/wga --skill conventional-git -a codex`. Or copy the skill folder (.agents/skills/conventional-git in blackfyre/wga) into .agents/skills/conventional-git in your project. Codex loads it when a task matches its description.
Can I use Conventional Git in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add blackfyre/wga --skill conventional-git -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/conventional-git, .gemini/skills/conventional-git, .github/skills/conventional-git and .opencode/skills/conventional-git in your project.
What does Conventional Git need to run?
Going by SKILL.md and its folder, Conventional Git needs the command-line tools its instructions call (git).
Does Conventional Git access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Conventional Git safe to install?
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.
What licence does Conventional Git use?
Conventional Git is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Conventional Git use?
About 843 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Conventional Git?
Skills that share tags, products or a category with Conventional Git: Publish Pull Request for taskctl (taskctl/taskctl, 434 stars), Git Workflow and Versioning (addyosmani/agent-skills, 103k stars), React Router Pull Request Creator (remix-run/react-router, 57k stars) and Emoji Commit Conventions (baptisteArno/typebot.io, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Conventional Git?
blackfyre (a GitHub user) maintains it in blackfyre/wga, which has 194 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 5, 2026.
Source: blackfyre/wga on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.