committing-changes

Enforce pre-commit quality gates for commits and PRs in Agentic Framework projects.

Updated Dec 31, 2025
One-click install
npx skills add https://github.com/tomgun/agentic-framework --skill committing-changes-tomgun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: committing-changes
Source: https://github.com/tomgun/agentic-framework/tree/main/.agentic/lib/agents/claude/skills/committing-changes
Command: npx skills add https://github.com/tomgun/agentic-framework --skill committing-changes-tomgun

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Prevents incomplete or low-quality work from being committed by enforcing WIP checks, branch policies, artifact updates, test validation, secrets scanning, and explicit human approval before creating commits and pull requests.

Core Features & Use Cases

  • WIP detection and blocking: Detects active work tracked by the framework and blocks commits until work is completed.
  • Branch management: Ensures commits occur on feature branches and warns when on main/master to avoid accidental direct pushes.
  • Durable artifact updates: Uses project scripts to update journal and status artifacts so commits are accompanied by outcome-focused project state.
  • Quality gates: Runs test/validation checks, verifies staged files, scans for obvious secrets, and surfaces warnings or errors.
  • Human-in-the-loop commit and PR creation: Always shows diffs for approval, stages specific files, creates PRs, bumps VERSION, and logs review tasks for follow-up.
  • Use Case: Finalizing a completed feature—verify no active WIP, update STATUS and JOURNAL, run the validation script, show the diff to the developer, then commit and open a PR.

Quick Start

Commit and create a PR for the current feature branch by running the pre-commit checks, updating the journal and status, showing the diff to the human for approval, and then performing a staged commit and PR creation.

Frequently Asked Questions about committing-changes

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

FAQPage Schema
How do I enforce pre-commit checks and prevent incomplete work from being committed?

Pre-commit checks enforce quality gates by detecting active WIP, scanning staged files for secrets, and validating branch state to block incomplete work. The flow requires shell and git access to run validation scripts before finalizing any commit.

What's the best way to manage git commits on feature branches and avoid accidental direct pushes to main?

Branch management ensures commits occur on feature branches and warns when on main or master to avoid accidental direct pushes. This prevents direct pushes to main by validating the current branch state before allowing any staged commit.

Can I automate pull request creation with human approval and diff validation in git?

Yes, human-in-the-loop PR creation shows diffs for explicit approval, stages specific files, and creates pull requests. This approval-driven PR flow bumps VERSION and logs review tasks while requiring human validation before opening the pull request.

Does this pre-commit workflow require specific shell scripts or framework compatibility to run?

Yes, the pre-commit workflow requires shell and git access with Claude Code compatibility. It relies on internal scripts including wip.sh, journal.sh, status.sh, and a pre-commit-check.sh wrapper to detect WIP and branch state within the Agentic Framework.

How do I update project status and journal artifacts before creating a git commit?

Durable artifact updates use project scripts to update journal and status artifacts so commits are accompanied by outcome-focused project state. The workflow runs these updates alongside test validation and secrets scanning before showing the diff for human approval.