Loading...
Loading...
Found 246 Skills
Generate comprehensive release notes and changelogs. Compiles version history, feature descriptions, and breaking changes from commit information.
Generate git commits following Conventional Commits (commitlint). Use when user wants to commit changes.
Detects optimal commit type from git changes. Use when analyzing commits, determining commit type, or before committing.
Create git commits with user approval and no Claude attribution
Groups related git changes into coherent commits and drafts commit messages. Use when the user asks to commit, commit current changes, or create a commit.
Review code changes against a plan using the plan location and implementing git commit(s).
Git 커밋 히스토리 기반으로 일자별 학습 로그를 생성합니다. 학습 로그, 학습 기록, 일지 생성, recap, 복습 일정, 학습 요약 요청 시 사용.
Always apply this skill when committing to git
Use when committing changes, staging files, or finishing work in a git worktree. Covers smart commit, multi-concern splitting, sensitive-file guarding, and worktree merge.
ping-pong TDD 세션의 마지막 단계입니다. .tdd-sessions/에서 활성 세션 파일을 읽어 완료된 태스크를 요약하고, Conventional Commits 메시지를 제안하며, 커밋을 실행하고 세션 파일을 정리합니다. 모든 /tdd-task 호출이 완료된 후 실행합니다.
Analyses git changed files in the workspace and makes atomic, functional, and semantic commits using conventional commits format. Use when the user asks to commit changes, create commits from staged/unstaged files, or organise working tree changes into meaningful commits.
Create well-formatted conventional commits in a repository hosted on Azure DevOps (ADO / Azure Repos). Use this whenever the user asks to commit changes and the project is on Azure DevOps — dev.azure.com, visualstudio.com, or explicit mentions of ADO, Azure Repos, or work item IDs like `AB#1234`. Automatically appends `AB#<id>` work-item trailers when the branch name or staged changes reference one, and attributes AI-assisted authorship.