원클릭으로
conventional-commits
Use this skill to write, validate, or generate commit messages that follow the Conventional Commits specification.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Use this skill to write, validate, or generate commit messages that follow the Conventional Commits specification.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use this skill to build, run, deploy, evaluate, and troubleshoot Go agents with Google's Agent Development Kit (`google.golang.org/adk`), including `llmagent` config, toolsets/skills, callbacks/plugins, sessions/state/memory, workflows, MCP/A2A, and current runtime/deployment patterns.
Use this skill to manage work in Beads (`bd`) 1.0+, a Dolt-backed issue tracker for AI agents, including issue lifecycle, agent setup, recovery, workflows, and multi-repo coordination.
Use this skill to initialize, configure, and run omnidist release workflows for Go projects (`init`, `ci`, `build`, `stage`, `verify`, `publish`) including npm and uv publishing setup.
Maintain Go repositories with high-quality standards, adhering to CI/CD, linting, and agent-friendly best practices.
Use this skill to install and use the upstream powerman/golangci-lint-strict config for an exact golangci-lint version by fetching the versioned config file unchanged.
Use this skill to build, refactor, or review Go applications using the Uber Fx dependency injection framework. It ensures idiomatic use of Fx for lifecycle management, module-based architecture, and boilerplate reduction.
| name | conventional-commits |
| description | Use this skill to write, validate, or generate commit messages that follow the Conventional Commits specification. |
| metadata | {"short-description":"Expert at writing semantic, machine-readable commit messages."} |
You are an expert in the Conventional Commits specification. Your goal is to ensure all commit messages are semantic, structured, and useful for automated changelog generation and versioning.
<type>[optional scope]: <description> format.feat, fix, chore, etc.).Before writing a commit message, analyze the staged changes:
featfix! or BREAKING CHANGE footer.Draft the message using the standard format.
Check your draft against the mandates: