soba-cli 0.1.0

data/.claude/commands/osoba/revise.md

@@ -0,0 +1,176 @@
+---
+allowed-tools: TodoRead, TodoWrite, Bash, Read, Write, Edit, MultiEdit, Grep, Glob, LS
+description: "Revise implementation based on review feedback"
+---
+
+## Overview
+
+You are a skilled developer responsible for addressing review feedback and fixing issues found during the code review process.  
+In this phase, you will review the PR comments, understand the feedback, make necessary corrections, and ensure the implementation meets all quality standards.
+
+---
+
+## Prerequisites
+
+### Documents
+
+Refer to the following documentation:
+
+- **Coding Standards**: @docs/development/coding-standards.md
+- **Testing Strategy**: @docs/development/testing-strategy.md
+- **Other Development Documents**: @docs/development/INDEX.md
+
+### Expected state of the Issue
+
+- A Pull Request exists with review comments
+- The PR has "status:requires-changes" label
+- Acceptance criteria remain unchanged
+
+---
+
+## Rules
+
+1. Always read and understand ALL review comments before making changes
+2. Address each review comment systematically
+3. Follow TDD when adding or modifying tests
+4. Respect the existing design and architecture
+5. After addressing all feedback, the PR should be ready for re-review
+6. Update the Issue label to "status:review-requested" when complete
+7. If the current directory is under `.git/osoba/`, this is a dedicated codebase created using git worktree
+8. **Work carefully and thoroughly until all issues are resolved, without worrying about time constraints or context compression**
+9. **Code Collective Ownership**: Take responsibility for the entire codebase and proactively fix issues even if they seem unrelated to your changes
+10. **Time Constraints**: Do not fear time constraints or context compression. Work calmly and thoroughly, prioritizing quality above speed
+
+---
+
+## Instructions
+
+### **⚠️ CI Success is Mandatory ⚠️**
+
+**Passing CI is an absolute prerequisite for task completion.**
+
+- Even if CI failures are "unrelated to your current changes", **you must make every effort to fix those issues**
+- All CI problems must be resolved, including test failures, build errors, and lint errors
+- Never mark a task as complete while CI is failing
+
+### Workflow (Overview)
+
+1. Check the PR and review comments
+2. Understand all feedback points
+3. Make necessary corrections
+4. Run tests to verify fixes
+5. **Ensure CI passes completely**
+6. Commit changes with clear messages
+7. Post a summary of changes made
+8. Update Issue labels
+
+---
+
+## Detailed Steps
+
+1. **Check the Pull Request and review comments**
+   - Run `gh pr list --author @me --state open` to find your PR
+   - Run `gh pr view <PR number>` to see PR details
+   - Run `gh pr view <PR number> --comments` to read all review comments
+   - Make a list of all feedback points that need to be addressed
+
+2. **Understand the feedback**
+   - Categorize feedback into:
+     - Code quality issues
+     - Bug fixes
+     - Test coverage gaps
+     - Documentation updates
+     - Style/formatting issues
+   - Prioritize critical issues first
+
+3. **Make corrections systematically**
+   - Address each feedback point one by one
+   - Write/update tests as needed
+   - Ensure each change maintains backward compatibility
+   - Commit frequently with descriptive messages like:
+     ```
+     fix: address review feedback on error handling
+     refactor: improve variable naming as suggested
+     test: add missing test cases for edge conditions
+     ```
+
+4. **Run tests and verify (MANDATORY)**
+   - **⚠️ CRITICAL: All tests in the entire codebase must pass - this is an absolute requirement for acceptance**
+   - Run the full test suite (`bin/rails spec` - NO ARGUMENTS) to ensure nothing is broken # timeout 600000ms
+   - **ABSOLUTE REQUIREMENT**: Never mark as complete without running the full test suite
+   - Verify that all review points have been addressed
+   - Check that the code still meets the original requirements
+   - **Ensure CI passes completely**
+   - If CI fails, fix the issues regardless of their cause
+   - **IMPORTANT**: Execute `bin/rails spec` without any arguments to test the entire codebase
+
+5. **Post a summary comment**
+   - Create a comment on the PR summarizing what was changed:
+   ```bash
+   gh pr comment <PR number> --body "## レビュー指摘対応完了
+
+   以下の指摘事項に対応しました：
+   - ✅ [対応した項目1]
+   - ✅ [対応した項目2]
+   - ✅ [対応した項目3]
+
+   全てのテストがパスすることを確認済みです。
+   再レビューをお願いいたします。"
+   ```
+
+6. **Update Issue labels**
+   - Remove "status:revising" label
+   - Add "status:review-requested" label
+   ```bash
+   gh issue edit <issue number> \
+     --remove-label "status:revising" \
+     --add-label "status:review-requested"
+   ```
+
+---
+
+## Common Review Feedback Types
+
+### Code Quality
+- Variable/function naming improvements
+- Code duplication removal
+- Complex logic simplification
+- Error handling improvements
+
+### Testing
+- Missing test cases
+- Edge case coverage
+- Test data improvements
+- Mock simplification
+
+### Documentation
+- Missing or unclear comments
+- API documentation updates
+- README updates
+
+### Performance
+- Inefficient algorithms
+- Unnecessary database queries
+- Memory leak risks
+
+---
+
+## Best Practices
+
+1. **Be thorough**: Address ALL feedback, not just the easy ones
+2. **Be communicative**: If you disagree with feedback, explain why
+3. **Be proactive**: Look for similar issues elsewhere in the code
+4. **Be respectful**: Thank reviewers for their feedback
+5. **Be complete**: Ensure all tests pass before marking as ready
+
+---
+
+## Important Notes
+
+- **Never mark as "ready for review" if CI is failing**
+- **If CI is failing, you must attempt to fix it even if the cause is unrelated to your current changes**
+- If you cannot address certain feedback, explain why in the PR comments
+- Keep the commit history clean and meaningful
+- Always verify the changes work as expected before updating labels
+- **Task completion requirement: CI must pass completely**
+- **CRITICAL: Always update Issue labels upon task completion, regardless of any circumstances. This is an essential rule to keep the workflow moving forward without interruption.**

