fcakyon/commit-workflow
plugins/github-dev/skills/commit-workflow/SKILL.md
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 runs /commit-staged or /commit-creator commands.
$ install --global
skillsauthnpx skillsauth add fcakyon/claude-codex-settings commit-workflowInstall 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 4, 2026, 8:27 PM9.0s1 file scanned
SKILL.md
- name:
- commit-workflow
- description:
- 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 runs /commit-staged or /commit-creator commands.
Commit Workflow
Complete workflow for creating commits following project standards.
Process
-
Use commit-creator agent
- Run
/commit-staged [context]for automated commit handling - Or follow manual steps below
- Run
-
Analyze staged files only
- Check all staged files:
git diff --cached --name-only - Read diffs:
git diff --cached - Completely ignore unstaged changes
- Check all staged files:
-
Commit message format
- First line:
{type}: brief description(max 50 chars) - Types:
feat,fix,refactor,docs,style,test,build - Focus on 'why' not 'what'
- 1 sentence conventional style + 1 sentence motivation/findings if possible
- For complex changes, add bullet points after blank line
- First line:
-
Message examples
feat: implement user authentication systemfix: resolve memory leak in data processing pipelinerefactor: restructure API handlers to align with project architecture
-
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
- Check README.md for:
-
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
- Reference related code if helpful
- One logical change per commit
- Ensure README reflects implementation
Related Skills
fcakyon/setup
tools
VerifiedTrustedCommunity
This skill should be used when user asks to "set up overleaf", "configure overleaf cookie", "overleaf auth failed", "overleaf 401", "overleaf session expired", "overleaf unauthorized", or needs to install or refresh their Overleaf session cookie for the overleaf-skills plugin.
674SKILL.mdUpdated May 10, 2026
fcakyon/review-overleaf
documentation
VerifiedTrustedCommunity
This skill should be used when user asks to "fetch overleaf review comments", "address overleaf reviews", "apply overleaf comments", "review my overleaf paper", "sync overleaf feedback to local", "what comments are on my overleaf doc", or wants to act on Overleaf reviewer feedback in a local git-tracked LaTeX repo.
658SKILL.mdUpdated May 3, 2026
fcakyon/dokploy-deploy
tools
VerifiedTrustedCommunity
This skill should be used when user asks to "deploy with Dokploy", "use Dokploy Cloud", "manage self-hosted Dokploy", "deploy Docker Compose on Dokploy", "manage Dokploy databases", "configure Dokploy domains", or "look up Dokploy CLI commands".
654SKILL.mdUpdated Apr 26, 2026
fcakyon/stripe-best-practices
development
VerifiedTrustedCommunity
Guides Stripe integration decisions — API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, Treasury financial accounts, integration surfaces (Checkout, Payment Element), migrating from deprecated Stripe APIs, and security best practices (API key management, restricted keys, webhooks, OAuth). Use when building, modifying, or reviewing any Stripe integration — including accepting payments, building marketplaces, integrating Stripe, processing payments, setting up subscriptions, creating connected accounts, or implementing secure key handling.
645SKILL.mdUpdated Apr 4, 2026