Git Commit Workflow

Use when the user wants a single clean commit created from current changes with safe staging, message drafting, and non-interactive git usage.

Security Scan

The skill's requirements and instructions align with its stated purpose (making a single safe git commit) and it does not request unrelated credentials, installs, or persistent privileges.

Purpose & Capability

Name/description ('single clean commit') match the instructions: inspect status/diff/branch, stage relevant files, draft message, and create one non-amended commit. No unrelated binaries, env vars, or config paths are requested.

Instruction Scope

SKILL.md limits runtime actions to repository-scoped operations (git status/diff/branch, staging, commit) and includes sensible guardrails (don't amend, don't bypass hooks, avoid staging secrets). It does not instruct reading arbitrary system files or external endpoints. It implicitly assumes the agent has access to the working tree, which is expected for this skill.

Install Mechanism

Instruction-only skill with no install spec and no code files; nothing will be downloaded or written to disk by an installer.

Credentials

No environment variables, credentials, or config paths are required. Requested inputs (current diff, branch state, commit style) are proportional to the task.

Persistence & Privilege

always is false and the skill does not request persistent presence or system-wide changes; autonomous invocation is allowed by default but is not combined with any broad privileges or credential access.

Assessment

This skill appears coherent and limited to git repo operations. Before using it, ensure you're running the agent in the intended repository (so it can't commit in the wrong project), verify the staged changes and generated commit message before finalizing, and avoid granting the agent access to repositories that contain secrets. If you need to enforce stricter checks, run the steps manually or require a user confirmation step before the final git commit.

Use this skill when the task is to create one commit from current work.

Workflow

1. Inspect git status, diff, branch, and recent commit style.
2. Stage only relevant changes.
3. Draft a concise commit message that reflects why the change exists.
4. Create a new commit non-interactively.
5. Report the resulting commit summary.

Guardrails

• Never amend unless explicitly asked.
• Never bypass hooks unless explicitly asked.
• Avoid staging secrets or unrelated files.
• Do not create an empty commit.

Example Requests

• Make one clean commit from the current working tree.
• Stage the right files and create a proper commit message.

Inputs

• Current diff
• Branch state
• Recent commit style

Outputs

• One non-amended commit
• Accurate commit message

Success Criteria

• Only relevant changes were committed.
• No empty commit was created.
• Hooks and safety rules were respected.

Non-Goals

• Amend flows unless explicitly asked
• Committing secrets or unrelated changes

Source Provenance

Derived from src/commands/commit.ts.