prepare-commit

Stars2

Forks0

UpdatedApril 19, 2026 at 10:35

Use this skill when the user asks to prepare a commit, write a commit message, stage files, create a branch, or prepare PR notes for Signalist.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

thlaure

thlaure/Signalist

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	prepare-commit
description	Use this skill when the user asks to prepare a commit, write a commit message, stage files, create a branch, or prepare PR notes for Signalist.

Prepare Commit

Use this skill to prepare a commit and PR context without silently performing protected git actions.

Read first:

AGENTS.md
Makefile
frontend/package.json

Read as needed:

git status
git diff
git log

Workflow:

Inspect the current branch and working tree.
Stage the intended files with git add.
Run the repository quality checks relevant to the current change.
Review the change for correctness, architecture, validation, regressions, and test coverage.
Review the change with a security lens.
If the current branch is main, master, develop, or another protected/shared branch, create a dedicated working branch first.
Build a Conventional Commit title and optional body from the actual change.
Prepare PR-ready notes:
- what
- why
- how
- tests or verification
- risks or follow-up
Prepare a checkbox-style verification list using the repo's actual quality gates.
If the user explicitly asks to commit, ask for confirmation before running git commit.
If the user explicitly asks to push, ask for confirmation before running git push.

Rules:

Never commit or push without explicit confirmation in the current conversation.
Do not assume all changed files belong to the intended commit.
Keep the commit message human-readable and reviewer-friendly.
Prefer the repository's real verification commands over generic checklist items.
If pre-commit checks find blockers, report them before proposing the final commit.

More from this repository

same repository

bug-fix

thlaure/Signalist

Use this skill when the user reports broken behavior, errors, regressions, failing tests, or asks to fix a bug in Signalist.

2026-04-192

hotfix

thlaure/Signalist

Use this skill when the user describes a critical production issue that needs an immediate, minimal-risk fix in Signalist.

2026-04-192

improve-instructions

thlaure/Signalist

Use this skill when the user asks to improve agent instructions, update Claude or Codex guidance, review drift in AGENTS.md or .claude files, or keep the repo guidance aligned with how the project actually evolves.

2026-04-192

karpathy-guidelines

thlaure/Signalist

Use for bug fixes, refactors, reviews, or ambiguity-heavy implementation tasks to reinforce explicit assumptions, minimal diffs, simplicity, and direct verification.

2026-04-192

new-feature

thlaure/Signalist

Use this skill when the user asks to add, create, implement, or build new functionality in Signalist.

2026-04-192

review-change

thlaure/Signalist

Use this skill when the user asks for a code review, a correctness pass, a check before PR, or asks whether a Signalist change follows project conventions.

2026-04-192

name	prepare-commit
description	Use this skill when the user asks to prepare a commit, write a commit message, stage files, create a branch, or prepare PR notes for Signalist.

Prepare Commit

Use this skill to prepare a commit and PR context without silently performing protected git actions.

Read first:

AGENTS.md
Makefile
frontend/package.json

Read as needed:

git status
git diff
git log

Workflow:

Inspect the current branch and working tree.
Stage the intended files with git add.
Run the repository quality checks relevant to the current change.
Review the change for correctness, architecture, validation, regressions, and test coverage.
Review the change with a security lens.
If the current branch is main, master, develop, or another protected/shared branch, create a dedicated working branch first.
Build a Conventional Commit title and optional body from the actual change.
Prepare PR-ready notes:
- what
- why
- how
- tests or verification
- risks or follow-up
Prepare a checkbox-style verification list using the repo's actual quality gates.
If the user explicitly asks to commit, ask for confirmation before running git commit.
If the user explicitly asks to push, ask for confirmation before running git push.

Rules:

Never commit or push without explicit confirmation in the current conversation.
Do not assume all changed files belong to the intended commit.
Keep the commit message human-readable and reviewer-friendly.
Prefer the repository's real verification commands over generic checklist items.
If pre-commit checks find blockers, report them before proposing the final commit.