Gjalla Prepare And Commit
- 211 installs
- 2 repo stars
- Updated June 15, 2026
- gjalla/engineering
Checks that code is ready to commit, then stages changes into clean, atomic commits.
About
Verifies code is commit-ready and stages the changes into clean, atomic commits. A developer uses it right before committing to keep history tidy.
- Pre-commit readiness check
- Stages changes into atomic commits
Gjalla Prepare And Commit by the numbers
- 211 all-time installs (skills.sh)
- Ranked #174 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
- Data as of Jul 24, 2026 (Skillselion catalog sync)
npx skills add https://github.com/gjalla/engineering --skill gjalla-prepare-and-commitAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 211 |
|---|---|
| repo stars | ★ 2 |
| Last updated | June 15, 2026 |
| Repository | gjalla/engineering ↗ |
What it does
Checks that code is ready to commit, then stages changes into clean, atomic commits.
Files
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 --examplewill 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.
Related skills
Caveman CommitGenerate terse, Conventional Commits messages that preserve intent without fluff or AI attribution.272k94k
Resolving Merge ConflictsQuickly understand, resolve, and commit merge conflicts without losing work or breaking their flow.183k193kGit Guardrails Claude CodePrevent Claude Code from accidentally running destructive git commands like force push, hard reset, or clean.175k193k
Using Git WorktreesGuarantee every new feature or implementation task runs inside a clean, isolated workspace without polluting the main branch or current working directory.149k263k
Git CommitGenerate accurate conventional commit messages and intelligently stage files directly from natural language requests.40.6k37.2k
Resolve Merge ConflictsQuickly understand and resolve Git merge conflicts without losing context or breaking changes.16.5k148