Commit Staged
This skill should be used when user asks to "commit these changes", "write commit message", "stage and commit", "create a commit", "commit staged files", or explicitly invokes "commit-staged".
Install
$ agentstack add skill-fcakyon-claude-codex-settings-commit-staged ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-fcakyon-claude-codex-settings-commit-staged) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Commit Staged
Complete workflow for creating commits following project standards.
When explicitly invoked with extra text, treat that text as additional context about the changes and include it in commit planning and commit messages. When session history includes findings, motivation, or rationale, include the strongest points in the commit message body instead of relying on the diff alone.
Process
- Preferred execution
- If subagents are available, use
github-dev:commit-creatorfor the full workflow. - Pass along any extra invocation text as additional context.
- Otherwise follow the manual steps below.
- Analyze staged files only
- Check all staged files:
git diff --cached --name-only - Read diffs:
git diff --cached - Completely ignore unstaged changes
- Commit message format
- First line:
{type}: brief description(max 50 chars) - Types:
feat,fix,refactor,docs,style,test,build - Use plain language. Avoid jargon, buzzwords, and repo shorthand unless an exact command or tool name is needed.
- Use findings and motivation from session history when available.
- Focus on 'why' not 'what'
- 1 sentence conventional style + 1-2 short motivation/findings sentences if possible
- For complex changes, add bullet points after blank line
- Message examples
feat: add sign-in flowfix: stop duplicate jobs on savedocs: add skills install snippets
- Documentation update
- Check README.md for:
- New features that should be documented
- Outdated descriptions no longer matching implementation
- Missing setup instructions for new dependencies
- Update as needed based on staged changes
- Execution
- Commit uses HEREDOC syntax for proper formatting
- Verify commit message has correct format
- Don't add test plans to commit messages
Best Practices
- Analyze staged files before writing message
- Keep first line under 50 chars
- Use active voice in message
- Use simple words that still stay accurate
- Prefer session findings over repeating raw diff details
- One logical change per commit
- Ensure README reflects implementation
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: fcakyon
- Source: fcakyon/claude-codex-settings
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.