oh-my-customcode 0.69.0 → 0.71.0

package/templates/CLAUDE.md

@@ -104,6 +104,7 @@ oh-my-customcode로 구동됩니다.
 | `/omcustom:fix-refs` | 깨진 참조 수정 |
 | `/omcustom:harness-eval` | 15 SE task 구조적 벤치마크 평가 |
 | `/omcustom:auto-improve` | 개선 사항 자동 적용 워크플로우 |
+| `/omcustom:claude-native` | Claude Code 릴리즈 모니터링 및 이슈 자동 생성 |
 | `/omcustom:improve-report` | eval-core 기반 개선 현황 리포트 |
 | `/omcustom-takeover` | 기존 에이전트/스킬에서 canonical spec 추출 |
 | `/adversarial-review` | 공격자 관점 보안 코드 리뷰 |
@@ -130,8 +131,8 @@ oh-my-customcode로 구동됩니다.
 | `/deep-verify` | 다중 관점 릴리즈 품질 검증 |
 | `/professor-triage` | 이슈 교차 분석 트리아지 (omc_issue_analyzer 댓글 기반) |
 | `/release-plan` | verify-done 이슈 릴리즈 유닛 계획 생성 |
-| `/omcustom:workflow` | YAML 워크플로우 실행 (예: /omcustom:workflow auto-dev) |
-| `/omcustom:workflow:resume` | 중단된 워크플로우 재개 |
+| `/pipeline` | YAML 파이프라인 실행 (예: /pipeline auto-dev) |
+| `/pipeline resume` | 중단된 파이프라인 재개 |
 | `/omcustom:sauron-watch` | 전체 R017 검증 |
 | `/sdd-dev` | Spec-Driven Development 워크플로우 (sdd/ 폴더 기반) |
 | `/structured-dev-cycle` | 6단계 구조적 개발 사이클 (Plan → Verify → Implement → Verify → Compound → Done) |
@@ -150,7 +151,7 @@ project/
 +-- CLAUDE.md                    # 진입점
 +-- .claude/
 |   +-- agents/                  # 서브에이전트 정의 (46 파일)
-|   +-- skills/                  # 스킬 (100 디렉토리)
+|   +-- skills/                  # 스킬 (99 디렉토리)
 |   +-- rules/                   # 전역 규칙 (R000-R021)
 |   +-- hooks/                   # 훅 스크립트 (보안, 검증, HUD)
 |   +-- contexts/                # 컨텍스트 파일 (ecomode)

