smith-stacks
Stacked pull request workflows for large features. Use when creating stacked PRs, managing dependent PRs, or rebasing after parent merges. Covers stack creation, merge order, and squash merge handling.
Stacked pull request workflows for large features. Use when creating stacked PRs, managing dependent PRs, or rebasing after parent merges. Covers stack creation, merge order, and squash merge handling.
Create focused GitHub issues that serve as summaries for work. Issues describe the user goal and link to branch plans for implementation details. One issue per meaningful unit of work - avoid splitting into many small issues.
Comprehensive feature development workflow management with branching strategies, code reviews, testing automation, and deployment coordination.
Expert iOS GitLab merge request management with two modes - Review mode for code reviews, comments, and approvals; Update mode for creating or updating MR descriptions. Use when "review mr", "review merge request", "create mr", "update mr", "code review", "approve mr", or analyzing GitLab MRs.
Use when designing cloud infrastructure, CI/CD pipelines, or deployment strategies
Comprehensive guide for building robust, secure, and efficient CI/CD pipelines using GitHub Actions. Covers workflow structure, jobs, steps, environment variables, secret management, caching, matrix strategies, testing, and deployment strategies.
Architecture and ADR workflows for Workbench CLI. Use when documenting system design, decisions, tradeoffs, or rationale that must be tracked over time.
Git-backed issue tracker for multi-session work with dependencies and persistent memory across conversation compaction. Use when work spans sessions, has blockers, or needs context recovery after compaction. Triggers: "tasks", "beads", "task tracker", "issue tracker", "task memory", "bd", "issues".
Create GitHub issues across any repository with proper formatting, labels, and project board assignment. Use when mentions "create issue", "GitHub issue", "open issue", "file issue", "report bug", "feature request".
Use the /review-plan slash command to validate scope, risks, and success criteria. Use when: gating plans before execution.
Critically review implementation plans before execution. Use when validating plans, checking standards compliance, or before running implement-plan.
Orchestrate parallel and/or sequential subagents working in separate git worktrees to deliver PR(s). Use when bundling multiple related GitHub issues into a single task, running best-of-3 identical attempts, monitoring runs, selecting the best PR, and closing/cleaning up the rest.
Manage development phases and quality gates. Use for starting new projects, advancing phases, and navigating the development lifecycle.
Comprehensive development workflow specialist combining TDD, debugging, performance optimization, code review, PR review, and quality assurance into unified development workflows
Use this skill when the user wants to generate a commit message. Contains workflow for branch checking, ticket ID extraction, and message formatting.
Creates phase-based feature plans with TDD workflow and quality gates. Use for code projects requiring structured development approach. Keywords: plan, planning, phases, TDD, test-driven, roadmap.
Apply triage decisions to SonarCloud security issues by reading a CSV with review decisions and updating issue/hotspot statuses via the SonarCloud API. Use when the user has reviewed security issues and wants to bulk-update SonarCloud with their triage decisions.
Orchestrate the full product flow from vision to shipped code. Use when starting a new feature or product.
Advanced Git workflows, branching strategies, and commit conventions
Development workflow emphasizing test-first development, task classification, and appropriate tracking. Use when starting implementation, planning changes, or structuring development work.
Classify workflow failures and attempt automatic recovery. Use when sprint/feature fails during implementation to determine if auto-fix is possible or manual intervention required.
Development workflow for code changes. Load when: implementing features, fixing bugs, writing tests, refactoring, creating PRs, reviewing code. Covers exploration → design → implementation → commit → PR cycle. Keywords: feature, bug, fix, test, refactor, PR, pull request, commit, code review, implement, develop, build.
Systematic framework for contributing to open source projects. Guides through issue discovery, integrated analysis with code exploration, implementation, and PR creation. Use when starting OSS contributions, analyzing issues, or creating pull requests. Includes modular sub-skills for each contribution phase.
GitHub Projectの管理スキル。ghコマンドを使用してプロジェクトの確認、アイテム追加・状態変更、フィールド更新を行う。 トリガー条件: - 「Projectを確認して」「プロジェクトのアイテム一覧」「Project #N を見せて」 - 「IssueをProjectに追加」「PRをProjectに紐付け」 - 「ステータスをDoneに変更」「フィールドを更新」 - 「カンバンを操作」「タスクの進捗を更新」