Rite Workflow Skill

This skill provides context for rite workflow operations.

Auto-Activation Keywords

• Issue, PR, Pull Request
• workflow, rite
• branch, commit
• GitHub Projects
• review, lint
• recall, 決定事項検索, コンテキスト, なぜ

Context

When activated, this skill provides:

1. Workflow Awareness

   • Current branch and associated Issue
   • Work memory state
   • Status in GitHub Projects

2. Command Guidance

   • Suggest appropriate commands
   • Remind about work memory updates
   • Guide through workflow steps

3. Best Practices

   • Conventional Commits format
   • Branch naming conventions
   • PR template usage

4. Coding Principles

   • Avoid common AI coding failure patterns
   • See references/coding-principles.md for details

5. Common Principles

   • Reduce excessive AskUserQuestion usage
   • See references/common-principles.md for details

Workflow State Detection

Detect current state from:

• Branch name pattern: {type}/issue-{number}-*
  • {type} values: feat, fix, docs, refactor, chore, style, test
  • style is used for code style/formatting changes (no logic changes)
• Git status
• Open PRs

Suggested Actions

State	Suggestion
On main/develop, no Issue	/rite:issue:create or /rite:issue:list
On feature branch, no PR	/rite:pr:create after work
PR open, draft	/rite:pr:review then /rite:pr:ready
Long session (30+ minutes elapsed)	/rite:issue:update
Sprint with Todo Issues available	/rite:sprint:execute to run Issues sequentially
Sprint with multiple independent Issues	/rite:sprint:team-execute to run Issues in parallel with worktrees
Want to recall past decisions or context	/rite:issue:recall or /rite:issue:recall {scope}

Question Management

Key Principle: Always apply question_self_check (see references/common-principles.md) before asking questions. Most questions can be avoided through context inference and using sensible defaults.

When Questions Are Necessary

Ask immediately (do not defer) when:

• Blockers: Issues that prevent further progress
• Security-related: Decisions affecting security
• Destructive operations: Actions that cannot be undone
• External impacts: Changes affecting users or external systems

Work Memory Integration

If questions arise during work, record them in the work memory comment under "要確認事項" (Items to Confirm):

### 要確認事項

1. [ ] {confirmation_item_1}
2. [ ] {confirmation_item_2}

Expected Question Frequency

Target: Minimize questions through context inference and sensible defaults. Issue Start: 0-1 (score C/D only), Implementation: 0, PR Review: 0-1 (critical decisions only). Record non-blocking questions in work memory.

See references/common-principles.md for detailed frequency table by phase.

Session Start Auto-Detection

Automatically detect work state at session start and notify if interrupted work exists.

See references/session-detection.md for details.

Quick Reference

1. Extract Issue number from branch name ({type}/issue-{number}-* pattern)
2. Fetch work memory comment from the Issue
3. Extract and display phase information

See references/phase-mapping.md for phase list.

See references/work-memory-format.md for work memory format.

AI Coding Principles (Summary)

Avoid common AI coding failure patterns: surface assumptions, manage confusion, push back when warranted, enforce simplicity, maintain scope discipline, clean dead code, plan inline, and address all discovered issues.

See references/coding-principles.md for the full principle list and details.

Common Principles (AskUserQuestion Reduction)

Reduce excessive questions: self-check necessity, use defaults when available, infer from context.

See references/common-principles.md for details.

Preflight Guard (All Commands)

Before executing any /rite:* command, run the preflight guard. Resolve {plugin_root} per references/plugin-path-resolution.md.

bash {plugin_root}/hooks/preflight-check.sh --command-id "{current_command_id}" --cwd "$(pwd)"

Replace {current_command_id} with the slash command being executed (e.g., /rite:lint, /rite:pr:review).

If exit code is 1 (blocked), stop execution and display the preflight output. Do NOT proceed.

gh CLI Safety Rules

All gh commands that accept --body or --comment parameters MUST use safe patterns to avoid shell injection:

• Use --body-file with mktemp for multi-line content
• Reference: See references/gh-cli-patterns.md for detailed safe patterns

Never pass user-generated content directly via --body or --comment flags.

Integration

This skill works with:

• All /rite:* commands
• GitHub CLI operations
• Git operations