package/templates/manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.69.0",
+  "version": "0.71.0",
   "lastUpdated": "2026-03-24T00:00:00.000Z",
   "components": [
     {
@@ -18,7 +18,7 @@
       "name": "skills",
       "path": ".claude/skills",
       "description": "Reusable skill modules (includes slash commands)",
-      "files": 100
+      "files": 99
     },
     {
       "name": "guides",

package/templates/workflows/auto-dev.yaml

@@ -1,5 +1,5 @@
 # /omcustom:workflow auto-dev — Full-auto release pipeline
-# Pre-triages professor-labeled issues → triage verify-done → plan → implement → verify → PR → followup
+# Pre-triages open issues → triage verify-done → plan → implement → verify → PR → followup
 
 name: auto-dev
 description: "Full-auto release pipeline: pre-triage → triage → plan → implement → verify → PR → followup"
@@ -9,8 +9,8 @@ error: halt-and-report
 steps:
   - name: pre-triage
     skill: professor-triage
-    description: Run professor-triage on professor-labeled issues that lack verify-done label
-    condition: "issues with label:professor but NOT label:verify-done exist"
+    description: Run professor-triage on open issues that lack verify-done label
+    condition: "open issues without label:verify-done exist"
 
   - name: triage
     skill: professor-triage
@@ -27,7 +27,7 @@ steps:
     foreach: release-group
 
   - name: implement
-    action: implement
+    prompt: "Execute implementation plan with appropriate agents"
     description: Execute implementation plan with appropriate agents
     foreach: planned-issue
 
@@ -36,7 +36,7 @@ steps:
     description: Multi-angle release quality verification
 
   - name: release
-    action: create-pr
+    prompt: "Create release branch and pull request"
     description: Create release branch and pull request
 
   - name: followup

package/templates/.claude/skills/workflow/SKILL.md

@@ -1,68 +0,0 @@
----
-name: omcustom:workflow
-description: Invoke YAML-defined workflows by name — /omcustom:workflow auto-dev runs the full pipeline
-scope: harness
-user-invocable: true
-effort: high
-argument-hint: "<workflow-name> | (no args to list available)"
----
-
-# /omcustom:workflow — Workflow Invocation
-
-## Usage
-
-```
-/omcustom:workflow auto-dev     # Run the auto-dev workflow
-/omcustom:workflow                  # List available workflows
-/omcustom:workflow:resume           # Resume a halted workflow
-```
-
-## Behavior
-
-### List Mode (no arguments or --list flag)
-
-Execute these steps to display available workflows:
-
-1. **Scan built-in workflows**: Use `Glob("workflows/*.yaml")` (NOT templates/) to find all workflow definitions
-2. **Extract metadata**: For each YAML file found, use `Bash` to extract name and description:
-   ```bash
-   for f in workflows/*.yaml; do
-     name=$(grep -m1 '^name:' "$f" | sed 's/^name: *//' | tr -d '"')
-     desc=$(grep -m1 '^description:' "$f" | sed 's/^description: *//' | tr -d '"')
-     echo "  $name — $desc"
-   done
-   ```
-3. **Scan template workflows**: Use `Glob("templates/workflows/*.yaml")` for template examples
-4. **Extract template metadata**: Same extraction as step 2 for `templates/workflows/*.yaml`
-5. **Display formatted output**:
-   ```
-   Available workflows:
-     {name} — {description}
-     {name} — {description}
-
-   Template workflows (in templates/workflows/):
-     {name} — {description}
-   ```
-6. If no workflows found, display: "No workflows found in workflows/ directory."
-7. If YAML parsing fails for a file, skip it and show: `  {filename} — (parse error, skipped)`
-
-### Run Mode (with workflow name)
-
-1. Validate workflow exists: `workflows/{name}.yaml`
-2. Load and validate YAML structure
-3. Announce: `[Workflow] Starting {name} — {step_count} steps`
-4. Invoke workflow-runner skill with the loaded definition
-5. Report completion or failure
-
-### Resume Mode (/omcustom:workflow:resume)
-
-1. Check for state file: `/tmp/.claude-workflow-*-{PPID}.json`
-2. If found: show halted workflow name and failed step
-3. Ask: "Resume from step {N} ({step_name})?"
-4. Re-invoke workflow-runner from the failed step
-
-## Error Handling
-
-- Workflow not found → list available workflows with suggestion
-- YAML parse error → report with line number
-- Step failure → halt-and-report per workflow error policy

package/templates/.claude/skills/workflow-resume/SKILL.md

@@ -1,26 +0,0 @@
----
-name: omcustom:workflow:resume
-description: Resume a halted workflow from its last failure point
-scope: harness
-user-invocable: true
-effort: medium
----
-
-# /omcustom:workflow:resume — Resume Halted Workflow
-
-## Usage
-
-```
-/omcustom:workflow:resume            # Find and resume the most recent halted workflow
-```
-
-## Behavior
-
-1. Scan `/tmp/.claude-workflow-*-$PPID.json` for state files
-2. If none found: "No halted workflows found."
-3. If found: display workflow name, failed step, error message
-4. Options:
-   - **Retry** — Re-execute the failed step
-   - **Skip** — Mark failed step as skipped, continue to next
-   - **Abort** — Delete state file, cancel workflow
-5. On resume: invoke workflow-runner with state file context

package/templates/.claude/skills/workflow-runner/SKILL.md

@@ -1,75 +0,0 @@
----
-name: workflow-runner
-description: Execute YAML-defined workflow pipelines — parse, validate, and run multi-step skill chains
-scope: harness
-user-invocable: false
-effort: high
----
-
-# Workflow Runner
-
-## Purpose
-
-Core engine for the workflow system. Parses YAML workflow definitions from `workflows/` directory, validates step structure, and executes each step sequentially by invoking the referenced skills or actions.
-
-## Execution Protocol
-
-### 1. Load Workflow
-
-Read the specified YAML file from `workflows/{name}.yaml`. Validate:
-- Required fields: `name`, `description`, `steps[]`
-- Each step has either `skill:` or `action:` (not both)
-- Referenced skills exist in `.claude/skills/`
-- Skill names must match `^[a-z0-9-]+$` (kebab-case only) — reject path traversal attempts
-- Action values must be one of: `implement`, `create-pr` — reject unknown actions with error
-
-### 2. Execute Steps
-
-Process steps top-to-bottom:
-
-**Skill steps** (`skill: name`):
-- Invoke via Skill tool: `Skill(skill: "{name}")`
-- Capture output for next step's `input` reference
-
-**Action steps** (`action: name`):
-- `implement` — Delegate to appropriate agents based on issue domain
-- `create-pr` — Delegate to mgr-gitnerd for branch creation, push, PR
-
-**Foreach steps** (`foreach: collection`):
-- Iterate over collection from previous step output
-- Execute the step once per item
-
-### 3. Error Handling
-
-Based on workflow `error` field:
-- `halt-and-report` — Stop execution, save state, report failure with context
-- State saved to `/tmp/.claude-workflow-{name}-{PPID}.json`
-
-### 4. State Tracking
-
-Track per-step state:
-```json
-{
-  "workflow": "{name}",
-  "started": "ISO-8601",
-  "status": "running|completed|halted",
-  "current_step": 0,
-  "steps": [
-    {"name": "triage", "status": "completed", "duration_ms": 5000},
-    {"name": "plan", "status": "running"}
-  ]
-}
-```
-
-### 5. Completion
-
-On all steps completed:
-- Delete state file
-- Report summary with per-step durations
-- Output final results
-
-## Notes
-
-- This skill is invoked by the workflow bridge skill (workflow/SKILL.md)
-- It does NOT appear in slash commands (user-invocable: false)
-- All file writes delegated to subagents per R010