rite

rite workflow の Getting Started ガイド

rite workflow の初回セットアップウィザード

コード調査（/investigate）

ブランチの作成とベースブランチの設定

親 Issue から適切な子 Issue を自動選択

Issue の完了状態を確認

> **Source**: Extracted from `start.md` Phase 5.6. This file is the source of truth for the completion report procedure.

Issue の仕様書作成・分解・一括作成

Issue 作成のためのインタビュー実行

単一 Issue の確認・作成・登録

新規 Issue を作成し、GitHub Projects に追加

既存 Issue の内容を対話的に修正

実装作業・コミット・プッシュ・チェックリスト更新ロジック

Issue 内容を分析して実装計画を生成

GitHub Issue の一覧を表示

親Issue判定・子Issue選択・分解提案ロジック

コンテキストコミット履歴から過去の決定事項を検索

作業メモリを更新

Issue に作業メモリコメントを初期化

品質チェックを実行

PR マージ後のクリーンアップを実行

ドラフト Pull Request を作成

レビュー指摘への対応を支援

PR を Ready for review に変更

> **Source**: Extracted from `cleanup.md` Phase 3-4. This file is the source of truth for Projects Status Update, Issue close, Parent Issue handling, and state reset procedures.

> **Source**: Extracted from `review.md` Phase 5.3.1-5.3.7. This file is the source of truth for assessment rules.

Pre-computed change statistics provided to reviewers to improve review quality and focus.

> **Source**: Referenced from `review.md` Phase 5 Critic Phase (`#### Fact-Checking Phase`, between Deduplication and Specification Consistency Verification). This file is the source of truth for fact-checking rules.

Defines how fix targets are determined in the `/rite:issue:start` review-fix loop.

Optimization rules for handling large PRs in `/rite:pr:review`.

Built-in minimal profiles for when skill files (`skills/reviewers/*.md`) cannot be loaded.

中断した作業を再開

現在のコンテキストを分析し、適用可能なスキルを提案

現在のスプリント詳細を表示

Sprint 内の Todo Issue を連続実行

Sprint/Iteration 一覧を表示

スプリント計画を実行

Sprint 内の Todo Issue を並列チーム実行

テンプレートを再生成

rite ワークフロー全体のガイドを表示

All reviewers MUST adopt these principles:

Reviews API design, REST conventions, and interface contracts

Reviews code for quality issues (duplication, naming, error handling, structure, unnecessary fallbacks)

Reviews schema design, queries, migrations, and data operations

Reviews package dependencies, versions, and supply chain security

Reviews infrastructure, CI/CD pipelines, and deployment configurations

Reviews error handling patterns for silent failures, inadequate logging, and inappropriate fallbacks

Reviews UI components, styling, accessibility, and client-side code

Reviews code for performance issues (N+1 queries, memory leaks, algorithm efficiency)

Reviews Claude Code skill, command, and agent definitions for prompt quality

Reviews code for security vulnerabilities (injection, auth, data handling)

Sprint team member agent that implements Issue tasks within an assigned worktree directory

Reviews documentation for clarity, accuracy, and completeness

Reviews test quality, coverage, and testing strategies

Reviews type design for encapsulation, invariant expression, usefulness, and enforcement quality

Investigate code structures (/investigate) using a 3-phase process: Grep to locate, Read to verify, and Codex (optional) to cross-check. Prevents false reports from guessing. Covers all code structures: function calls, hashes, conditionals, method chains, class definitions, and configuration values. Activates on "調査", "investigate", "コード調査", "grep で調べて", "呼び出し箇所", "使われ方", "一覧", "全件", "どこで使われている".

Coordinates parallel multi-expert PR code review. Activates with /rite:pr:review or when user asks for "code review", "PR feedback", "security check", "review my changes", "レビューして", "PRレビュー", "コードチェック", "セキュリティ確認", "変更を確認", "コードレビュー". Spawns specialized reviewers (Security, API, Database, DevOps, Frontend, Test, Dependencies, Prompt Engineer, Tech Writer, Code Quality, Error Handling, Type Design) based on changed file patterns. Produces unified findings with severity levels.

Automates the complete Issue-to-PR lifecycle: start working on Issues, create branches, implement changes, run quality checks, and manage PRs — all through a single workflow. Essential for any /rite: command, workflow questions, or when working with Issues, branches, commits, or PRs. Activates on "start issue", "create PR", "next steps", "workflow", "rite", "Issue作業", "ブランチ", "コミット規約", "PR作成", "作業開始", "ワークフロー", "次のステップ". Use for workflow state detection, phase transitions, and command suggestions.

8 hooks across 7 events