メニュー
Expert PR and commit message writing following Conventional Commits. Use when creating pull requests, merge requests, writing commit messages, or generating changelogs. Applies to GitHub, GitLab, and Azure DevOps.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
SQL engineering standards for writing correct, safe, cross-dialect SQL across PostgreSQL, MySQL, SQL Server, SQLite, DuckDB, and Oracle. Use when writing SQL queries, exploring schemas, running migrations, optimizing queries, transpiling between dialects, or connecting to databases via native CLIs.
MongoDB engineering standards for querying collections, building aggregation pipelines, designing document schemas, managing indexes, and administering deployments via mongosh. Use when writing MongoDB queries, exploring collections, designing schemas, optimizing performance, or managing replica sets and sharding.
Engineering planning standards for creating design docs, DRI working docs, ADRs, and weekly updates. Use when planning projects, writing design docs, creating RFCs, tracking risks, writing status updates, or reviewing engineering plans. Covers structure, operational tracking, context engineering, and scaling from startup to enterprise.
Multi-agent PR review that spawns parallel domain-specific subagents (python-expert, rust-expert, dbt-expert, dotnet-expert, kedro-expert, d2-tala-expert, ui-designer) based on changed file types, posts inline review comments on GitHub, GitLab, and Azure DevOps.
dbt engineering standards for building clean, modular, well-tested data transformations. Use when writing dbt models, configuring sources, designing project structure, writing tests, managing materializations, or preparing for dbt Fusion. Covers dbt Core 1.8–1.11, Fusion v2.0, SQL style, testing, governance, and deployment.
Langfuse observability platform standards for querying traces, managing prompts, debugging LLM applications, and accessing Langfuse data programmatically. Use when interacting with Langfuse, querying traces or sessions, managing prompts, instrumenting applications, or looking up Langfuse documentation. Covers CLI-based API access (via npx) and documentation retrieval.
| name | pr-writing |
| description | Expert PR and commit message writing following Conventional Commits. Use when creating pull requests, merge requests, writing commit messages, or generating changelogs. Applies to GitHub, GitLab, and Azure DevOps. |
This skill provides Claude Code with expert-level knowledge for writing pull requests, merge requests, and commit messages following industry best practices and Conventional Commits specification.
<type>(<scope>): <description>
[optional body]
[optional footer(s)]
<type>: <concise description>
Or with scope:
<type>(<scope>): <concise description>
| Type | When to Use | Example |
|---|---|---|
feat | New feature or capability | feat: add OAuth2 authentication |
fix | Bug fix | fix: resolve null pointer in user service |
docs | Documentation only | docs: update API reference |
chore | Maintenance, deps, configs | chore: upgrade dependencies |
refactor | Code change, no behavior change | refactor: extract validation logic |
test | Adding/fixing tests | test: add unit tests for auth module |
ci | CI/CD pipeline changes | ci: add caching to build workflow |
perf | Performance improvement | perf: optimize database queries |
style | Formatting, whitespace | style: fix indentation |
build | Build system changes | build: update webpack config |
revert | Reverting previous commit | revert: feat: add OAuth2 |
| Bad | Good |
|---|---|
Fixed the bug | fix: resolve race condition in auth |
Updated stuff | chore: upgrade lodash to 4.17.21 |
New feature | feat: add dark mode toggle |
Changes | refactor: simplify error handling |
WIP | feat: add user export (WIP) |
## Summary
- First major change or feature
- Second major change
- Third change if applicable
## Changes
### Category 1
- `path/to/file.ts` - Description of change
- `path/to/other.ts` - Description of change
### Category 2
- `another/file.ts` - Description of change
## Test Plan
- [ ] Verify feature X works as expected
- [ ] Verify existing tests pass
- [ ] Manual testing of scenario Y
## Notes
Any additional context, breaking changes, or migration notes.
| Concept | GitHub | GitLab | Azure DevOps |
|---|---|---|---|
| Code review request | Pull Request (PR) | Merge Request (MR) | Pull Request (PR) |
| Default branch | main | main | main |
| CI/CD config | .github/workflows/ | .gitlab-ci.yml | azure-pipelines.yml |
| CLI tool | gh | glab | az repos |
Detect platform from git remote URL:
| URL Pattern | Platform | CLI Command |
|---|---|---|
github.com | GitHub | gh pr create |
gitlab.com or gitlab.* | GitLab | glab mr create |
dev.azure.com | Azure DevOps | az repos pr create |
*.visualstudio.com | Azure DevOps | az repos pr create |
gh pr create --base <target> --title "<title>" --body "<body>"
glab mr create --target-branch <target> --title "<title>" --description "<body>"
az repos pr create --target-branch <target> --title "<title>" --description "<body>"
When multiple commits exist, determine the primary type:
feat commit? → PR type is featfix commits? → PR type is fixdocs commits? → PR type is docsfeat > fix > refactor > perf > test > docs > chore > styleFor breaking changes, add an exclamation mark after the type:
feat!: remove deprecated API endpoints
fix!: change authentication flow
Or add footer:
feat: redesign user API
BREAKING CHANGE: User endpoint now requires authentication token.
Scope is optional but useful for larger projects:
| Scope | Example |
|---|---|
| Module/feature | feat(auth): add password reset |
| File type | style(css): fix button alignment |
| Component | fix(navbar): resolve dropdown z-index |
| Package | chore(deps): update react to 18.2 |