メニュー
Format commit messages using the Conventional Commits v1.0.0 specification. Use when writing commit descriptions, generating commit messages, or when the user asks about commit message format.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Extract embedded text and rendered page images from PDFs. Use when the user asks to read, inspect, parse, convert, or extract contents from PDF files without OCR.
Answer questions about the Datadog org structure using Workday data in Snowflake. Use when the user asks about org charts, team structure, who reports to someone, headcount, titles, or any people/org question.
Upload files with the chonk command and return shareable chonk URLs. Use when the user asks to upload files to chonk or share files via chonk.
Interact with Atlassian Jira and Confluence via MCP. Use when the user asks about Jira issues, Confluence pages, sprints, boards, or any Atlassian task.
Fetch a URL and convert it to clean markdown using trafilatura, writing the result to a file to avoid polluting the context window with HTML. Use when the user asks to fetch, read, scrape, summarize, or extract content from a web page.
Search the web via the Kagi Search API. Use when the user asks to search the web, look something up online, find current information, or needs external references/URLs.
| name | conventional-commits |
| description | Format commit messages using the Conventional Commits v1.0.0 specification. Use when writing commit descriptions, generating commit messages, or when the user asks about commit message format. |
All commit messages MUST follow this format:
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
| Type | Purpose | SemVer |
|---|---|---|
feat | A new feature | MINOR |
fix | A bug fix | PATCH |
build | Changes to the build system or dependencies | — |
chore | Maintenance tasks, no production code change | — |
ci | CI configuration and scripts | — |
docs | Documentation only | — |
style | Formatting, whitespace, semicolons (not CSS) | — |
refactor | Code change that neither fixes nor adds | — |
perf | Performance improvement | — |
test | Adding or correcting tests | — |
feat, fix, etc.).feat(parser):.: ) MUST follow the type/scope prefix.: .token: value or token #value (inspired by git trailers).- in place of spaces (except BREAKING CHANGE).: — e.g. feat!: or feat(api)!:BREAKING CHANGE: <description>BREAKING CHANGE MUST be uppercase. BREAKING-CHANGE is also allowed.feat and fix are permitted (the table above is conventional, not exhaustive).BREAKING CHANGE.SKILL.md files are never docs. They are configuration/tooling — use chore for maintenance edits or feat for new capabilities.claude, api, auth), not the specific file or sub-skill. Prefer the parent package or module name.Co-Authored-By footers, no model names (e.g. Claude, Opus), no Generated by lines, no tool attribution. Commit messages must read as if written by a human.Simple feature:
feat: add email notifications for new signups
Feature with scope:
feat(auth): support OAuth2 PKCE flow
Fix with body:
fix(parser): handle nested brackets in expressions
The regex previously failed on inputs containing consecutive
closing brackets. Switch to a recursive descent approach.
Breaking change (bang and footer):
feat(api)!: remove deprecated /v1/users endpoint
BREAKING CHANGE: The /v1/users endpoint has been removed.
Clients must migrate to /v2/users.
Chore with scope:
chore(deps): bump tokio from 1.37 to 1.38
Docs:
docs: clarify rate-limit behavior in README