Discover tools git workflows skills, compare source repositories and read the instructions for each workflow.
Expert PM validation for increment closure with 3-gate quality checks (tasks, tests, documentation). Acts as final quality gate before closing increments. Validates task completion, test coverage, documentation...
Expert guide for setting up bidirectional synchronization between SpecWeave and external tools (GitHub Issues, Jira Epics, Azure DevOps Work Items). Provides interactive setup wizards with sync direction option...
Aligns versions across multiple repositories according to release strategy (lockstep, independent, umbrella). Handles semantic versioning constraints, detects version conflicts, suggests version bumps based on...
Invoke BEFORE committing changes
Audits repositories for Claude Code readiness and suggests improvements. Use when asked to check CLAUDE.md quality, review settings, audit project organization, or optimize for agentic work.
Expertise in validating that the codebase matches a specific plan. Use when the user asks to "validate the plan", "check implementation", or "audit the code".
Deployment workflows, pre-deploy validation, and smoke testing patterns. Use when deploying to staging or production, running smoke tests, or validating deployments.
Advanced git operations including rebase, bisect, cherry-pick, and conflict resolution. Use when rebasing branches, debugging with bisect, cherry-picking commits, or resolving complex merge conflicts.
SAFe development workflow guidance including branch naming conventions, commit message format, rebase-first workflow, and CI validation. Use when starting work on a Linear ticket, preparing commits, creating br...
Deployment workflows, pre-deploy validation, and smoke testing patterns. Use when deploying to staging or production, running smoke tests, or validating deployments.
Advanced git operations including rebase, bisect, cherry-pick, and conflict resolution. Use when rebasing branches, debugging with bisect, cherry-picking commits, or resolving complex merge conflicts.
PR creation, CI/CD validation, and release coordination patterns. Use when creating pull requests, running pre-PR validation, checking CI status, or coordinating merges.
SAFe development workflow guidance including branch naming conventions, commit message format, rebase-first workflow, and CI validation. Use when starting work on a Linear ticket, preparing commits, creating br...
PR creation, CI/CD validation, and release coordination patterns. Use when creating pull requests, running pre-PR validation, checking CI status, or coordinating merges.
brainbaseにおけるGitコミットのルールとフォーマット。コミットメッセージの書き方、type一覧、自動提案タイミングを定義。コミット作成時に使用。
開発ワークフロー統合ガイド（7 Skills統合版）。Git運用・CI/CD管理・Design-to-Code・Claude Code活用・ワークフロー検証・Worktree管理・CI/CD認証を統合。§ 1（Gitコミット）→ § 2（CI/CD）→ § 3（Design-to-Code）→ § 4（...
brainbaseのGitワークフロー（/commit、/merge）への準拠をチェック。Conventional Commits、Decision-making capture、Branch safetyを自動検証。
【必須】バグ修正時は常にこのフレームワークを使用すること。仮説より先に確認を積み上げ、根本原因から修正する6 Phase体系。
Automate software releases, versioning, and changelog management. Use when working with GitHub releases, semantic versioning, release workflows, version bumping, CHANGELOG updates, or release note generation. H...
Enforce code quality standards, test coverage, and static analysis. Use when working with code coverage thresholds, mutation testing, linting, code formatting, or quality gates. Maintains high code quality stan...
File reference material into the filesystem (default ~/Documents/Reference). Use when routing non-actionable items to reference, cleaning up a filesystem inbox, or migrating reference material from another sync...
Comprehensive code quality assessment in spaces/[project]/. Use before commits, merges, or releases to ensure consistent quality.
Complete task: validate, document, review, commit, and merge to develop. Use when all implementation is done and ready to finalize.
Create git commits in spaces/[project]/ with conventional message format. Use for saving progress with quality checks and proper commit messages.
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.