Stage, review, and commit one exact atomic Git change with explicit human approval.
npx skills add https://github.com/peregrinus879/eyragents --skill commit-peregrinus879
Please help me install this Agent Skill. Skill: commit Source: https://github.com/peregrinus879/eyragents/tree/main/agents/.agents/skills/commit Command: npx skills add https://github.com/peregrinus879/eyragents --skill commit-peregrinus879
commit-candidate, capturing tree, parent, branch, message, and scan state before any commit happens. - Credential and privacy scanning: Screens staged paths, diffs, and blobs for secrets, machine identifiers, and session metadata, requiring manual inspection of any unscanned objects. - Verified commit execution: commit-apply validates the receipt digest, index, identities, and hooks before committing through an isolated index, never amending or resetting on failure. - Receipt lifecycle management: Supports showing, rejecting, and closing out receipts with dry-run previews, local-only completion, and resumable close-out staging. - Use Case: After finishing a feature, ask the agent to prepare a commit; it stages only intended hunks, runs gates, presents a commit card with the conventional-commit message, and commits only after you select approval. ## Quick Start Ask the agent to prepare and commit the current atomic change, then review the presented commit card and select Commit and resume to authorize it.High-intent search queries and answers about installing and using this skill.
Stage only intended hunks with git apply --cached on a reviewed patch, then record the prepared index with commit-candidate in record-only mode. The skill refuses partially staged mixed files when using --stage and never allows git add -A or git add .
The agent presents one commit card at a time showing the candidate reference, changes, full message, gate results, and scan disposition, followed by a Commit and resume or Commit and pause selector. Only selecting a Commit option authorizes that single candidate; free text counts as a question or rejection.
Yes, staged paths, diffs, and blobs are screened through a payload scanner for credential patterns, plus a privacy screen for machine identifiers, local paths, and session metadata. Unscanned objects are inventoried and require manual inspection before approval.
It uses conventional commits: type(scope): subject with types like feat, fix, docs, refactor, style, test, and chore. Subjects are imperative, lowercase, and 50 characters max, with a Co-Authored-By trailer resolved from the active model at commit time.
On any refusal or mismatch it reports the outcome and stops; it never amends, resets, switches branches, or bypasses hooks to repair the state. The original index and worktree are never restored or overwritten, leaving resolution to the human.
Receipts are kept through dependent approval, publication, CI, or recovery, then closed by exact ID using commit-candidate --close with a dry-run preview first. Ready candidates, ambiguous records, and other worktrees' records are always preserved rather than swept.
villetakanenValidate the working tree, verify spec alignment, and create an atomic micro-commit.
AgentSystemLabsCommit local changes and push the current HEAD branch to its remote.
npowIdentify and prioritize defects in software artifacts before implementation.
govctl-org__init__