Discover tools git workflows skills, compare source repositories and read the instructions for each workflow.
MANDATORY quality gate. Run this skill BEFORE: (1) asking user "Is this okay?", (2) git commit, (3) creating PR, (4) presenting any implementation or design to user. Codex reviews in read-only sandbox, iterates...
Terminal-based GitHub PR review tool. Review PRs without leaving the terminal using your favorite editor.
Automatically report work progress as comments on GitHub Issues. Use upon completion of major milestones, PR creation, merge completion, or when explicitly requested.
Git commit 前的完整驗證檢查。當用戶提到「commit」、「提交」、「push」或完成重要修改時自動執行。
Applies Google's engineering practices for strict, health-focused code reviews.
Comprehensive engineering standards for monorepo projects with Claude Code, covering hooks, testing, documentation, quality gates, and best practices. Use when setting up new projects, validating compliance, or...
CI/CD pipeline guide covering GitHub Actions, Lefthook hooks, Dependabot, and deployment scripts. Use when asking about workflows, automation, or deployment.
Manage WIP document lifecycle: create, track, review, and archive work-in-progress documentation; use when starting features, reviewing active WIPs, or archiving completed work (project)
MANDATORY skill for ALL commits. Must be used EVERY TIME before creating any git commit. No exceptions.
Generate git commands (add, commit, push) ready to execute
Commit message format guidelines.
Write Nix code and manage NixOS/home-manager configurations. Use when writing Nix expressions, flakes, modules, or debugging derivations.
Manage git worktrees with gtr. Use when working on multiple branches in parallel, especially with async agents.
Guide for debugging failing GitHub Actions workflows. Use this skill when debugging failing GitHub Actions workflows.
Create, update, and manage GitHub issues using MCP tools. Use this skill when users want to create bug reports, feature requests, or task issues, update existing issues, add labels/assignees/milestones, or mana...
Use when the repo contains .agentscfg and the user asks to add/update agent configuration, skills, MCP, or tool settings. Enforce the agentscfg workspace layout and avoid creating separate/legacy agent config l...
Prepare a release (phases 1-6). Usage: /prepare-release [version]. If version omitted, infers from conventional commits. Coordinates agents for review, runs prepare-release.sh, then enhances release notes with...
Review unpushed commits before pushing for code quality, bugs, security issues, and error handling. Use when preparing to push commits, want pre-push code review, or need to validate changes before pushing. Run...
This skill should be used when the user asks to "optimize dotfiles", "optimize my dotfiles", "improve shell", "improve my shell configuration", "check configs", "check my configuration", "audit dotfiles", "anal...
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 co...
This skill should be used when the user says "commit changes", "commit this", "commit my work", "save to git", "save my changes", "push this", "push my work", "create a commit", or wants to save their work to v...
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
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of ma...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.