data/.claude/commands/soba/implement.md

@@ -0,0 +1,88 @@
+---
+allowed-tools: TodoRead, TodoWrite, Bash, Read, Write, Edit, MultiEdit, Grep, Glob
+description: "TDDによる実装とPR作成"
+---
+
+## 概要
+
+実装計画に基づいてTDDで開発を進め、Pull Requestを作成します。
+
+---
+
+## 前提条件
+
+- Issueコメントに実装計画が存在
+- ラベルは `soba:doing` の状態
+
+---
+
+## ルール
+
+1. **実装計画を必ず確認し従う**
+2. **TDD実践（テストファースト）**
+3. **既存設計・アーキテクチャを尊重**
+4. **実装完了後はPRを作成**
+5. **全テストのパスが必須条件**
+
+---
+
+## 実行手順
+
+1. **Issue・計画確認**
+   - `gh issue view <番号>` で内容確認
+   - `gh issue view <番号> --comments` でコメント確認
+
+2. **テスト作成**
+   - 計画に基づくテストケース作成
+   - Red → Green → Refactor
+
+3. **実装**
+   - 小さな単位でコミット
+   - 意味のあるコミットメッセージ
+
+4. **テスト実行**
+   - 単体テスト実行
+   - 全体テスト実行（必須）
+
+5. **PRテンプレート作成**
+   - `./.tmp/pull-request-<番号>.md` 作成
+
+6. **PR作成**
+   ```bash
+   gh pr create \
+     --title "feat: [機能名] (#<Issue番号>)" \
+     --body-file ./.tmp/pull-request-<番号>.md \
+     --base main
+   ```
+
+7. **Issueコメント**
+   - 「PR #<番号> を作成しました」
+
+8. **ラベル更新**
+   ```bash
+   gh issue edit <番号> \
+     --remove-label "soba:doing" \
+     --add-label "soba:review-requested"
+   ```
+
+---
+
+## PRテンプレート
+
+```markdown
+## 実装完了
+
+fixes #<番号>
+
+### 変更内容
+- [主要な変更点]
+
+### テスト結果
+- 単体テスト: ✅ パス
+- 全体テスト: ✅ パス
+
+### 確認事項
+- [ ] 実装計画に沿った実装
+- [ ] テストカバレッジ確保
+- [ ] 既存機能への影響なし
+```

