code-commit

Stage files, run tests, and commit with a standardized prefix and diff summary.

7|1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/Shiien/Self-Evolved-Research-Framework --skill code-commit-shiien
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-commit
Source: https://github.com/Shiien/Self-Evolved-Research-Framework/tree/main/skills/code-commit
Command: npx skills add https://github.com/Shiien/Self-Evolved-Research-Framework --skill code-commit-shiien

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Committing code only after it passes a full test suite and pre-commit verification, ensuring validated changes, traceable messages, and consistent workflows.

Core Features & Use Cases

  • Pre-commit verification: Run the complete test suite and per-criterion checks before committing.
  • Commit preparation: Generate a standardized commit message per git-conventions rules and present a diff summary.
  • Workflow integration: Stage specified files and, if driven by a checklist, update the checklist with the commit SHA.

Quick Start

Run the code-commit workflow immediately after code review to validate and commit changes.

Frequently Asked Questions about code-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate git commits to only run after passing tests and pre-commit verification?▼

To automate git commits with pre-commit verification, trigger the workflow after code review. It runs a full test suite, stages files, generates a diff summary, and applies a standardized commit prefix to ensure validated changes.

What is the best way to generate standardized commit messages with a diff summary?▼

Generating standardized commit messages with a diff summary requires applying git-conventions rules. The workflow stages specified files, chooses a prefix based on intention, and presents the diff summary for final validation.

Can I update an associated checklist with the commit SHA automatically?▼

Yes, you can update an associated checklist with the commit SHA automatically. When driven by a checklist workflow, the commit process appends the generated SHA to maintain traceability after changes pass verification.

How does pre-commit verification handle code review integration?▼

Pre-commit verification handles code review integration by triggering after changes pass review. It finalizes the work by running per-criterion checks and a complete test pass before staging files and creating a validated commit.

When should I trigger the automated commit workflow for reviewed code?▼

You should trigger the automated commit workflow for reviewed code using prompts like 'commit these changes' or 'finalize this work'. This ensures the full test pass and pre-commit verification execute before finalizing.