aviflombaum/avinyc:commit
plugins/git-workflows/skills/commit/SKILL.md
This skill should be used when the user asks to "commit", "make a commit", "commit my changes", "create commits", "git commit", or wants to commit staged/unstaged changes with logical grouping and conventional commit format.
$ install --global
skillsauthnpx skillsauth add aviflombaum/claude-code-in-avinyc avinyc:commitInstall 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 3, 2026, 8:42 AM10.0s1 file scanned
SKILL.md
- name:
- avinyc:commit
- description:
- This skill should be used when the user asks to "commit", "make a commit", "commit my changes", "create commits", "git commit", or wants to commit staged/unstaged changes with logical grouping and conventional commit format.
- user-invocable:
- true
- argument-hint:
- [files or message]
Git Commit Assistant
Analyze git changes and create logical, well-structured commits using conventional commit format.
When to Use
- User asks to commit changes
- Multiple unrelated changes need separate commits
- Changes need conventional commit formatting
Workflow
Step 1: Review Current State
Run git status to see all changes:
git status
Review both staged and unstaged changes. Identify modified, added, and deleted files.
Step 2: Analyze and Plan Commits
Group changes into logical commits based on:
- Feature boundaries: Files that implement the same feature together
- Type of change: Separate fixes from features from refactors
- Scope: Group by component, module, or area of the codebase
Present the commit plan to the user before proceeding:
I see the following logical commits:
1. feat(auth): Add password reset - auth/reset.rb, auth/mailer.rb
2. fix(api): Handle null responses - api/client.rb
3. docs: Update README - README.md
Step 3: Execute Commits One by One
For each planned commit:
Stage specific files only:
git add <file1> <file2>
Verify staging:
git status
Create commit with conventional format:
git commit -m "<type>[scope]: <description>" -m "<body>"
Verify commit succeeded:
git status
Only proceed to the next commit after verifying the current one completed.
Conventional Commit Types
| Type | Description | |------|-------------| | feat | New feature | | fix | Bug fix | | docs | Documentation only | | style | Formatting, no code change | | refactor | Code change, no new feature or fix | | perf | Performance improvement | | test | Adding or fixing tests | | chore | Build process, auxiliary tools |
Commit Message Format
<type>[optional scope]: <description>
[optional body]
[optional footer]
- Description: Imperative mood, lowercase, no period ("add feature" not "Added feature.")
- Body: Explain what and why, not how
- Scope: Component or area affected (auth, api, db, ui)
Rules
- Never mix unrelated changes in a single commit
- Always verify staging before committing
- Always verify success after committing
- Explain the plan before executing
- Never use
git add .orgit add -Awithout explicit approval - Never include "Generated with Claude Code" or Co-Authored-By footers
Example Session
$ git status
# Modified: auth/login.rb, auth/signup.rb, README.md, api/client.rb
Plan:
1. feat(auth): Improve login validation - auth/login.rb, auth/signup.rb
2. fix(api): Handle timeout errors - api/client.rb
3. docs: Add authentication guide - README.md
Executing commit 1...
$ git add auth/login.rb auth/signup.rb
$ git status # verify only auth files staged
$ git commit -m "feat(auth): improve login validation" -m "Add email format check and rate limiting"
$ git status # verify commit succeeded
Executing commit 2...
[continues...]
Related Skills
aviflombaum/avinyc:warp-bootstrap
development
VerifiedTrustedCommunity
Bootstrap Warp terminal configuration for Rails projects. Creates launch configurations with colored tabs for dev server, Claude, shell, and more. This skill should be used when setting up Warp for a Rails project. Triggers on "setup warp", "configure warp", "warp rails", "warp bootstrap", "terminal setup for rails", "warp-rails".
38SKILL.mdUpdated Apr 3, 2026
aviflombaum/avinyc:write
development
VerifiedTrustedCommunity
Write technical blog posts, tutorials, and documentation in Flatiron School's engaging style. Use for explaining code patterns, debugging stories, or turning complex topics into clear narratives. Triggers on "write a blog post", "tutorial about", "explain how", "technical writing".
38SKILL.mdUpdated Apr 3, 2026
aviflombaum/avinyc:marketing
data-ai
VerifiedTrustedCommunity
Marketing funnel modeling and conversion metrics. Use for ad spend analysis, CPM/CPC optimization, landing page conversions, waitlist economics, and funnel modeling. Triggers on "ad spend", "cpm", "cpc", "conversion rate", "landing page", "waitlist", "funnel".
38SKILL.mdUpdated Apr 3, 2026
aviflombaum/avinyc:business
testing
VerifiedTrustedCommunity
SaaS unit economics and growth strategy. Use for LTV, CAC, MRR/ARR analysis, payback period, churn analysis, Rule of 40, and SaaS financial modeling. Triggers on "unit economics", "ltv", "cac", "mrr", "arr", "churn", "saas metrics".
38SKILL.mdUpdated Apr 3, 2026