data/.claude/commands/soba/plan.md

@@ -0,0 +1,93 @@
+---
+allowed-tools: TodoWrite, TodoRead, Bash, Read, Grep, Glob
+description: "GitHub Issueの実装計画を策定"
+---
+
+## 概要
+
+GitHub Issueに対する実装計画を策定し、Issueコメントとして投稿します。
+
+---
+
+## 前提条件
+
+- ラベルは `soba:planning` の状態
+
+---
+
+## ルール
+
+1. **コード修正は行わず、計画策定に専念**
+2. **TDDを前提とした計画設計**
+3. **既存アーキテクチャに従う**
+4. **実行可能な単位にステップ分割**
+5. **テンプレート形式で計画作成**
+6. **完了後ラベルを `soba:ready` に更新**
+
+---
+
+## 実行手順
+
+1. **Issue確認**
+   - `gh issue view <番号>` で内容確認
+   - `gh issue view <番号> --comments` でコメント確認
+
+2. **コードベース調査**
+   - 関連ファイル・過去実装を確認
+   - 影響範囲と依存関係を特定
+
+3. **技術選定**
+   - 使用ライブラリ・パターンを決定
+   - 選定理由を明確化
+
+4. **実装ステップ定義**
+   - テスト可能な単位に分割
+   - 関連ファイル・副作用を記載
+
+5. **テスト・リスク・スケジュール策定**
+   - テスト計画（単体・統合）
+   - リスクと対策
+   - 実装期間の見積もり
+
+6. **計画ファイル作成**
+   - `./.tmp/plan-[slug].md` に保存
+
+7. **コメント投稿**
+   - `gh issue comment <番号> --body-file ./.tmp/plan-[slug].md`
+
+8. **ラベル更新**
+   - `gh issue edit <番号> --remove-label "soba:planning" --add-label "soba:ready"`
+
+---
+
+## テンプレート
+
+```markdown
+# 実装計画: [タイトル]
+
+## 要件概要
+- [目的と背景]
+- [機能要件]
+- [受け入れ条件]
+
+## 設計方針
+- [技術選定と理由]
+- [アーキテクチャ上の考慮点]
+
+## 実装ステップ
+1. [ステップ名]
+   - 作業内容: [詳細]
+   - 関連ファイル: [ファイルパス]
+
+## テスト計画
+- 単体テスト: [対象とケース]
+- 統合テスト: [シナリオ]
+
+## リスクと対策
+- リスク: [内容]
+  対策: [方法]
+
+## スケジュール
+- 見積もり: 合計[X]時間
+- ステップ別: 各[Y]時間
+```

data/.claude/commands/soba/review.md

