commit-guidelines
Guidelines for creating git commits. Use when making commits, staging changes for commit, or deciding how to split changes across commits.
Guidelines for creating git commits. Use when making commits, staging changes for commit, or deciding how to split changes across commits.
Initialize complete governance framework in a project - creates constitution, roadmap, directory READMEs, and issue/spec templates with guided setup process
Generate clear conventional commit messages from git diffs. Use when writing commit messages, reviewing staged changes, or after completing TDD cycles.
A comprehensive guide for configuring and using Terrateam, an open-source GitOps CI/CD platform for Terraform and OpenTofu. Covers configuration file structure, access control, workflows, OIDC authentication, drift detection, and best practices for managing infrastructure through pull requests.
When you need to understand the directory structure, open-core model, or where to add new code.
End the current session. Converts transcript to markdown, writes summary, syncs files, commits, and pushes to GitHub and Blot.
Use when creating research or plan documents to gather git commit, branch, repository info.
"Work with git worktrees and workspaces for concurrent development. Use when: (1) Creating new workspaces with \`git worktree add\`, (2) Listing existing worktrees with \`git worktree list\`, (3) Removing worktrees with \`git worktree remove\`, (4) Pruning stale worktree metadata with \`git worktree prune\`, (5) Managing multiple checked-out branches simultaneously, (6) Migrating uncommitted work between workspaces, or (7) Any git workspace/worktree operation. Requires Git 2.5+ for worktree support."
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.
This skill should be used when reviewing code or preparing code for review. It provides guidelines for what to look for in reviews, how to write constructive feedback, and standards for review comments.
Use when starting new feature work to create isolated git worktrees with smart directory selection and safety verification. Keeps main branch clean while developing.
CLI tools guide for git, gh, npm, and other development tools. Triggers: git, gh, npm, CLI, コマンドライン, バージョン管理, ブランチ, コミット.
Orchestrate replying to multiple GitHub PR review comments in parallel. Use when the user wants to reply to multiple PR review comments or resolve all unresolved comments on a PR.
Any time committing changes is mentioned, use this commit flow.
MANDATORY skill when users mention GitHub CLI searches - establishes non-negotiable requirement to use gh-cli-search skills for correct syntax, quoting, and platform handling
Prepare for the next agent or session by documenting work and leaving codebase in good state
Clean up git worktrees whose associated feature PRs have been merged. Only removes worktrees where the PR is confirmed merged - never removes active development worktrees.
A guide to using magit-section for building collapsible, hierarchical buffer UIs in Emacs.
Use when searching GitHub pull requests - provides syntax for filtering by draft status, merge status, review state, CI checks, branches, and all standard PR attributes
Use when gh CLI is not installed, not configured, or authentication fails - provides installation steps, authentication methods, and troubleshooting for all platforms
Post-checkout git hook for automatic worktree setup. Use when: (1) Setting up automatic configuration for new git worktrees, (2) Creating post-checkout hooks that detect new worktrees and run setup tasks, (3) Configuring worktrees to automatically copy env files and install dependencies
Use when searching GitHub issues - provides syntax for filtering by labels, state, assignees, authors, comments, reactions, dates, and includes option to search pull requests