amhuppert/commit
claude/ai-resources-plugin/skills/commit/SKILL.md
Commit staged git changes after generating and approving a message.
$ install --global
skillsauthnpx skillsauth add amhuppert/my-ai-resources 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: May 7, 2026, 3:44 AM153.8s1 file scanned
SKILL.md
- name:
- commit
- description:
- Commit staged git changes after generating and approving a message.
- disable-model-invocation:
- true
- allowed-tools:
- Bash(git add:*), Bash(git status:*), Bash(git diff --cached), Bash(git commit -m:*)
Git Commit Helper
This skill helps create well-formatted git commit messages based on staged changes.
Context
% git status
!`git status`
% git diff --cached
!`git diff --cached`
% git branch --show-current
!`git branch --show-current`
% git log --oneline -10
!`git log --oneline -10`
Instructions:
-
Check the current branch. If it is 'main', abort the commit and ask the user to switch to a different branch.
-
If not on 'main', analyze the staged changes in the git diff.
-
Generate a commit message following this format:
{one line commit summary} {more detailed description of changes if necessary} -
Ensure your commit message adheres to these rules:
- Do not mention Claude Code, AI assistance, or any related terms
- Do not include co-author information
- Keep the summary line concise and informative
- Provide a more detailed description only if necessary
-
If you need to revise your commit message, do so until it meets all criteria.
Before generating the final commit message, wrap your analysis inside <git_analysis> tags in your thinking block. This analysis should include:
- A summary of the git status, diff, and recent commits
- A list of all files changed and the type of changes (added, modified, deleted)
- Identification of the main theme or purpose of the changes
- Brainstorming of a few potential commit messages
This will help ensure a thorough interpretation of the git diff and status.
Here's an example of a good commit message format:
Implement user authentication feature
- Add login and registration endpoints
- Create user model
- Set up JWT token generation
Remember, the key is to be descriptive yet concise, focusing on what was changed and why.
Now, please proceed with your analysis and commit message generation based on the provided git information. Once the user has approve the commit message, commit the changes.
Related Skills
amhuppert/hotkey-helper
tools
VerifiedTrustedCommunity
Use when picking or vetting a keyboard shortcut on macOS. Triggers include "what hotkey should I use for X", "is `<combo>` available", "does this shortcut conflict", "recommend a keybinding for…", "check `<combo>` against my setup", "pick a hotkey for…", or any mention of choosing/binding/changing a shortcut in WezTerm, tmux, Zed, Chrome, Claude Code, or macOS. Determines whether a proposed combo collides with OS-reserved bindings, app defaults, or the user's customizations, and recommends ergonomic alternatives when needed.
2SKILL.mdUpdated Jun 2, 2026
amhuppert/knip
development
VerifiedTrustedCommunity
Detect and remove dead code with knip. Use when the user asks to "run knip", "find unused files", "find unused exports", "find unused dependencies", "clean up dead code", "remove dead code", "set up knip", "configure knip", "knip.json", "knip false positive", "knip CI", or mentions a `knip` config, dependency bloat, bundle bloat from unused imports, or tree-shaking unused exports. Covers the configuration-first workflow, confidence-gated deletion, framework-specific gotchas (Next.js 15+, Tailwind, Storybook, Jest, Bun's test runner and `bun build --compile`), monorepos, CI integration, and performance tuning.
1SKILL.mdUpdated May 27, 2026
amhuppert/react-scan
tools
VerifiedTrustedCommunity
This skill should be used when the user asks to "set up react-scan", "install react-scan", "diagnose React re-renders", "find unnecessary renders", "find unstable props", "automate React render checks with Playwright", "react-scan + playwright", "measure component renders programmatically", "check why a React component is slow", or mentions React rendering issues, slow React interactions, render counts, or component-level perf attribution. Covers install across Next.js/Vite/Remix/script-tag/browser-extension, the lite headless API for CI, and the canonical render-attribution → fix → validate loop driven through Playwright.
1SKILL.mdUpdated May 20, 2026
amhuppert/knowledge-base-ingest
documentation
VerifiedTrustedCommunity
This skill should be used when integrating source material into a knowledge base, including when the user asks to "integrate this document into the knowledge base", "add this transcript to the memory bank", "ingest this document", "update the knowledge base", "analyze a new source document", or "sync current-state docs with this source".
1SKILL.mdUpdated May 17, 2026