antiwork/commit
.claude/skills/commit/SKILL.md
Stage and commit changes with a clear, concise commit message.
$ install --global
skillsauthnpx skillsauth add antiwork/gumroad 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 15, 2026, 5:26 PM5.0s1 file scanned
SKILL.md
- name:
- commit
- description:
- Stage and commit changes with a clear, concise commit message.
- argument-hint:
- [optional message hint]
- allowed-tools:
- Bash(git *)
Commit
Create a commit for the current changes.
Steps
- Run
git status(without-uall) to see untracked and modified files. - Run
git diffandgit diff --cachedto understand staged and unstaged changes. - Run
git log --oneline -5to see recent commit style. - Run linters on changed files before staging:
- Ruby files:
bundle exec rubocop --force-exclusion -a <files> - JS/TS files:
npm run lint-fast -- --max-warnings 0 --fix --no-warn-ignored <files> - TypeScript type check:
npx tsc --noEmit(required, catches type errors that eslint skips) - CSS/SCSS/JSON/MD files:
npx prettier --write <files> - SVG files:
npx svgo --multipass <files> - Fix any lint errors or type errors before proceeding. Do not commit code that fails linting or type checking.
- Ruby files:
- Stage the relevant files by name — avoid
git add -Aorgit add .. - Write a commit message and commit.
If $ARGUMENTS is provided, use it as a hint for the message.
Commit message rules
- Use the imperative mood ("Add", "Fix", "Remove", not "Added", "Fixes", "Removed").
- Be concise: one short sentence, ideally under 50 characters.
- Do NOT use conventional commit prefixes (no
feat:,fix:,chore:, etc.). - Do NOT add any
Co-Authored-Byor similar trailers. - Focus on what changed and why, not how.
- If a second line is needed for context, keep it brief.
Examples of good messages
Prevent discount code from being cleared on editAdd integration test for offer code persistenceRemove unused legacy export helperFix thumbnail missing in upsell insert
$ARGUMENTS
Related Skills
antiwork/review-pr
development
VerifiedTrustedCommunity
Review GitHub pull requests for the Gumroad codebase against project guidelines, code quality, and correctness. Use when the user wants to review a PR, check new comments on a PR, provide feedback on code changes, or asks about PR quality. Triggers on: "review PR", "review this PR", "check PR #NNN", any GitHub PR URL (e.g. https://github.com/antiwork/gumroad/pull/NNNN), "what's new on the PR", "check comments", "review the diff", "give feedback on this PR", or requests to evaluate code changes in a pull request.
8,811SKILL.mdUpdated Apr 4, 2026
antiwork/pr-description
documentation
VerifiedTrustedCommunity
Generate a PR description for the current branch and its linked GitHub issue. Outputs to an unstaged markdown file in the repo root. Never creates or updates PRs. Triggers on: "generate PR description", "write PR description", "PR description", "describe this PR", "draft PR", or after completing implementation work when the user wants to prepare a PR. Also use when the user says "pr", "pull request description", or asks to summarize their branch changes for review.
8,811SKILL.mdUpdated Apr 4, 2026
antiwork/create-issue
development
VerifiedTrustedCommunity
Draft GitHub issues for the Gumroad codebase. Outputs to an unstaged markdown file in the repo root. Never creates issues on GitHub. Triggers on: "create issue", "write issue", "draft issue", "write a bug report", "file an issue", "create a ticket", or when the user describes a problem or feature they want to turn into a GitHub issue.
8,811SKILL.mdUpdated Apr 4, 2026
steipete/skill-creator
testing
VerifiedTrustedCommunity
Create, edit, improve, or audit AgentSkills. Use when creating a new skill from scratch or when asked to improve, review, audit, tidy up, or clean up an existing skill or SKILL.md file. Also use when editing or restructuring a skill directory (moving files to references/ or scripts/, removing stale content, validating against the AgentSkills spec). Triggers on phrases like "create a skill", "author a skill", "tidy up a skill", "improve this skill", "review the skill", "clean up the skill", "audit the skill".
356,423SKILL.mdUpdated Apr 13, 2026