j.commit

Commits completed epic, story, or task work using the EST naming convention.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve? AI-assisted development sessions often end without properly committing completed work, leaving board state drifted, documentation out of sync, and user-action prerequisites undocumented. This Skill commits implemented epic, story, or task work with a consistent EST naming convention while running pre-commit safety checks. ## Core Features & Use Cases - Scoped pre-commit reconcile: Invokes /reconcile scoped to the exact epic, story, or task being committed so the board is never committed in a drifted state, skipping the scan entirely when no board files are staged. - Report-only doc-sync scan: Runs /doc-sync limited to the files changed by this commit, surfacing documentation drift findings without blocking the commit with a nested approval prompt. - User-action prerequisite check: Verifies an _INSTRUCTIONS.md file exists for tasks with out-of-scope prerequisites, creating one from a template if missing. - Inline mode: When called by /do with --inline or JENGA_COMMIT_INLINE=1, skips reconcile, doc-sync, and worktree logic to commit single small tasks directly. - Use Case: After a developer agent finishes task E12_S03_T02, invoke the commit flow to reconcile the board, check documentation drift, and create a commit like task(E12_S03_T02): add login validation. ## Quick Start Ask the agent to commit the work just completed for the current task using the EST naming convention.

Frequently Asked Questions about j.commit

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

FAQPage Schema
How do I commit completed task work in Jenga AI?▼

Invoke /commit (or /j-commit if the bare form is shadowed) after finishing an epic, story, or task. The skill reconciles the board, runs a scoped doc-sync report, checks user-action prerequisites, and commits using the EST naming convention.

What commit message format does the EST naming convention use?▼

Epics use `epic(<Epic Title>): <summary>` and tasks or stories use `story(<Epic Title>_<Story Title>): <summary>` with a maximum 50-character summary. Inline mode commits use `task(<E##_S##_T##>): <description>`.

Why use /j-commit instead of /commit?▼

The j-commit directory is a collision-safe alias of the commit skill. Some host tools have built-in commands that shadow the bare /commit name, so /j-commit guarantees the same flow remains reachable.

Does commit run doc-sync automatically on every commit?▼

Yes, but only in report-only mode scoped to the files changed by that commit. It surfaces documentation drift findings without applying updates or blocking the commit; you run /doc-sync standalone afterward to apply fixes.

When is the reconcile step skipped before committing?▼

Reconcile is skipped when no board files under project/board/ are staged, since such a commit cannot introduce board drift. It is also skipped entirely in inline mode invoked by /do for single small tasks.