Agent skill

Commit

Stage and commit uncommitted changes with conventional commit messages.

MITAuto-check: notesDevelopment

Install Commit

skills CLI

$ npx skills add TyrealQ/q-skills --skill commit -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install TyrealQ/q-skills commit --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/TyrealQ/q-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/commit .claude/skills/commit && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "commit" agent skill from https://github.com/TyrealQ/q-skills/tree/main/skills/commit into .claude/skills/commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit", 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

$skill-installer install https://github.com/TyrealQ/q-skills/tree/main/skills/commit

Type 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.

skills CLI

$ npx skills add TyrealQ/q-skills --skill commit -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install TyrealQ/q-skills commit --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/TyrealQ/q-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/commit .agents/skills/commit && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "commit" agent skill from https://github.com/TyrealQ/q-skills/tree/main/skills/commit into .agents/skills/commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit", 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.

skills CLI

$ npx skills add TyrealQ/q-skills --skill commit -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install TyrealQ/q-skills commit --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/TyrealQ/q-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/commit .cursor/skills/commit && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "commit" agent skill from https://github.com/TyrealQ/q-skills/tree/main/skills/commit into .cursor/skills/commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit", 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

$ gemini skills install https://github.com/TyrealQ/q-skills.git --path skills/commit

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add TyrealQ/q-skills --skill commit -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install TyrealQ/q-skills commit --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/TyrealQ/q-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/commit .gemini/skills/commit && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "commit" agent skill from https://github.com/TyrealQ/q-skills/tree/main/skills/commit into .gemini/skills/commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit", 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.

GitHub CLI

$ gh skill install TyrealQ/q-skills commit

Installs 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).

skills CLI

$ npx skills add TyrealQ/q-skills --skill commit -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/TyrealQ/q-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/commit .github/skills/commit && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "commit" agent skill from https://github.com/TyrealQ/q-skills/tree/main/skills/commit into .github/skills/commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit", 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.

skills CLI

$ npx skills add TyrealQ/q-skills --skill commit -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install TyrealQ/q-skills commit --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/TyrealQ/q-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/commit .opencode/skills/commit && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "commit" agent skill from https://github.com/TyrealQ/q-skills/tree/main/skills/commit into .opencode/skills/commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit", 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: commit
GitHub stars: 108
Token cost: ~1.1k tokens
SKILL.md length: 503 words
Files: 1
Skills in repo: 16
Repo updated: Sep 23, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Stage and commit uncommitted changes with conventional commit messages.

Works in 7 steps: Review changes → Analyze changes and verify consistency → Decide commit strategy → …
Committing changes
Calls git
Grouping commits by topic

What it does

Commit is an agent skill from TyrealQ/q-skills. Stage and commit uncommitted changes with conventional commit messages. Use for committing changes or grouping commits by topic.

Its SKILL.md is about 1.1k 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 Commit messages. The repository describes itself as: End-to-end skills for academic writing, data analysis, teaching, and research communication. The licence is MIT.

When your agent uses it

Committing changes
Grouping commits by topic

Example prompts

“/commit”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

Review changes
Analyze changes and verify consistency
Decide commit strategy
Generate commit message
Stage and commit
Cleanup temp files
Confirm

What it can do on your machine

Read from SKILL.md and the folder at commit d8aaee7. 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

Commit loads about 1.1k tokens when it runs. Until then it costs about 34 tokens; SKILL.md has 503 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~34
When it runs · the whole SKILL.md, loaded when a task matches: ~1.1k

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NoteMentions a .env fileSKILL.md:90

es that likely contain secrets, such as `.env` or `credentials.json`, from staging unless the user explicitly asks to in

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 TyrealQ/q-skills at commit d8aaee7, republished under its MIT licence (© TyrealQ). 503 words, ~1,103 tokens.

