Gjalla prepare commit

Skill gjalla/engineering/skills/gjalla-prepare-commit

Opinionated, time-tested agent skills for trustworthy, production-grade engineering — spec-driven planning, rigorous review, and test auditing for the agentic SDLC.

Install

npx -y skills add gjalla/engineering --skill gjalla-prepare-commit

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Make sure your code is ready to commit, then stage changes into clean, atomic commit. Use before committing.

SKILL.md

1.7 KB, as published. Nobody here has run it

Make your changes commit-ready

Turn a working change into a committable change that reviewers and future readers can trust.

1. Review what you implemented

Are all verification criteria and expected outcomes met?
Is the implementation complete (no dummy data or placeholder stubs left)?
Are all of the gjalla rules met?
Does this elegantly build on top of / within the existing state/architecture/properties?
Does it match the plan / gjalla spec?
Are positive, negative, and edge cases saliently tested?

2. Make a commit plan

One logical change per commit. If the diff does two unrelated things, don't be afraid to split it (git add -p).
Ensure you're committing to the right branch and/or following the expected branching strategy.
Prepare what you will report to git (description of the lines of code that are changing) and to gjalla (via attestation - properties of the system that have changed, including a reference to the gjalla spec)
Ensure gjalla git hooks are in place already. If they're not, your attestation and spec will not get sync'd into the master source of truth.

3. Commit

Write your gjalla attestation. gjalla attest --example will show you the format, make sure to view the full output (do not run the command and pipe it 2>/dev/null for example)
Write your commit message and run your commit. Your gjalla attestatation and spec will be sync'd with gjalla as part of the git hooks, no additional work required from you.
Unless the user has given you blanket permission, you should likely ask the user before pushing the commit.

Gives 1 of the 12 instructions most pr commit review skills give

Counted across 888 of the 1,342 authors here whose files we hold, read 2026-08-06

use conventional commits formatin 123 of 888, across 110 files
keep subject line under 72 charactersin 60 of 888, across 46 files
delete branches after mergein 50 of 888, across 37 files
use imperative mood in subject linein 50 of 888, across 41 files
use imperative mood in commit messagesin 45 of 888
generate a conventional commit messagein 42 of 888
make atomic commitsin 37 of 888, across 25 files
run tests before committingin 36 of 888, across 24 files
run project test suite to verify clean baselinein 35 of 888, across 7 files
run detected project setup commandsin 34 of 888, across 6 files
wrap commit body at 72 charactersin 32 of 888, across 25 files
split unrelated changes into separate commitshere, and in 32 of 888, across 27 files

Said here and by no other author read

verify all outcomes and criteria are met
remove all dummy data and placeholder stubs
test positive negative and edge cases
commit to the correct branch
prepare git description and gjalla attestation
verify gjalla git hooks are installed

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.