aiskillstore/commit
skills/davidopdebeeck/commit/SKILL.md
Generate commit messages following project conventions for staged changes. Use when the user asks to commit changes or run /commit.
$ install --global
skillsauthnpx skillsauth add aiskillstore/marketplace 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 1, 2026, 3:34 AM60.5s2 files scanned
SKILL.md
- name:
- commit
- description:
- Generate commit messages following project conventions for staged changes. Use when the user asks to commit changes or run /commit.
Commit Message Generator
Generate commit messages following project conventions for staged changes.
Instructions
When this skill is invoked:
- Run
git diff --stagedto review the staged changes - Run
git statusto understand the overall state - Run
git log --oneline -10to see recent commit style for context - Analyze what was changed and why
- Generate a commit message following the format below
- Present the commit message to the user for approval - keep it concise, just show the message and ask for approval
- If approved, execute the commit
Presentation Style: Be direct and minimal. Present only the commit message and ask "Proceed with this commit message?" - no analysis, explanations, or bullet points unless the changes are complex or ambiguous.
Commit Message Format
<type>: <short description>
[optional body with more detail]
Types
feat- New featurefix- Bug fixrefactor- Code restructuring without behavior changetest- Adding or updating testsdocs- Documentation changesstyle- Formatting, whitespace (no code change)chore- Build, config, dependency updates
Rules
- First line: Must be under 72 characters
- Tense: Present tense, imperative mood ("add" not "added" or "adds")
- Description: Complete the sentence "This commit will..."
- Body: Optional, use for explaining "why" not "what"
- NO AI attribution: Never include "Generated with Claude Code" or "Co-Authored-By" lines
Examples
feat: add auto-reveal toggle for estimation rounds
fix: prevent duplicate user connections to lobby
refactor: extract insight resolution logic to separate resolvers
test: add usecase tests for SetEstimateCommand handler
docs: update architecture documentation with processing groups
chore: upgrade Spring Boot to 3.4.12
Analysis Guidelines
When analyzing changes, consider:
- Module affected: Which module (api, lobby, session, ui)?
- Layer affected: Domain, usecase, adapter, or API contract?
- Intent: What problem does this solve or capability does it add?
- Scope: Is this a single logical change or mixed concerns?
Common Patterns to Recognize
Backend Changes:
- New Commands/Events/Queries in
api/→feat: add X command/event/query - Handler implementations →
feat: implement X handlerorfix: correct X handler logic - Domain logic updates →
feat: add X behavior to aggregateorrefactor: simplify X logic - Read model updates →
feat: update X view projection - Tests →
test: add tests for X
Frontend Changes:
- New components →
feat: add X component - State management →
feat: implement X state handling - UI improvements →
feat: enhance X interface - Styling →
style: update X component styles
Mixed Changes:
- If frontend + backend for same feature →
feat: add X feature(describe full feature) - If unrelated changes → Suggest splitting into multiple commits
Related Skills
aiskillstore/hig-components-content
development
VerifiedTrustedCommunity
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
244SKILL.mdUpdated Apr 10, 2026
aiskillstore/helpdesk-automation
tools
VerifiedTrustedCommunity
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
244SKILL.mdUpdated Apr 10, 2026
aiskillstore/haskell-pro
testing
VerifiedTrustedCommunity
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
244SKILL.mdUpdated Apr 10, 2026
aiskillstore/graphql
tools
VerifiedTrustedCommunity
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.
244SKILL.mdUpdated Apr 10, 2026