agentmods.dev

igniter-js: Command for GitHub Copilot

.github/prompts/create-conventional-commits.md

create-conventional-commits is a command for GitHub Copilot from felipebarcelospro/igniter-js. It costs 0 tokens per session (603 once invoked), scanned A, original, Apache-2.0.

A command that reviews staged and unstaged Git changes, groups them into logical units, and creates commit messages following the Conventional Commits format. Git is a version-control system, and a commit is a saved set of project changes.

In plain words
What is it for?
It is for turning working-directory changes into separate, focused Git commits with standard messages.
Why use it?
It helps keep mixed changes out of the same commit and makes the commit history more consistent and understandable.

Command for GitHub Copilot

Written for GitHub Copilot: a Copilot chat mode or prompt.

This is felipebarcelospro/igniter-js's own configuration. It tells GitHub Copilot how to work on igniter-js itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything igniter-js configures →

not rated 240repo 29d ago A scan 0 tokens original Apache-2.0
View source ↗ felipebarcelospro/igniter-js igniterjs.com
Reuse

Borrowing it

Nothing to install: this file belongs to felipebarcelospro/igniter-js. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/felipebarcelospro/igniter-js/main/.github/prompts/create-conventional-commits.md
Clone the repo
git clone --depth 1 https://github.com/felipebarcelospro/igniter-js

Made for: GitHub Copilot.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for create-conventional-commits

README.md
[![agentmods](https://agentmods.dev/badge/commands/felipebarcelospro/igniter-js/create-conventional-commits/github.svg)](https://agentmods.dev/commands/felipebarcelospro/igniter-js/create-conventional-commits)
Your own site
<a href="https://agentmods.dev/commands/felipebarcelospro/igniter-js/create-conventional-commits"><img src="https://agentmods.dev/badge/commands/felipebarcelospro/igniter-js/create-conventional-commits/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for create-conventional-commits

Your own site · 80×15
<a href="https://agentmods.dev/commands/felipebarcelospro/igniter-js/create-conventional-commits"><img src="https://agentmods.dev/badge/commands/felipebarcelospro/igniter-js/create-conventional-commits.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 603 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00603
Opus 5.5 $0.00000 $0.00241
Sonnet 5.5 $0.00000 $0.00121
Haiku 4.5 $0.00000 $0.00060

Measured 1mo ago against content hash 564cc3b5d9d6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

create-conventional-commits scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.github/prompts/create-conventional-commits.md · 46 lines

How it starts

The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Prompt: Generate Conventional Commits from All Working Directory Changes

Task Definition

The goal of this task is to analyze all unstaged and staged changes in the Git working directory, interactively group them into logical, atomic commits, stage them, and generate commit messages that strictly adhere to the Conventional Commits specification. This process should be repeated until the working directory is clean.

Step-by-Step Instructions

  1. Check Repository Status:

    • Run git status --porcelain to get a list of all modified, staged, and untracked files.
    • If the working directory is clean, inform the user and stop the process.

  2. Analyze and Propose First Logical Commit:

    • Review the list of all changed files and their diffs (git diff <file-path>).
    • Identify a small, cohesive set of changes that constitute a single logical unit of work (e.g., a single feature, a bug fix with its test). This will be the first proposed commit.
    • List the files you propose to include in this commit.

  3. Determine Commit Type and Scope:

    • For the proposed group of files, determine the primary type (e.g., feat, fix, docs, refactor, chore, etc.).
    • Determine the scope based on the location of the changed files (e.g., core, cli, adapter-redis, www, repo).

  4. Construct the Commit Message:

    • Follow the Conventional Commits v1.0.0 specification precisely.
    • Subject: type(scope): imperative-mood description
    • Body (Optional): Explain the "what" and "why".
    • Footer (Optional): Note any BREAKING CHANGE: and reference issues.

  5. Present for Approval:

    • Display a clear plan for the first commit:
      • The files to be staged (git add ...).
      • The fully formed git commit command.
    • Ask for explicit approval from the user to proceed with this single commit.

  6. Execute and Repeat:

    • Upon receiving approval, execute the git add and git commit commands for the proposed group.
    • After the commit is successful, return to Step 1 and repeat the entire process with the remaining changes.
    • Continue this loop until all changes have been committed and the working directory is clean.

Read the full file on GitHub · 46 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 46 lines · 0 tokens per session scan A 564cc3b5d9d6

Subscribe to this mod's changes

create-conventional-commits is a command published in the GitHub repository felipebarcelospro/igniter-js (240 stars, last pushed 29d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 603 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-27.

CommitsGit and workflowapiexpressfastifyframeworkhttpmiddleware
Related

create-conventional-commits compared with commands from other repositories

create-conventional-commits next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
create-conventional-commitsfelipebarcelospro/igniter-jsCommand24029d agoApache-2.0A0GitHub Copilot
gitstefan-jansen/claude-code-toolkitCommand924mo agoMITA12Claude Code
api-resource-shipgerard-labs/superpowers-api-platformCommand25mo agoMITA38Claude Code
gitazrtydxb/procoderCommand21111d agoApache-2.0A20Claude Code
session-reportdamusix/atomic-claudeCommand1154d agoMITA31Claude Code
git-workflowHermeticOrmus/LibreUIUX-Claude-CodeCommand1151mo agoMITA14Claude Code
commitjoaquimscosta/arkhe-claude-pluginsCommand2221d agoMITA11Claude Code