Download SKILL.mdSave it as .claude/skills/commit/SKILL.md (or your agent's skills folder).

name: commit
description: Stage and commit uncommitted changes with conventional commit messages. Use for committing changes or grouping commits by topic.

Git Commit Skill

Stages and commits uncommitted changes with conventional commit messages. Groups files by topic when multiple unrelated changes are pending, runs cascade and CLAUDE.md freshness checks, and sweeps temp files after each commit. Does not push — hand off to /ship for that.

Workflow

Step 1: Review changes

Run both commands to get the full picture:

git status --short
git diff --cached --name-status

git status --short shows unstaged modifications and untracked files. git diff --cached catches files that are already staged but not yet committed. Use the union of both outputs.

If both commands return empty, report "nothing to commit" and stop.

Classify each change:

M — modified, ?? — untracked, D — deleted, R — renamed, A — staged new file

Step 2: Analyze changes and verify consistency

Classify file paths

Path pattern	Type
`posts/`, `articles/`, `content/`	content/writing
`.claude/skills/`	skill config
`src/`, `.go`, `.py`, `.ts`, `.R`, `*.r`	code/scripts
`*.md`	documentation
`.json`, `.yaml`, `.toml`, `.csv`	config/data

Cascade check (skip if no scripts or data files changed)

If any modified files are scripts or data files:

Identify downstream files: Find all markdown reports, appendices, and documentation that reference outputs or data from the modified files — search for filename references, table headers, variable names, and output patterns
Verify consistency: Check that numbers, table data, file paths, and cross-references in downstream files match the current state of the modified scripts and their outputs
Fix discrepancies: Update any stale numbers, outdated references, or mismatched data in downstream files. Include these fixes in the commit

CLAUDE.md freshness (always run)

If the working directory has a CLAUDE.md, read it and compare against the current project state — not just the changes being committed, but also decisions made during the session, new or renamed files on disk, and structural changes. Update CLAUDE.md before proceeding if any section reflects outdated state.

Show full SKILL.md (213 more words)Show less

Step 3: Decide commit strategy

Single topic: one commit for all files
Multiple topics: group by directory/topic, one commit per group

Grouping priority:

Content (one commit per article/document unit)
Skills (one commit per skill)
Code changes (group by module)
Config files (group together)

Step 4: Generate commit message

Follow conventional commits format from rules/git-workflow.md:

<type>: <description>

Types: feat, fix, refactor, docs, test, chore, perf, ci

Examples:

docs: add exploratory analysis notebook
feat: add batch processing to pipeline
fix: correct citation formatting in report
chore: update project config

Keep descriptions concise (under 70 chars).

Step 5: Stage and commit

git add <file1> <file2> ...
git commit -m "<message>"

Rules:

Specify files explicitly — never use git add . or git add -A
Exclude temp files (*.bak-*, .DS_Store, node_modules/)
Exclude test scaffolding (tests/, test_*.py) from repos that ship as shared/public artifacts unless the user asks to include it
Exclude files that likely contain secrets, such as .env or credentials.json, from staging unless the user explicitly asks to include them

Step 6: Cleanup temp files

After the commit succeeds, remove these patterns from the working tree (skip .git/):

Files: *.bak-*, *.pyc, *.pyo, *.swp, *.swo, *~, .DS_Store, Thumbs.db
Directories: __pycache__/, .pytest_cache/, .mypy_cache/, .ruff_cache/

List matches first, then delete. If nothing matches, note "no temp files to clean" and proceed.

find . -not -path '*/.git/*' -type f \( -name '*.bak-*' -o -name '*.pyc' -o -name '*.pyo' -o -name '*.swp' -o -name '*.swo' -o -name '*~' -o -name '.DS_Store' -o -name 'Thumbs.db' \) -print -exec rm -f {} +
find . -not -path '*/.git/*' -type d \( -name '__pycache__' -o -name '.pytest_cache' -o -name '.mypy_cache' -o -name '.ruff_cache' \) -print -exec rm -rf {} +

Step 7: Confirm

Run: git log --oneline -3

Files

Just SKILL.md in skills/commit of TyrealQ/q-skills.

Open the folder on GitHubat commit d8aaee7

Compare with similar skills

Commit 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.

Commit compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Commit this skillTyrealQ/q-skills	108	—	~1.1k	Automated safety check: Notes	MIT	13 days ago
Contextual Commit Messagesyamadashy/repomix	29k	1 repos	~2.7k	Automated safety check: Pass	MIT	4 days ago
React Router Release Notes Prepremix-run/react-router	57k	—	~1.1k	Automated safety check: Pass	MIT	today
PR Finalize Reviewmicrosoft/garnet	12k	—	~3.1k	Automated safety check: Pass	MIT	today
Caveman Commitvishiri/fantasia-archive	409	13 repos	~642	Automated safety check: Pass	GPL-3.0	6 days ago
ToolJet Multi-Repo CommitToolJet/ToolJet	41k	—	~1.3k	Automated safety check: Pass	AGPL-3.0	today

Similar skills

Contextual Commit Messages
yamadashy/repomix
Writes Conventional Commits whose bodies carry action lines recording the intent, decisions and constraints behind a change, not only what changed.
29k GitHub starsUsed in 1 repo~2.7k tokens
DevelopmentAuto-check passed
React Router Release Notes Prep
remix-run/react-router
Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.
57k GitHub stars~1.1k tokensUpdated today
DevelopmentAuto-check passed
PR Finalize Review
microsoft/garnet
Official
Checks that a pull request's title and description match its implementation and reviews the code for Garnet best practices, reporting findings without posting them.
12k GitHub stars~3.1k tokensUpdated today
DevelopmentAuto-check passed
Caveman Commit
vishiri/fantasia-archive
Ultra-compressed commit message generator. An agent skill from vishiri/fantasia-archive.
409 GitHub starsUsed in 13 repos~642 tokens
DevelopmentAuto-check passed
ToolJet Multi-Repo Commit
ToolJet/ToolJet
Commits changes across ToolJet's root repo and its server/ee and frontend/ee submodules, writing messages from the diffs and updating submodule pointers in order.
41k GitHub stars~1.3k tokensUpdated today
DevelopmentAuto-check passed
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.
102k GitHub starsUsed in 2 repos~3.5k tokens
DevelopmentAuto-check: notes

More from TyrealQ/q-skills

All 16 skills in this repo

Q-Infographics
TyrealQ/q-skills
Converts a report or other document into a business story and then an infographic image, pausing for your review after each step.
108 GitHub stars~814 tokensUpdated 13 days ago
Auto-check: notes
Q-EDA Exploratory Analysis
TyrealQ/q-skills
Runs exploratory data analysis on tabular data after you confirm each column's measurement level, then writes CSV tables and a narrative summary.
108 GitHub stars~1.1k tokensUpdated 13 days ago
Auto-check passed
Multimodal Media Feature Extraction
TyrealQ/q-skills
Extracts pixel, video-frame, speech, music and visual-semantic features from image, video and audio files for research datasets, using local tools or the Gemini API.
108 GitHub stars~2k tokensUpdated 13 days ago
Auto-check: notes
Topic Model Consolidation
TyrealQ/q-skills
Consolidates BERTopic, LDA or NMF topic output into a theory-driven classification framework and writes the final labels back to an Excel file.
108 GitHub stars~1k tokensUpdated 13 days ago
Auto-check passed
Q-Presentations Slide Deck Generator
TyrealQ/q-skills
Generates branded slide deck images from written content, with a content analysis step, a layout catalog and scripts that merge the slides into PowerPoint or PDF.
108 GitHub stars~1.1k tokensUpdated 13 days ago
Auto-check passed
Repository Layout and Docs Auditor
TyrealQ/q-skills
Audits a repository's file layout and project documentation against a written convention file, then proposes moves, deletions and doc fixes as an approved plan before touching anything.
108 GitHub stars~4.4k tokensUpdated 13 days ago
Auto-check: notes

Questions about Commit

What does Commit do?

Stage and commit uncommitted changes with conventional commit messages. Commit is an agent skill from TyrealQ/q-skills. Stage and commit uncommitted changes with conventional commit messages.

When should I use Commit?

Commit fits situations like: committing changes; grouping commits by topic.

How do I install Commit in Claude Code?

Run `npx skills add TyrealQ/q-skills --skill commit -a claude-code`. Or copy the skill folder (skills/commit in TyrealQ/q-skills) into .claude/skills/commit in your project. Claude Code loads it when a task matches its description.

How do I install Commit in Codex?

Run `npx skills add TyrealQ/q-skills --skill commit -a codex`. Or copy the skill folder (skills/commit in TyrealQ/q-skills) into .agents/skills/commit in your project. Codex loads it when a task matches its description.

Can I use Commit 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 TyrealQ/q-skills --skill commit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/commit, .gemini/skills/commit, .github/skills/commit and .opencode/skills/commit in your project.

What does Commit need to run?

Going by SKILL.md and its folder, Commit needs the command-line tools its instructions call (git).

Does Commit 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 Commit safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Commit use?

Commit is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Commit use?

About 1.1k tokens (SKILL.md is roughly 4.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 Commit?

Skills that share tags, products or a category with Commit: Contextual Commit Messages (yamadashy/repomix, 29k stars), React Router Release Notes Prep (remix-run/react-router, 57k stars), PR Finalize Review (microsoft/garnet, 12k stars) and Caveman Commit (vishiri/fantasia-archive, 409 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Commit?

TyrealQ (a GitHub user) maintains it in TyrealQ/q-skills, which has 108 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on September 23, 2026.

Source: TyrealQ/q-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Commit

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Git Commit Skill

Workflow

Step 1: Review changes

Step 2: Analyze changes and verify consistency

Classify file paths

Cascade check (skip if no scripts or data files changed)

CLAUDE.md freshness (always run)

Step 3: Decide commit strategy

Step 4: Generate commit message

Step 5: Stage and commit

Step 6: Cleanup temp files

Step 7: Confirm

Files

Compare with similar skills

Similar skills

More from TyrealQ/q-skills

Related

Questions about Commit