commit

Enforce EST naming conventions and verify prerequisite files for version control commits.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/samwelmunga/JengaAgent --skill commit-samwelmunga
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/samwelmunga/JengaAgent/tree/main/.agents/skills/commit
Command: npx skills add https://github.com/samwelmunga/JengaAgent --skill commit-samwelmunga

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This skill eliminates inconsistent commit messaging and ensures that all work items are properly verified and documented before being finalized in the repository.

Core Features & Use Cases

  • EST Naming Convention: Enforces a structured format for Epics, Stories, and Tasks to maintain a clean audit trail.
  • Safety Verification: Automatically checks for required user-action instructions to ensure handoffs are complete.
  • Use Case: After finishing a coding task, use this skill to generate a standardized commit message and verify that the necessary setup instructions for the next developer or user are in place.

Quick Start

Run the commit skill to finalize your current work item and verify that all necessary documentation is prepared.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I standardize git commit messages for epics, stories, and tasks?

You can standardize git commit messages by enforcing the EST naming convention for epics, stories, and tasks. This approach eliminates inconsistent messaging and maintains a clean audit trail across your project repository.

How does safety verification work for project commits?

Safety verification for project commits works by automatically checking for required user-action instruction files. This ensures that necessary setup instructions for the next developer or user are in place before any work item is finalized in the repository.

What is the EST naming convention for version control commits?

The EST naming convention is a structured format for Epics, Stories, and Tasks applied to version control commits. It enforces logical grouping of changes and requires structured summaries to facilitate overall project auditability.

Can I automate workflow documentation checks before finalizing a commit?

Yes, you can automate workflow documentation checks before finalizing a commit. The process verifies the existence of prerequisite instruction files and checks for subsequent epic boundaries to ensure handoffs are complete and properly documented.

When do I need to verify prerequisite instruction files for a commit?

You need to verify prerequisite instruction files for a commit when managing the transition of work items. This verification ensures that all necessary setup instructions for the next developer or user are in place before the work is finalized.