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
This skill should be used for integrating PR review comments back into devloop plan, parsing review feedback, addressing reviewer concerns
Git-branchless stacked diffs workflow patterns and command reference
Creates and maintains bidirectional links between specifications and GitHub issues/PRs via comments
Sync a single project bidirectionally with codex core repository. Delegates to fractary CLI for sync operations.
GitHub Actions の条件付き実行を設計し、if 条件とイベントフィルタの運用を支援するスキル。 条件式の整理、イベント別の分岐、検証と記録の流れを体系化する。 Anchors: • The Pragmatic Programmer（Andrew Hunt, David Thomas）/ 適用: 条件分岐による品質管理 / 目的: 実践的な流れ制御パターンを参照 • Continuous Delivery（Jez Humble）/ 適用: パイプラインの段階的実行制御 / 目的: 効率的な実行制御 • GitHub Actions / 適用: if 条件・event filters・status functions / 目的: 標準構文の準拠 Trigger: Use when designing conditional execution in GitHub Actions workflows, handling if expressions, or applying event filters and status functions. conditional execution, github actions, if conditions, event filters, status functions
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Use when you've developed a broadly useful skill and want to contribute it upstream via pull request - guides process of branching, committing, pushing, and creating PR to contribute skills back to upstream repository
Review a project's PRs to check for issues detected in code review by Seer Bug Prediction. Use when asked to review or fix issues identified by Sentry in PR comments, or to find recent PRs with Sentry feedback.
Create and manage Git branches with safety checks and validation
Commit code changes with well-structured messages following Conventional Commits. Use when ready to commit after implementation or bug fix.
Use when managing git worktrees. Provides patterns for creation, cleanup, and branch naming.
Gitを活用したドキュメントのバージョン管理と変更履歴管理の専門スキル。 ブランチ戦略、コミット規約、Changelog生成、PRレビューを提供します。 Anchors: - Pro Git（Scott Chacon）/ 適用: ブランチ戦略・履歴管理 / 目的: Gitベストプラクティス - Conventional Commits / 適用: コミットメッセージ規約 / 目的: 自動化可能なコミット - Keep a Changelog / 適用: Changelog形式 / 目的: 人間が読みやすい変更履歴 Trigger: Use when managing document versions with Git, designing branch strategies, generating changelogs, or preparing PR reviews for documentation.
Create an implementation plan with atomic commits that build toward a complete feature
Fetch and analyze GitHub PR review comments and code-level feedback using the prc CLI. Use this skill whenever the user mentions PR comments, PR feedback, reviewer feedback, review comments, addressing reviews, fixing PR issues, checking what reviewers said, loading PR context, or working on PR revisions. Accepts PR numbers (auto-detects repo), PR URLs, or owner/repo format.
[DEPRECATED] GitHub Issues handler - Use Fractary CLI instead
Get GitHub repository statistics including stars, forks, and watchers
Audits local HyperFleet repositories against team architecture standards dynamically fetched from the architecture repo. Activates when users ask to audit repos, check standards compliance, or identify standards gaps. READ-ONLY - does not modify any files. Produces JIRA-ready gap specifications for integration with jira-ticket-creator skill.
Linear issue-tracked development workflow. Auto-activates when starting work on issues, creating branches, changing status, writing comments, or creating PRs.
Define and enforce golden paths and best practices for development teams
Best practices for breaking down work into GitHub issues, proper sizing, and milestone organization. Use during discovery/planning phases.
