メニュー
Prompt and workflow for generating conventional commit messages using a structured format. Guides users to create standardized, descriptive commit messages in line with the Conventional Commits specification, including instructions, examples, and validation.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Implements Manus-style file-based planning to organize and track progress on complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when asked to plan out, break down, or organize a multi-step project, research task, or any work requiring 5+ tool calls.
AI-powered codebase security scanner that reasons about code like a security researcher — tracing data flows, understanding component interactions, and catching vulnerabilities that pattern-matching tools miss. Use this skill when asked to scan code for security vulnerabilities, find bugs, check for SQL injection, XSS, command injection, exposed API keys, hardcoded secrets, insecure dependencies, access control issues, or any request like "is my code secure?", "review for security issues", "audit this codebase", or "check for vulnerabilities". Covers injection flaws, authentication and access control bugs, secrets exposure, weak cryptography, insecure dependencies, and business logic issues across JavaScript, TypeScript, Python, Java, PHP, Go, Ruby, and Rust. Also covers IaC-specific issues: hardcoded credentials, overly permissive IAM, unencrypted storage, and public resource exposure in Terraform, Ansible, CloudFormation, and Helm.
| name | conventional-commit |
| description | Prompt and workflow for generating conventional commit messages using a structured format. Guides users to create standardized, descriptive commit messages in line with the Conventional Commits specification, including instructions, examples, and validation. |
This skill generates conventional commit messages following the Conventional Commits specification.
Follow these steps:
git status to review changed files.git diff or git diff --cached to inspect changes.git add <file>.<type>(<scope>): <description>
[optional body]
[optional footer]
Types:
feat — New feature or blueprint additionfix — Bug fix or configuration correctiondocs — Documentation changes onlystyle — Formatting, missing semicolons, no logic changerefactor — Code change that neither fixes a bug nor adds a featureperf — Performance improvementtest — Adding missing tests or correcting existing testsbuild — Changes that affect the build system or dependenciesci — Changes to CI/CD configuration files and scriptschore — Updating grunt tasks etc; no production code changerevert — Reverts a previous commitfeat(01-aws-ec2): add KMS key for EBS encryption
fix(01-aws-ec2): correct subnet CIDR calculation
docs(02-ha-kubernetes): update Helm values reference table
chore(deps): pin terraform aws provider to 5.50.0
ci(validate): add tfsec security scan to PR workflow
refactor(shared/terraform-modules): extract vpc into reusable module
feat(03-air-gapped): add ansible role for docker hardening
01-aws-ec2), module name, or component nameBREAKING CHANGE: description) or issue references (Closes #123)After constructing the message, run:
git commit -m "type(scope): description"
# Or for multi-line:
git commit