Commits code changes with appropriate git commit strategy. Adopts Squash (default), new commit, or Interactive Rebase based on context, and creates messages following Conventional Commits format. Use when implementation is complete or user requests a commit.
Git から指定範囲のコミットを収集し、Quarto（reveal.js）でスライド（HTML/PDF）を生成する。 タスクID、コミット範囲、ブランチ間の差分など、柔軟な指定方法に対応。
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
MANDATORY skill for ALL commits. Must be used EVERY TIME before creating any git commit. No exceptions.
Use when reviewing GitHub pull requests with gh CLI - creates pending reviews with code suggestions, batches comments, and chooses appropriate event types (COMMENT/APPROVE/REQUEST_CHANGES)
Git コミットのベストプラクティス。意味のある変更単位でのコミット、Conventional Commits ルール、コミットメッセージの書き方を定義。
Fetch and analyze GitHub issues from the monorepo. Use when user asks about issues, what's blocking, issue status, dependencies, or wants to see issue details.
Identify and remove merged or stale git worktrees. Use for housekeeping, removes worktrees for branches that have been merged to main. Frees disk space.
Load a GitHub issue, create an isolated worktree, plan the implementation, and submit a PR. Use when asked to fix, implement, or work on a GitHub issue by number. Requires the gh CLI to be authenticated.
Verify if the current repository uses Jujutsu (jj) instead of git. Use this skill when you or the user needs to confirm the version control system (VCS) state before performing operations.
Analyze git diff to identify code changes requiring documentation updates. Categorizes changes (database/schema, API endpoints, components, configuration, authentication) and suggests relevant documentation files to review. Use when: (1) After making code changes, (2) Before committing significant changes, (3) When adding new features or modifying APIs, (4) During PR preparation, (5) When working with database schemas, API routes, components, or configuration files, (6) To ensure documentation stays synchronized with code changes, (7) For documentation sync and maintenance, or (8) For pre-commit documentation checks. Triggers: check docs, docs check, documentation check, update docs, sync documentation, what docs need updating, check if docs are up to date, after code changes, before committing.
Create well-formatted git commit messages following conventional commits standard. This skill should be used after completing coding tasks to create clear, descriptive commit messages that accurately reflect changes.
This skill should be used when providing context about "modern CLI tools", "best practices for shell configuration", "dotfiles organization", "security patterns for configs", "performance optimization", "git configuration patterns", "modern alternatives to traditional tools", or when the main dotfiles-optimizer skill needs reference knowledge about configuration best practices.
This skill should be used when addressing MISRA-C 2023 or CERT-CPP compliance violations through automated suppression workflows. Use it for analyzing violation reports, applying systematic suppressions, and managing the git-based compliance workflow from initial analysis to pull request creation.
Use when creating git commits or pull requests, or when asked to write a commit message
