git-commit
Guide for breaking changes into logical, atomic commits using interactive staging. Use when committing changes that span multiple concerns, when needing to stage parts of files (hunks), when asked to create wel...
Découvrez les skills content media git workflows, comparez leurs dépôts et consultez leurs instructions.
Guide for breaking changes into logical, atomic commits using interactive staging. Use when committing changes that span multiple concerns, when needing to stage parts of files (hunks), when asked to create wel...
Remove a worktree and clean up resources. Use when asked to clean, remove, or delete a worktree.
Complete the session close protocol. Runs git status, stages changes, syncs beads, commits, pushes to remote, and optionally deploys to Shopify. Use when ending a work session.
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
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 codebas...
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Git workflow conventions for RawDrive. Use when creating commits, branches, pull requests, or reviewing code changes.
Full feature development workflow (called by feature-new/feature-continue)
Investigates and creates Git branches. Triggered when: branch status check, new branch creation, branch-related errors.
Git command conventions. Use when running any git commands to avoid blocking on interactive pager.
Use when writing commit messages or understanding conventional commit format. CSO keywords: 커밋 메시지, commit message, feat fix refactor, breaking change, 커밋 규칙, atomic commit, 원자적 커밋
Use when setting up environment configuration, loading .env files, or managing application settings across environments. Triggers for: .env setup, loading environment variables, Pydantic BaseSettings, configura...
Manage CodeCommit PRs (create/list/view)
Use as default workflow when no specialized workflow (debug, iterate, pr-comment) applies. For general implementation tasks.
Manages safe git branching, conventional commits, and push flow for Next.js + TS projects. Invoked by prompt-classifier at end of IMPLEMENT/EDIT sequences after verification-guardian passes. Ensures work happen...
This skill should be used when the user asks to "review this commit message", "validate my commit", "improve this commit message", "explain conventional commits", "teach me commit message best practices", "writ...
This skill should be used when the user asks to "review this commit message", "validate my commit", "improve this commit message", "explain conventional commits", "teach me commit message best practices", "writ...
This skill should be used when the user types "/review-commit" or asks to review and clean up staged changes before committing. It launches the commit-cleaner agent to review code quality, remove redundancies,...
Full PR review workflow with checklist verification and release notes. Use when reviewing PRs before merge.
Analyze all commits on your branch since diverging from main, then generate a PR/MR title and description summarizing the complete changeset
変更内容を分析し、Conventional Commits形式でコミットを作成する
Project structure and coding conventions for RawDrive. Use when creating new files, organizing code, or understanding the codebase layout. CRITICAL for preventing random file creation.
変更内容を分析し、適切なGitブランチを作成する
uvとRuffでPythonプロジェクトを立ち上げる。新規リポジトリ作成と初期のlint/format運用確立に使う。
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.