pr-prepare
Prepare pull request descriptions following project template. Activates on: prepare PR, create PR, pull request, ready for PR, draft PR, write PR
code-review-preferences
Use when reviewing code, PRs, or discussing code quality standards. Applies team coding standards and review methodology.
repo-docs
This skill should be used when the user asks to "generate repository documentation", "create a README", "document API", "write architecture docs", "add CONTRIBUTING guide", "update repo docs", "document codebase", or mentions repository documentation, codebase analysis, or cross-repository integration documentation.
commit-message-generator
Generate appropriate commit messages based on Git diffs
global-conventions
Follow project-wide development conventions including project structure, version control practices, environment configuration, documentation, dependency management, and code review processes. Use this skill when organizing files/directories, writing commit messages, managing branches, configuring environments, handling secrets, maintaining documentation, or establishing team workflows. Apply when working with project structure, README files, .gitignore, environment variables, dependency files (package.json, requirements.txt), feature flags, changelogs, or any aspect of project organization and team collaboration that requires consistency across the development lifecycle.
env-config
Use when setting up environment configuration, loading .env files, or managing application settings across environments. Triggers for: .env setup, loading environment variables, Pydantic BaseSettings, configuration validation, or secret management. NOT for: code-specific logic, feature flags, or runtime feature toggles.
waterfall-development
Enforces strict waterfall development workflow with phase gates. Use when (1) features.yml exists in project root, (2) user asks to implement/develop/build a feature, (3) user explicitly requests waterfall workflow. Creates features.yml if missing when invoked.
repo-metadata
This skill should be used when the user asks to "generate repository metadata", "create catalog-info.yaml", "add repo metadata", "document repository structure", or mentions generating structured metadata for service catalog or architecture documentation.
git-commit
MUST use this skill when user asks to commit, create commit, save work, or mentions "커밋". This skill OVERRIDES default git commit behavior. Creates commits following Conventional Commits format with emoji + type/scope/subject (✨ feat, 🐛 fix, ♻️ refactor, etc).
high-quality-commit
コード変更を適切なgitコミット戦略でgit commitします。基本的には既存のgitコミットへのsquash戦略を採用し、必要に応じてブランチ全体のgitコミット履歴を再構成します。実装完了時やユーザーがgit commitを依頼した時に使用します。
git-commit-helper
Generate descriptive commit messages by analyzing git diffs. Use when the user asks for help writing commit messages or reviewing staged changes.
rust-development
Rust development best practices for the Guts project - idiomatic code, error handling, async patterns, and commonware integration
spec-discovery
Parse specs to extract IDs, titles, and traceability metadata (repo, path, hash).