Skills Guide

Commit with User Prompts

VerifiedSafe

Creates git commits that include the user prompts from the conversation that led to the changes. Useful for preserving the context of why changes were made when committing. Automatically extracts relevant prompts and session metadata.

Download and use
Sby Skills Guide Bot
DevelopmentIntermediate
6/2/2026
Claude Code
#git#commit#version-control#prompts#changes

Recommended for

Backend developerClaude CodeCode reviewFrontend developerFullstack developerRefactoring

Automated summary

Creates Git commits that include the user prompts that led to the changes, along with session metadata.

Strengths

  • Preserves decision context in Git history
  • Automates collection of user prompts and session information
  • Enhances traceability of AI-assisted changes

Limitations

  • Requires the 'uv' tool to be installed and configured in the project
  • Works only in an interactive session with prompt history
  • May produce long messages if many prompts are involved
When to use it

Use this skill when you want to record in Git the conversational context that led to the changes.

When not to use it

Avoid using it for quick or trivial commits where context is unnecessary.

Security analysis

Safe
Quality score85/100

The skill uses git commands and a custom session-info script to create commits with user prompts. No destructive, exfiltrating, or obfuscated actions; all operations are standard version control tasks within the workspace.

No concerns found

How this analysis is made

Examples

Commit with prompts
Commit these changes with the user prompts that led to them.
Save work to Git
Save my work to git, including the conversation context.

name: commit description: Commit with user prompts from this conversation. Use when user mentions committing, wants to commit changes, asks to save their work to git, or says "commit this". allowed-tools: Bash, Read

Commit with User Prompts

Create git commits that include the user prompts that led to the changes.

Instructions

  1. Extract User Prompts: Collect user messages from this conversation that led to the changes. Include them in chronological order.

  2. Analyze Changes:

    git status
git diff --staged

  3. Get Session Info:

    uv run {baseDir}/ai-blame.py session-info

  4. Generate Commit Message:

    <brief summary of changes>

User prompts:
- "<first user prompt>"
- "<second user prompt>" (context if prompt is ambiguous)

AI-Session-ID: <from session-info>
AI Agent: <from session-info>
Model: <from session-info>

  5. Execute Commit:

    git add -A && git commit -m "$(cat <<'EOF'
<your commit message here>
EOF
)"

Rules

  • Only include prompts that led to file changes (not /commit or meta-discussion)
  • Preserve exact wording, add (context) in parentheses if prompt is ambiguous
  • Summary line under 50 characters
  • Each prompt on a single line, no mid-sentence wrapping

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/commit-with-user-prompts-mma3jrbo/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/commit-with-user-prompts-mma3jrbo' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/commit-with-user-prompts-mma3jrbo/download' --output '.skill-downloads/commit-with-user-prompts-mma3jrbo/SKILL.md.part' && mv '.skill-downloads/commit-with-user-prompts-mma3jrbo/SKILL.md.part' '.skill-downloads/commit-with-user-prompts-mma3jrbo/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Bash, Read

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/commit-with-user-prompts-mma3jrbo/SKILL.md' && test -s '.skill-downloads/commit-with-user-prompts-mma3jrbo/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/commit' && cp -R '.skill-downloads/commit-with-user-prompts-mma3jrbo' '.claude/skills/commit'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/commit-with-user-prompts-mma3jrbo'

openskills read 'commit-with-user-prompts-mma3jrbo'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/commit-with-user-prompts-mma3jrbo/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

React Hook Form Best Practices

Development

Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.

Claude CodeCursorWindsurf+2intermediateSafe 108,623
Skills Guide Bot

Emotion to Mantine Migration

Development

Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.

Claude CodeCursorWindsurf+1intermediateSafe 48,981
Skills Guide Bot

Scope Creep Detector

Development

Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.

Claude CodeCursorCodexintermediateSafe 135,015
Skills Guide Bot