@@ -0,0 +1,91 @@
+---
+allowed-tools: Bash, Read, Write, Edit, MultiEdit, Grep, Glob, LS
+description: "Review a Pull Request for a soba Issue"
+---
+
+# Review PR
+
+PRレビューを実施します。
+
+## Context
+
+- Issue番号: $ARGUMENTS
+
+## Workflow
+
+### 1. Issue確認
+
+```bash
+GH_PAGER= gh issue view <issue-number>
+GH_PAGER= gh issue view <issue-number> --comments
+```
+
+### 2. PR確認
+
+```bash
+GH_PAGER= gh pr view <PR-number>
+GH_PAGER= gh pr view <PR-number> --json mergeable,mergeStateStatus
+```
+
+### 3. コード変更確認
+
+```bash
+GH_PAGER= gh pr diff <PR-number>
+```
+
+レビュー観点:
+- コーディング規約への準拠
+- テストの実装状況
+- セキュリティ上の懸念
+- 不要な差分の有無
+
+### 4. CI確認（必須・完了まで待機）
+
+```bash
+gh pr checks <PR-number> --watch  # Timeout 600000
+```
+
+⚠️ **重要**: CI完了前にレビュー結果を投稿しないこと
+
+### 5. レビュー結果投稿
+
+`./.tmp/review-result-<issue-number>.md`を作成:
+
+```markdown
+## レビュー結果
+
+- Issue: #<issue-number>
+- PR: #<PR-number>
+
+### ✅ 判定
+- [ ] 承認（LGTM）
+- [ ] 修正要求
+
+### 🔄 マージ状態
+- [ ] コンフリクトなし
+- [ ] コンフリクトあり（要リベース）
+
+### 👍 良い点
+- [実装の良い点]
+
+### 🛠 改善提案
+- [具体的な改善点]
+```
+
+投稿:
+```bash
+gh pr comment <PR-number> --body "$(cat ./.tmp/review-result-<issue-number>.md)"
+```
+
+### 6. ラベル更新
+
+承認の場合:
+```bash
+gh issue edit <issue-number> --remove-label "soba:reviewing" --add-label "soba:done"
+gh pr edit <PR-number> --add-label "soba:lgtm"
+```
+
+修正要求の場合:
+```bash
+gh issue edit <issue-number> --remove-label "soba:reviewing" --add-label "soba:requires-changes"
+```

data/.claude/commands/soba/revise.md

@@ -0,0 +1,76 @@
+---
+allowed-tools: Bash, Read, Write, Edit, MultiEdit, Grep, Glob, LS
+description: "Revise implementation based on review feedback"
+---
+
+# Revise PR
+
+レビュー指摘事項に対応します。
+
+## Context
+
+- Issue番号: $ARGUMENTS
+
+## Workflow
+
+### 1. PR確認
+
+```bash
+GH_PAGER= gh pr list --search "linked:$ARGUMENTS" --state open --json number --jq '.[0].number'
+```
+
+### 2. レビューコメント確認
+
+```bash
+GH_PAGER= gh pr view <PR-number> --comments
+```
+
+### 3. 指摘事項への対応
+
+レビューコメントに基づいて修正を実施:
+- コード品質の改善
+- テストの追加・修正
+- エラーハンドリングの改善
+- 不要な差分の削除
+
+### 4. テスト実行
+
+```bash
+bundle exec rspec  # Timeout 600000
+```
+
+### 5. 修正内容のコミット
+
+```bash
+git add -A
+git commit -m "fix: レビュー指摘事項への対応
+
+- [修正内容の要約]
+"
+git push
+```
+
+### 6. 対応完了コメント
+
+`./.tmp/revise-complete-<issue-number>.md`を作成:
+
+```markdown
+## レビュー指摘対応完了
+
+以下の指摘事項に対応しました：
+- ✅ [対応項目]
+
+全てのテストがパスすることを確認済みです。
+再レビューをお願いいたします。
+```
+
+投稿:
+```bash
+gh pr comment <PR-number> --body "$(cat ./.tmp/revise-complete-<issue-number>.md)"
+```
+
+### 7. ラベル更新
+
+```bash
+gh issue edit <issue-number> --remove-label "soba:revising" --add-label "soba:review-requested"
+```

data/.devcontainer/.env

@@ -0,0 +1,2 @@
+RUBY_VERSION=3.4.5
+COMPOSE_PROJECT_NAME=soba-cli

data/.devcontainer/Dockerfile

@@ -0,0 +1,3 @@
+# Ruby 3.4 for soba CLI project
+FROM mcr.microsoft.com/devcontainers/ruby:3.4
+

data/.devcontainer/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Sho DOUHASHI
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

data/.devcontainer/README.md

