ricky-yosh/gf-create-git-commits
skills/greenfield/gf-create-git-commits/SKILL.md
Creates well-structured git commits from current changes. Analyzes staged or unstaged changes and splits them into coherent logical commits grouped by intention. Part of the gf (greenfield) skill family. Use when the user says /gf-create-git-commits, asks to commit their work, or wants to save progress as git commits during a long feature build.
development
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add ricky-yosh/agent-workflows gf-create-git-commitsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 8:38 PM30.5s1 file scanned
SKILL.md
- name:
- gf-create-git-commits
- description:
- Creates well-structured git commits from current changes. Analyzes staged or unstaged changes and splits them into coherent logical commits grouped by intention. Part of the gf (greenfield) skill family. Use when the user says /gf-create-git-commits, asks to commit their work, or wants to save progress as git commits during a long feature build.
- model:
- opus
Git Commit Strategy (Long Feature)
Commit Message Format
The commit message is a single -m string. One sentence. Nothing else.
No body. No bullet points. No trailers. No "Co-Authored-By". No heredocs.
git commit -m "Brief description of the change"
Examples:
git commit -m "Add project skeleton with Express server and folder structure"
git commit -m "Create user model with in-memory store and basic CRUD"
git commit -m "Wire up login endpoint to auth service"
Anti-examples — do NOT do this:
# WRONG: heredoc with trailer
git commit -m "$(cat <<'EOF'
Some change
Co-Authored-By: ...
EOF
)"
# WRONG: multi-line body
git commit -m "Some change
Added X, Y, and Z"
Commit Splitting
Split commits by intention — what the change is trying to accomplish, not just which files it touches. Read the diffs carefully to understand what each hunk does, then group hunks that serve the same purpose into one commit.
Think about it like telling a story: each commit is one sentence in the narrative of the feature. "First I set up the project, then I added the data model, then I wired up the API."
How to split: Use git add -p or git add <specific-files> to stage subsets, then commit each group separately. A single file can be split across commits if different hunks serve different intentions.
When NOT to split: If all changes serve the same intention and are tightly coupled, one commit is fine.
Workflow
This skill creates commits directly — the user can always git reset if they don't like the result. Do not ask for confirmation. Do not push to any remote. Just commit locally.
- Check
git diff --stagedfor staged changes. If nothing is staged, checkgit difffor unstaged changes and work with those instead. - Read every hunk carefully — understand what each change does
- Identify the distinct intentions across all changes
- For each intention group: stage the relevant files/hunks with
git addorgit add -p, thengit commit -m "..." - After all commits, run
git log --oneline -n <N>to show the result
Do not add, stage, or commit files that aren't part of the user's changes (e.g., don't touch unrelated files). Do not run git push.
Related Skills
ricky-yosh/gf-write-tests
development
VerifiedTrustedCommunity
Write tests for a batch of tasks BEFORE implementation. Detects the project's test framework and language, then writes tests that cover happy paths, edge cases, and failure modes. All tests should fail initially since there is no implementation yet. Part of the gf (greenfield) skill family. Use when the user says /gf-write-tests or wants to write tests before implementing a feature or task batch.
SKILL.mdUpdated Apr 16, 2026
ricky-yosh/gf-testing-notes
testing
VerifiedTrustedCommunity
Generate readable testing notes after a feature is complete. Compares spec against implementation to produce a concise list of what was built, how to test it, and any scope gaps. Writes testing-notes.md to .aw/greenfield-progress/. Part of the gf (greenfield) skill family.
SKILL.mdUpdated Apr 16, 2026
ricky-yosh/gf-save-progress
testing
VerifiedTrustedCommunity
Save current session work to .aw/greenfield-progress/progress.txt. Captures decisions (why, not just what) that git diff cannot show. Updates tasks.json to mark completed tasks. Part of the gf (greenfield) skill family.
SKILL.mdUpdated Apr 16, 2026
ricky-yosh/gf-review
testing
VerifiedTrustedCommunity
Gate the greenfield workflow on user verification after an implementation step. Reads the implementation digest, shows verification steps, and waits for the user to confirm before advancing. Part of the gf (greenfield) skill family.
SKILL.mdUpdated Apr 16, 2026