post-execution
Complete post-execution tasks after implementing a spec including tests, git workflow, PR creation, and documentation. Use when all spec tasks are complete.
Discover tools git workflows skills, compare source repositories and read the instructions for each workflow.
Complete post-execution tasks after implementing a spec including tests, git workflow, PR creation, and documentation. Use when all spec tasks are complete.
Review pull requests using team standards. Check code quality, test coverage, security, and architecture. Use when reviewing PRs, examining branch changes, or when user asks for code review.
Generate clear, conventional commit messages following project rules. Use when creating commits, writing commit messages, or reviewing staged changes.
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
Comprehensive code review tool for Clean Code principles and project architecture. Supports single-file review (/review-code) and project-wide analysis (/review-code ). Checks variable naming, function length,...
Jujutsu (jj) workflow guidance used in place of Git for commit/push, stacked work, status/log, diff/show, rebase, split/squash, abandon/restore, conflict resolve, bookmarks. Use when users mention jj/Jujutsu or...
Use the GitHub gh CLI for any GitHub task (PRs, issues, releases, workflows, repo queries).
Diagnose GitHub-driven agile workflow problems and guide feature branch development
Manage development phases and quality gates. Use for starting new projects, advancing phases, and navigating the development lifecycle.
將現在已進到 git stage 的檔案 commit 到 git repository
Generate conventional commit messages following git-cz style by default (emoji between type and subject). Automatically detects project configuration when present. Use when creating git commit messages with Con...
Personal commit and contribution preferences. Use when making commits or contributing code.
Use when interacting with GitHub repositories, branches, or PRs. Automatically triggered for PR viewing, code review, and repo inspection tasks.
Intelligently commit changes with a context-aware, auto-generated message that the user can approve or edit before committing. Does not push.
Create timestamped work-in-progress commits to save current state locally without pushing. Use when experimenting or saving intermediate states.
Stage all changes, commit with auto-generated message, and push to remote in one command. Use when you want to quickly save and share changes.
Pre-push validation checklist (cargo fmt, clippy with zero warnings, feature flag testing, test suite), CI monitoring, merge process, and release quality gates. Use when preparing to push code, validating chang...
Auto-check and update key documentation before Git commits to keep docs in sync with code. Triggers: docs, 文檔, 更新文檔, sync docs, release, 發布, documentation, 同步文件, 文件檢查, doc check, 發布前, before...
Intelligently update README.md to sync with code changes. Triggers: readme, 說明, 更新說明, update readme, 文檔同步, documentation, doc, 文件, 說明文件, 更新文檔, sync readme, 同步說明, 專案說明.
Orchestrate pre-commit workflow including Memory Bank sync, README/CHANGELOG/ROADMAP updates. Triggers: GIT, gc, push, commit, 提交, 準備 commit, 要提交了, git commit, pre-commit, 推送, stage, 暫存, checkin, 簽...
Complete code review workflow for PR/MR with multiple reviewers and automated checks. Triggers: PRW, 審查流程, review workflow, PR review, MR review, pull request, merge request, 程式碼審查流程, full review, 完...
Use this skill when the user wants to create a changeset for releasing changes, when preparing a release, or when running the /changeset command.
Establish the files used to track and manage progress.
Personal checklist for setting up new git repositories. Always configure local git identity to avoid commits with incorrect email.
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.