菜单
Generate well-structured git commit messages following conventional commits format. Use when committing changes, creating commit messages, or when commit history needs improvement. Ensures commits are clear, descriptive, and follow project conventions.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Checks code for accessibility issues including missing alt text, poor color contrast, missing ARIA labels, keyboard navigation issues, screen reader compatibility, and focus management. Returns structured accessibility issue reports with WCAG compliance information.
Ensures designs meet accessibility requirements including WCAG compliance, color contrast, keyboard navigation, screen reader support, and focus management. Reviews designs for accessibility issues and provides recommendations.
Assesses agent capabilities by analyzing agent files and determining what tasks they can handle. Use when you need to evaluate if an existing agent can handle a task or if a new agent is needed. Reviews agent descriptions, skills, and workflows to determine capability match.
Creates new agent files with complete specifications, following the same format as existing agents. Use when a new agent is needed for tasks that existing agents cannot handle. Generates agent markdown files with name, description, core principles, workflow, and integration details.
Implements API endpoints, routes, controllers, and request/response handling. Use when implementing REST APIs, GraphQL APIs, or other API endpoints. Handles routing, validation, error handling, and response formatting.
Reviews code architecture for design issues including poor separation of concerns, tight coupling, missing abstractions, design pattern violations, scalability concerns, and maintainability issues. Returns structured architecture review reports with improvement suggestions.
| name | git-commit-helper |
| description | Generate well-structured git commit messages following conventional commits format. Use when committing changes, creating commit messages, or when commit history needs improvement. Ensures commits are clear, descriptive, and follow project conventions. |
feat: New featurefix: Bug fixdocs: Documentation changesstyle: Code style changes (formatting, no logic change)refactor: Code refactoringperf: Performance improvementstest: Adding or updating testschore: Maintenance tasks, build config, etc.ci: CI/CD changesbuild: Build system changestype(scope): subjectInput: "I added a new login button and fixed the validation bug" Output:
feat(auth): add login button to header
- Add new login button component to navigation header
- Implement click handler to open login modal
- Add styling to match design system
fix(validation): resolve email validation error
- Fix regex pattern for email validation
- Add test cases for edge cases
- Update error message to be more user-friendly
Closes #123
Input: "Updated the README and fixed some typos" Output:
docs: update README with installation instructions
- Add detailed installation steps for different platforms
- Include troubleshooting section
- Fix typos in existing documentation
Input: "Refactored the payment processing code" Output:
refactor(payments): improve payment processing logic
- Extract payment validation into separate function
- Simplify retry logic for failed transactions
- Improve error handling and logging
- Add unit tests for payment flow
BREAKING CHANGE: PaymentProcessor constructor now requires config object
Conventional Commits Format:
<type>(<scope>): <subject>
<body>
<footer>
Types:
feat: New feature for usersfix: Bug fix for usersdocs: Documentation onlystyle: Formatting, missing semicolons, etc.refactor: Code change that neither fixes bug nor adds featureperf: Performance improvementtest: Adding missing testschore: Changes to build process or auxiliary toolsBest Practices: