@sk8metal/michi-cli 0.0.8 → 0.1.0

package/scripts/pr-automation.ts

@@ -4,7 +4,6 @@
 
 import { Octokit } from '@octokit/rest';
 import { config } from 'dotenv';
-import { loadProjectMeta } from './utils/project-meta.js';
 
 config();
 

package/scripts/pre-flight-check.ts

@@ -81,7 +81,7 @@ function checkProjectJson(): { errors: string[], warnings: string[] } {
   let projectMeta: any;
   try {
     projectMeta = JSON.parse(readFileSync(projectJsonPath, 'utf-8'));
-  } catch (error) {
+  } catch {
     errors.push('❌ project.json のパースに失敗しました');
     return { errors, warnings };
   }

package/scripts/pre-publish-check.sh

@@ -0,0 +1,311 @@
+#!/bin/bash
+
+# Michi Pre-Publish Check Script
+# NPMパッケージ公開前の動作確認を自動実行
+
+set -e  # エラー時に即座に終了
+
+# カラー出力用
+RED='\033[0;31m'
+GREEN='\033[0;32m'
+YELLOW='\033[1;33m'
+BLUE='\033[0;34m'
+NC='\033[0m' # No Color
+
+# プロジェクトルートディレクトリ
+PROJECT_ROOT="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
+cd "$PROJECT_ROOT"
+
+echo -e "${BLUE}========================================${NC}"
+echo -e "${BLUE}Michi Pre-Publish Check${NC}"
+echo -e "${BLUE}========================================${NC}"
+echo ""
+
+# テスト用feature名（タイムスタンプ付き）
+TEST_FEATURE="test-pre-publish-$(date +%s)"
+
+# クリーンアップ関数
+cleanup() {
+  echo -e "\n${YELLOW}Cleaning up test files...${NC}"
+  rm -rf ".kiro/specs/${TEST_FEATURE}" 2>/dev/null || true
+  echo -e "${GREEN}✓ Cleanup completed${NC}"
+}
+
+# エラー時のクリーンアップ
+trap cleanup EXIT
+
+# ステップカウンター
+STEP=1
+
+echo_step() {
+  echo -e "\n${BLUE}[Step ${STEP}] $1${NC}"
+  STEP=$((STEP + 1))
+}
+
+echo_success() {
+  echo -e "${GREEN}✓ $1${NC}"
+}
+
+echo_error() {
+  echo -e "${RED}✗ $1${NC}"
+}
+
+echo_info() {
+  echo -e "${YELLOW}ℹ $1${NC}"
+}
+
+# ========================================
+# Step 1: TypeScriptビルド確認
+# ========================================
+echo_step "TypeScript Build Check"
+if npm run build; then
+  echo_success "Build succeeded"
+else
+  echo_error "Build failed"
+  exit 1
+fi
+
+# ========================================
+# Step 2: テスト実行（既存機能の回帰確認）
+# ========================================
+echo_step "Running Tests (Regression Check)"
+if npm test; then
+  echo_success "All tests passed"
+else
+  echo_error "Some tests failed"
+  exit 1
+fi
+
+# ========================================
+# Step 3: テスト用featureの初期化
+# ========================================
+echo_step "Initializing Test Feature: ${TEST_FEATURE}"
+mkdir -p ".kiro/specs/${TEST_FEATURE}"
+
+# 最小限のspec.jsonを作成
+cat > ".kiro/specs/${TEST_FEATURE}/spec.json" <<EOF
+{
+  "feature": "${TEST_FEATURE}",
+  "description": "Pre-publish test feature",
+  "status": "draft",
+  "milestones": {},
+  "confluence": {},
+  "jira": {}
+}
+EOF
+
+# 最小限のrequirements.mdを作成
+cat > ".kiro/specs/${TEST_FEATURE}/requirements.md" <<EOF
+# Requirements: ${TEST_FEATURE}
+
+This is a test feature for pre-publish verification.
+EOF
+
+# 最小限のdesign.mdを作成
+cat > ".kiro/specs/${TEST_FEATURE}/design.md" <<EOF
+# Design: ${TEST_FEATURE}
+
+This is a test feature for pre-publish verification.
+EOF
+
+# 最小限のtasks.mdを作成（新ワークフロー構造）
+cat > ".kiro/specs/${TEST_FEATURE}/tasks.md" <<EOF
+# tasks.md
+
+## Phase 0.1: 要件定義
+
+### Story 0.1.1: 要件定義書作成
+
+## Phase 0.2: 設計
+
+### Story 0.2.1: 基本設計
+
+## Phase 2: TDD実装
+
+### Story 2.1: プロジェクトセットアップ
+
+## Phase 4: リリース準備
+
+### Story 4.1: 本番環境構築
+
+## Phase 5: リリース
+
+### Story 5.1: ステージング環境デプロイ
+
+Day 1（月）: 営業日ベース
+EOF
+
+echo_success "Test feature initialized"
+
+# ========================================
+# Step 4: 新フェーズの動作確認
+# ========================================
+echo_step "Testing New Phases (0.3-0.4, 1, A, B)"
+
+# Phase 0.3: テストタイプ選択
+echo_info "Testing Phase 0.3: test-type-selection"
+if npm run phase:run "${TEST_FEATURE}" test-type-selection > /dev/null 2>&1; then
+  echo_success "Phase 0.3 succeeded"
+else
+  echo_error "Phase 0.3 failed"
+  exit 1
+fi
+
+# Phase 0.4: テスト仕様書作成
+echo_info "Testing Phase 0.4: test-spec"
+if npm run phase:run "${TEST_FEATURE}" test-spec > /dev/null 2>&1; then
+  echo_success "Phase 0.4 succeeded"
+else
+  echo_error "Phase 0.4 failed"
+  exit 1
+fi
+
+# Phase 1: 環境構築
+echo_info "Testing Phase 1: environment-setup"
+if npm run phase:run "${TEST_FEATURE}" environment-setup > /dev/null 2>&1; then
+  echo_success "Phase 1 succeeded"
+else
+  echo_error "Phase 1 failed"
+  exit 1
+fi
+
+# Phase A: PR前自動テスト
+echo_info "Testing Phase A: phase-a"
+if npm run phase:run "${TEST_FEATURE}" phase-a > /dev/null 2>&1; then
+  echo_success "Phase A succeeded"
+else
+  echo_error "Phase A failed"
+  exit 1
+fi
+
+# Phase B: リリース準備テスト
+echo_info "Testing Phase B: phase-b"
+if npm run phase:run "${TEST_FEATURE}" phase-b > /dev/null 2>&1; then
+  echo_success "Phase B succeeded"
+else
+  echo_error "Phase B failed"
+  exit 1
+fi
+
+# ========================================
+# Step 5: バリデーションの確認
+# ========================================
+echo_step "Testing Phase Validations"
+
+# Phase 0.3
+echo_info "Validating Phase 0.3"
+if npm run validate:phase "${TEST_FEATURE}" test-type-selection > /dev/null 2>&1; then
+  echo_success "Phase 0.3 validation passed"
+else
+  echo_error "Phase 0.3 validation failed"
+  exit 1
+fi
+
+# Phase 0.4
+echo_info "Validating Phase 0.4"
+if npm run validate:phase "${TEST_FEATURE}" test-spec > /dev/null 2>&1; then
+  echo_success "Phase 0.4 validation passed"
+else
+  echo_error "Phase 0.4 validation failed"
+  exit 1
+fi
+
+# Phase 1
+echo_info "Validating Phase 1"
+if npm run validate:phase "${TEST_FEATURE}" environment-setup > /dev/null 2>&1; then
+  echo_success "Phase 1 validation passed"
+else
+  echo_error "Phase 1 validation failed"
+  exit 1
+fi
+
+# Phase A
+echo_info "Validating Phase A"
+if npm run validate:phase "${TEST_FEATURE}" phase-a > /dev/null 2>&1; then
+  echo_success "Phase A validation passed"
+else
+  echo_error "Phase A validation failed"
+  exit 1
+fi
+
+# Phase B
+echo_info "Validating Phase B"
+if npm run validate:phase "${TEST_FEATURE}" phase-b > /dev/null 2>&1; then
+  echo_success "Phase B validation passed"
+else
+  echo_error "Phase B validation failed"
+  exit 1
+fi
+
+# ========================================
+# Step 6: 既存フェーズの動作確認（回帰テスト）
+# ========================================
+echo_step "Testing Existing Phases (Regression)"
+
+# Phase 0.1: requirements
+echo_info "Testing Phase 0.1: requirements (dry-run)"
+# Confluenceを作成しないため、実際には実行しない（バリデーションのみ）
+if npm run validate:phase "${TEST_FEATURE}" requirements > /dev/null 2>&1; then
+  echo_success "Phase 0.1 validation passed"
+else
+  echo_error "Phase 0.1 validation failed"
+  exit 1
+fi
+
+# Phase 0.2: design
+echo_info "Testing Phase 0.2: design (dry-run)"
+if npm run validate:phase "${TEST_FEATURE}" design > /dev/null 2>&1; then
+  echo_success "Phase 0.2 validation passed"
+else
+  echo_error "Phase 0.2 validation failed"
+  exit 1
+fi
+
+# Phase 0.5-0.6: tasks
+echo_info "Testing Phase 0.5-0.6: tasks (dry-run)"
+if npm run validate:phase "${TEST_FEATURE}" tasks > /dev/null 2>&1; then
+  echo_success "Phase 0.5-0.6 validation passed"
+else
+  echo_error "Phase 0.5-0.6 validation failed"
+  exit 1
+fi
+
+# ========================================
+# Step 7: CLIヘルプ表示確認
+# ========================================
+echo_step "Checking CLI Help Messages"
+
+echo_info "phase:run --help"
+if npm run phase:run 2>&1 | grep -q "Available Phases"; then
+  echo_success "phase:run help message OK"
+else
+  echo_error "phase:run help message missing"
+  exit 1
+fi
+
+echo_info "validate:phase --help"
+if npm run validate:phase 2>&1 | grep -q "Available Phases"; then
+  echo_success "validate:phase help message OK"
+else
+  echo_error "validate:phase help message missing"
+  exit 1
+fi
+
+# ========================================
+# 完了
+# ========================================
+echo ""
+echo -e "${GREEN}========================================${NC}"
+echo -e "${GREEN}✓ All Pre-Publish Checks Passed!${NC}"
+echo -e "${GREEN}========================================${NC}"
+echo ""
+echo -e "${BLUE}Summary:${NC}"
+echo -e "  ✓ TypeScript build succeeded"
+echo -e "  ✓ All tests passed ($(npm test 2>&1 | grep -oP '\d+ passed' || echo 'unknown'))"
+echo -e "  ✓ New phases (0.3-0.4, 1, A, B) working"
+echo -e "  ✓ Phase validations working"
+echo -e "  ✓ Existing phases regression OK"
+echo -e "  ✓ CLI help messages OK"
+echo ""
+echo -e "${GREEN}Ready for npm publish!${NC}"
+echo ""

package/scripts/quick-verify.sh

@@ -0,0 +1,115 @@
+#!/bin/bash
+
+# 新規実装機能のクイック動作確認スクリプト
+# Usage: ./scripts/quick-verify.sh
+
+set -e
+
+echo "🚀 新規実装機能のクイック動作確認"
+echo "======================================"
+echo ""
+
+# 色の定義
+GREEN='\033[0;32m'
+YELLOW='\033[1;33m'
+RED='\033[0;31m'
+NC='\033[0m' # No Color
+
+# 1. ビルド確認
+echo "📦 Step 1: ビルド確認"
+echo "--------------------------------------"
+if npm run build > /dev/null 2>&1; then
+    echo -e "${GREEN}✅ ビルド成功${NC}"
+else
+    echo -e "${RED}❌ ビルド失敗${NC}"
+    exit 1
+fi
+echo ""
+
+# 2. プロジェクトメタデータ確認
+echo "📋 Step 2: プロジェクトメタデータ確認"
+echo "--------------------------------------"
+if [ -f ".kiro/project.json" ]; then
+    echo -e "${GREEN}✅ .kiro/project.json が存在します${NC}"
+    cat .kiro/project.json | head -5
+else
+    echo -e "${YELLOW}⚠️  .kiro/project.json が存在しません${NC}"
+    echo "   作成しています..."
+    mkdir -p .kiro
+    cat > .kiro/project.json << 'EOF'
+{
+  "projectId": "michi",
+  "projectName": "Michi",
+  "jiraProjectKey": "MICHI",
+  "confluenceLabels": ["michi", "ai-development", "claude-code"],
+  "status": "active",
+  "team": ["Development Team"],
+  "stakeholders": ["Product Team", "Engineering Team"],
+  "repository": "https://github.com/sk8metalme/michi",
+  "description": "AI駆動開発を支援するプロジェクト管理・ドキュメント管理フレームワーク"
+}
+EOF
+    echo -e "${GREEN}✅ .kiro/project.json を作成しました${NC}"
+fi
+echo ""
+
+# 3. 単体テスト
+echo "🧪 Step 3: 単体テスト実行"
+echo "--------------------------------------"
+echo "新規実装機能のテストを実行します..."
+if node dist/scripts/test-new-features.js 2>&1 | grep -q "テスト成功"; then
+    echo -e "${GREEN}✅ 単体テスト成功${NC}"
+else
+    echo -e "${YELLOW}⚠️  一部のテストがスキップされました（Confluence環境変数未設定）${NC}"
+fi
+echo ""
+
+# 4. 統合テスト
+echo "🔗 Step 4: 統合テスト実行"
+echo "--------------------------------------"
+echo "ワークフローの統合テストを実行します..."
+if npx tsx scripts/test-workflow-stages.ts --feature health-check-endpoint 2>&1 | grep -q "Workflow completed successfully"; then
+    echo -e "${GREEN}✅ 統合テスト成功${NC}"
+else
+    echo -e "${RED}❌ 統合テスト失敗${NC}"
+    exit 1
+fi
+echo ""
+
+# 5. 生成ファイル確認
+echo "📄 Step 5: 生成ファイル確認"
+echo "--------------------------------------"
+if [ -f ".kiro/specs/health-check-endpoint/test-report.md" ]; then
+    echo -e "${GREEN}✅ テストレポートが生成されました${NC}"
+    echo "   場所: .kiro/specs/health-check-endpoint/test-report.md"
+else
+    echo -e "${RED}❌ テストレポートが見つかりません${NC}"
+fi
+
+if [ -f ".kiro/specs/health-check-endpoint/release-notes-v1.0.0.md" ]; then
+    echo -e "${GREEN}✅ リリースノートが生成されました${NC}"
+    echo "   場所: .kiro/specs/health-check-endpoint/release-notes-v1.0.0.md"
+else
+    echo -e "${RED}❌ リリースノートが見つかりません${NC}"
+fi
+echo ""
+
+# 6. サマリー
+echo "======================================"
+echo "📊 動作確認サマリー"
+echo "======================================"
+echo ""
+echo -e "${GREEN}✅ すべての動作確認が完了しました！${NC}"
+echo ""
+echo "生成されたファイル:"
+echo "  - テストレポート: .kiro/specs/health-check-endpoint/test-report.md"
+echo "  - リリースノート: .kiro/specs/health-check-endpoint/release-notes-v1.0.0.md"
+echo ""
+echo "詳細な手順書:"
+echo "  docs/verification-guide.md"
+echo ""
+echo "次のステップ:"
+echo "  1. 生成されたファイルを確認"
+echo "  2. カスタム設定でテスト（RELEASE_VERSION=v2.0.0 など）"
+echo "  3. Confluence連携をテスト（環境変数設定後）"
+echo ""