Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

Commit

ASecurity

Selectively stages and commits only the changes related to the current session, skipping unrelated modifications.

477 stars
0 votes
0 copies
0 views
Added 9/22/2026
ai-agentsgit

Security Analysis

A100/100

Scanned 9/22/2026

Install to Claude Code

$npx -y skills add greenfield-inc/Pane --skill commit --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Commit?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Commit
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/greenfield-inc-commit-pane/badge)](https://www.skillsdirectory.com/skills/greenfield-inc-commit-pane)

More formats (shields.io, HTML) on the badges page.

Download Zip
Files
SKILL.md
---
name: commit
description: Selectively stages and commits only the changes related to the current session, skipping unrelated modifications.
argument-hint: "[optional: commit message or description of what to commit]"
---

# Commit Agent

Commit only the changes made in the current session to the local branch. Ignore
all other changes. Do not ask for confirmation at each step; classify, stage,
commit, and report.

## Step 1: Understand What Was Done

1. Check for plans in `./tmp/done-plans/` and `./tmp/ready-plans/`
2. If no plans exist, use the conversation history to understand the scope
3. If `$ARGUMENTS` is provided and is not already a `type: description` commit
   message, use it as extra classification context

## Step 2: Inspect All Changes

1. Run `git status`
2. Run `git diff` and `git diff --cached`
3. If there are no changes, stop and say so

## Step 3: Classify Changes

Include:
- files explicitly created or edited during this session
- files referenced by the implemented plan
- supporting changes clearly tied to the work
- relevant `./tmp/done-plans/` files and related context artifacts

Exclude:
- files not touched in this session
- pre-existing unrelated modifications
- unrelated changes from other agents or manual edits
- unrelated `./tmp/` files

When in doubt, include the file rather than leaving it out.

If zero files are clearly in scope, stop and say so.

## Step 4: Stage and Verify

1. Stage only specific in-scope files
2. Never use `git add .` or `git add -A`
3. Review the staged diff for secrets or credentials
4. If secrets are found, unstage them and ask the user how to proceed

## Step 5: Create the Commit

1. If `$ARGUMENTS` already matches `type: description`, use it verbatim
2. Otherwise derive a concise conventional commit message
3. Keep the subject under 72 characters
4. Add a short body when the commit covers multiple logical changes
5. Create the local commit and do not push

## Step 6: Report

Report:
- commit sha and subject
- files included
- files intentionally left uncommitted
- suggest `/prepare-pr` if appropriate

Attribution

greenfield-incgreenfield-inc
View sourceMore from greenfield-inc →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1066601 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

686011 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

651 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →