goji-commit-smart

Generate deterministic commits from Git changes using goji rules and jasper.toml policy.

1|Updated Dec 9, 2024
One-click install
npx skills add https://github.com/hadenlabs/tasks --skill goji-commit-smart
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: goji-commit-smart
Source: https://github.com/hadenlabs/tasks/tree/main/.claude/skills/goji-commit-smart
Command: npx skills add https://github.com/hadenlabs/tasks --skill goji-commit-smart

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates deterministic multi-commit generation from a Git working tree by applying goji rules and domain policy, helping teams maintain a clean, consistent history.

Core Features & Use Cases

  • Run validation before committing to ensure policy compliance and guardrails.
  • Inspect the working tree and derive commits using path-based grouping and goji conventions.
  • Derive issue keys from the current branch and create commits with appropriate scopes and emojis.
  • Sign commits when configured and supported by your Git setup to ensure traceability.
  • Produce conventional commits compatible with Jira, GitHub, and GitLab workflows.

Quick Start

Run the goji-commit-smart skill in a repository configured with jasper.toml and .goji.json to automatically validate, group, and commit changes according to goji rules.

Frequently Asked Questions about goji-commit-smart

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

FAQPage Schema
How do I automate deterministic git commits from my working tree?

You can automate deterministic git commits by partitioning working tree changes into groups that follow goji rules, using a domain model defined in .goji.json and policy in jasper.toml for consistent history.

What is automatic issue-key derivation from branch names for conventional commits?

Automatic issue-key derivation extracts issue keys from your current branch name and applies them to conventional commits, supporting both Jira-style and GitHub/GitLab styles for traceable project history.

How do I configure goji-commit-smart to validate and sign commits automatically?

Configure goji-commit-smart by setting up jasper.toml for policy and .goji.json for domain rules; it runs validation before committing and signs commits when configured and supported by your Git setup.

Do I need a Taskfile-based workflow to generate policy-driven commits?

Yes, generating policy-driven commits requires a valid Taskfile-based workflow alongside the jasper.toml policy file and a properly structured .goji.json domain file to validate and group changes.

Can I group path-based changes into separate commits with goji conventions?

Yes, you can group path-based changes into separate commits by inspecting the working tree and deriving commits using path-based grouping and goji conventions with appropriate scopes and emojis.

What is the best way to enforce standardized git commit formats across a team?

Enforce standardized git commit formats across a team by applying a domain model in .goji.json and policy in jasper.toml to automate deterministic, policy-driven commits that follow goji rules.