rpi-commit
/rpi-commit
Create git commits for the current working tree with user approval, sensitive-content scan, and gitignore enforcement. Use when user says 'commit this', 'commit the changes', 'make a commit', or 'let's commit what we have'.
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 19.07.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Create git commits for the current working tree with user approval, sensitive-content scan, and gitignore enforcement. Use when user says 'commit this', 'commit the changes', 'make a commit', or 'let's commit what we have'.
Triggers from the description
Original author description
Create git commits for the current working tree with user approval, sensitive-content scan, and gitignore enforcement. Use when user says 'commit this', 'commit the changes', 'make a commit', or 'let's commit what we have'.
How it works
- Goal
- Invariants
- Principles
SKILL.md preview
--- name: rpi-commit description: Create git commits for the current working tree with user approval, sensitive-content scan, and gitignore enforcement. Use when user says 'commit this', 'commit the changes', 'make a commit', or 'let's commit what we have'. --- # Commit Changes ## Goal Create git commits for changes in the working tree with user approval. This includes changes from the current session and any pre-existing modifications. ## Invariants - Gather consolidated git context first: branch, status, diff summary, recent commits - Scan staged files for sensitive content (.env, credentials, secrets, API keys) — warn and exclude unless explicitly told otherwise - Scan candidate files against `.gitignore` rules — warn and exclude any matches (commonly: a file tracked before being added to .gitignore) unless explicitly told to keep it - If the working tree is clean, inform the user and stop — no empty commits - Group related files into logical, focused commits — prefer smaller over monolithic - Draft commit messages in imperative mood, matching the repo's existing commit style; fall back to commitizen convention if no style detected - Cap each commit message at 50 words total (subject + body); if a draft exceeds the cap, condense before presenting for approval - Present the commit plan (files to stage + commit message for each) and ask for approval before executing - Stage specific files with `git add <file>` — never use `-A` or `.` - Use HEREDOC for commit messages to handle special characters safely - After hook failure: read error output, fix the issue, re-stage, create a new commit — never use `--amend` (the failed commit didn't happen) ## Principles - Review conversation history to understand intent behind changes - Inspect manually-edited files (staged but not discussed) before committing **Recommended model:** cheap tier, low effort — message and scans are CLI-backed. Advisory; see `docs/model-routing.md`.
Versions
The database has no other skills named rpi-commit.
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 10ccc3ddf162 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100commit
Write a commit message and create a git commit. Use when the user wants to commit changes, asks for a commit message, or says "commit this" or "make a commit". - 100commit
Create focused git commits from current working tree changes. Use when the user asks to commit changes, make a git commit, write a commit message, split changes into commits, organize commits, group changes into commits, or prepare local changes for commit. - 100commit
Create well-structured git commits from the current working tree. Use when the user says 'commit', 'save my work', 'let's commit this', 'make a commit', or any variation of wanting to commit code to git. - 92git-commit
Use when creating Git commits. - 96commit
Creates atomic conventional git commits using git-agent. This skill should be used when the user requests "commit", "git commit", "create commit", or wants to commit changes using AI atomic commits. - 100commit-message
Write a git commit message for the current changes and optionally make the commit. Use when the user says "commit this", "write a commit message", "commit my changes", or asks to split work into commits.