@@ -0,0 +1,85 @@
+# Rails DevContainer
+
+A fully-featured development container configuration for Ruby on Rails projects with integrated tools and services.
+
+## Features
+
+- Pre-configured Ruby on Rails development environment
+- Docker Compose setup with Selenium for system testing
+- GitHub CLI, Node.js, Python, and AWS CLI pre-installed
+- Automatic Ruby version synchronization
+- MCP (Model Context Protocol) server integration
+- Volume mounts for SSH, AWS, GitHub, and Claude configurations
+
+## Requirements
+
+- Docker Desktop or Docker Engine
+- Visual Studio Code with Dev Containers extension
+- Git
+
+## Quick Start
+
+1. In your Rails project directory, add this repository as a git subtree:
+   ```bash
+   git subtree add --prefix=.devcontainer --squash git@github.com:douhashi/devcontainer-rails.git main
+   ```
+
+### Visual Studio Code
+
+2. Open your Rails project in VS Code:
+   ```bash
+   code .
+   ```
+
+3. When prompted, click "Reopen in Container" or run the command "Dev Containers: Reopen in Container"
+
+4. Wait for the container to build and post-create scripts to complete
+
+### DevContainer CLI
+
+2. Rebuild and start the development container:
+   ```bash
+   .devcontainer/bin/rebuild
+   .devcontainer/bin/up
+   ```
+
+3. The container will build and start with all configured services
+
+## Updating DevContainer
+
+To update the DevContainer configuration with the latest changes from the upstream repository:
+
+```bash
+git subtree pull --prefix=.devcontainer --squash git@github.com:douhashi/devcontainer-rails.git main
+```
+
+## Configuration
+
+### Ruby Version
+
+The Ruby version is automatically synchronized from `.tool-versions` file. To change it:
+1. Update `.tool-versions` in your Rails project
+2. Run `sync-ruby-version.sh` to update the DevContainer configuration
+3. Rebuild the container
+
+### Services
+
+- **App**: Main Rails application container (ports 5100, 3036)
+- **Selenium**: Chrome browser for system tests (port 4444)
+
+### Environment Variables
+
+- `KAMAL_REGISTRY_USERNAME`: Docker registry username for Kamal deployments
+- `KAMAL_REGISTRY_PASSWORD`: Docker registry password for Kamal deployments
+- `VITE_RUBY_HOST`: Vite development server host (default: 0.0.0.0)
+- `SELENIUM_URL`: Selenium server URL for system tests
+
+## Scripts
+
+- `post-create.sh`: Runs after container creation (installs packages, tools, Rails setup)
+- `post-attach.sh`: Runs each time you attach to the container
+- `sync-ruby-version.sh`: Updates DevContainer Ruby version from .tool-versions
+
+## License
+
+This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.

data/.devcontainer/bin/devcontainer-common.sh

@@ -0,0 +1,50 @@
+#!/bin/bash
+
+# Sync environment variables from .tool-versions to .devcontainer/.env
+sync_envs() {
+    local script_path=".devcontainer/sync-envs.sh"
+    if [ -f "$script_path" ]; then
+        echo "Syncing environment variables..."
+        bash "$script_path"
+    else
+        echo "Warning: $script_path not found, skipping environment sync"
+    fi
+}
+
+# Function to start devcontainer
+up_devcontainer() {
+    local additional_flags="$1"
+    
+    # Sync environment variables before starting devcontainer
+    sync_envs
+    
+    # Get the tmux config path
+    tmux_config_path=~/.config/tmux
+    tmux_resolved_config_path=$(readlink -f "$tmux_config_path")
+    echo "Resolved config path: $tmux_resolved_config_path"
+    
+    # Construct the command to run the devcontainer
+    command="devcontainer up $additional_flags"
+    
+    # Add mount options
+    command+=" --mount type=bind,source=$tmux_resolved_config_path,target=/home/vscode/.config/tmux"
+    
+    # Add additional features
+    command+=" --additional-features='{ \
+            \"ghcr.io/duduribeiro/devcontainer-features/tmux:1\": {} \
+        }'"
+    
+    # Add workspace folder
+    command+=" --workspace-folder ."
+    
+    eval "$command"
+}
+
+# Function to connect to devcontainer
+exec_devcontainer() {
+    # Prepare exec command with environment variables
+    exec_command="devcontainer exec"
+    exec_command+=" --workspace-folder . /bin/bash"
+    
+    eval "$exec_command"
+}