Splits working-tree changes into atomic git commits gated on type checks and secrets scans.
npx skills add https://github.com/PMN123/trapdoor --skill atomic-commit-pmn123
Please help me install this Agent Skill. Skill: atomic-commit Source: https://github.com/PMN123/trapdoor/tree/main/.agents/skills/atomic-commit Command: npx skills add https://github.com/PMN123/trapdoor --skill atomic-commit-pmn123
.env*, *.key, *.pem, and .jac/ files, plus jac check type validation on every staged .jac file before committing. - Ownership and audit rules: Enforces a two-person file-ownership boundary (engine vs. client files), a conventional commit message format, and hard prohibitions on rewriting pushed history. - Use Case: After an agent session leaves git status full of unrelated edits across engine, UI, and docs files, use this Skill to split them by concern with git add -p, verify each compiles, and land a clean sequence of small commits. ## Quick Start Review my current uncommitted changes and split them into atomic commits, running the build and secrets checks before each one.High-intent search queries and answers about installing and using this skill.
Read the full diff first, then stage by concern using git add <path> or git add -p for hunk-level splits. Each commit should pass three tests: describable in one line without "and", revertable as exactly one decision, and leaving the repo in a building state.
An atomic commit contains exactly one logical change that either does one thing completely or becomes two commits. It keeps history revertable, simplifies code review, and prevents merge conflicts when multiple people or agent sessions work in parallel.
Run a secrets gate before staging: confirm no .env*, *.key, *.pem, secrets.toml, or .jac/ files are included, and never use git add -A without reading git status first. Never use git add -f, since it bypasses the .gitignore rules that keep credentials out.
No. This workflow prohibits --amend, rebase -i, reset --hard, and force-push on anything already pushed, because the commit timeline serves as an audit trail. Preserve timestamps and add corrective commits instead of rewriting history.
Stop and talk to the file owner rather than committing over their work. The ownership boundary assigns engine files (main.jac, walkers, node/edge types) to one person and client files (*.cl.jac, styling, ingester) to the other, and crossing it silently causes expensive conflicts.
nihalnihalaniImplement Jac server endpoints using walker and function routes with typed responses.
VYRE-StudiosCommit staged changes, push the branch, and open a pull request via GitHub CLI.
gqf2008Automate pre-commit verification with static security scans and quality gates.
Soyio-idCreate logically scoped git commits with Conventional Commit messages from working-tree changes.