oh-my-customcode 0.126.1 → 0.128.0

package/README.md

@@ -13,7 +13,7 @@
 
 **[한국어 문서 (Korean)](./README_ko.md)**
 
-49 agents. 116 skills. 22 rules. One command.
+49 agents. 117 skills. 22 rules. One command.
 
 ```bash
 npm install -g oh-my-customcode && cd your-project && omcustom init
@@ -132,7 +132,7 @@ Each agent declares its tools, model, memory scope, and limitations in YAML fron
 
 ---
 
-### Skills (116)
+### Skills (117)
 
 | Category | Count | Includes |
 |----------|-------|----------|
@@ -272,7 +272,7 @@ your-project/
 ├── CLAUDE.md                   # Entry point
 ├── .claude/
 │   ├── agents/                 # 49 agent definitions
-│   ├── skills/                 # 116 skill modules
+│   ├── skills/                 # 117 skill modules
 │   ├── rules/                  # 22 governance rules (R000-R021)
 │   ├── hooks/                  # 15 lifecycle hook scripts
 │   ├── schemas/                # Tool input validation schemas

package/dist/cli/index.js

@@ -2334,7 +2334,7 @@ var init_package = __esm(() => {
     workspaces: [
       "packages/*"
     ],
-    version: "0.126.1",
+    version: "0.128.0",
     description: "Batteries-included agent harness for Claude Code",
     type: "module",
     bin: {

package/dist/index.js

@@ -2014,7 +2014,7 @@ var package_default = {
   workspaces: [
     "packages/*"
   ],
-  version: "0.126.1",
+  version: "0.128.0",
   description: "Batteries-included agent harness for Claude Code",
   type: "module",
   bin: {

package/package.json

@@ -3,7 +3,7 @@
   "workspaces": [
     "packages/*"
   ],
-  "version": "0.126.1",
+  "version": "0.128.0",
   "description": "Batteries-included agent harness for Claude Code",
   "type": "module",
   "bin": {

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

@@ -0,0 +1,82 @@
+---
+name: goal
+description: Disciplined goal-to-execution workflow for any user task. Parses objective, asks only for materially missing requirements via ambiguity-gate, inspects repo via idea, plans via sdd-dev or deep-plan, executes safely under project conventions, verifies completion per R020, and reports changed files with evidence. Use when user invokes /goal <task>.
+version: 1.0.0
+scope: core
+---
+
+# /goal — Disciplined Goal-to-Execution Workflow
+
+Apply project discipline (planning, verification, cleanup, review) to any user-provided task. Acts as a thin orchestrator that routes to existing oh-my-customcode skills rather than duplicating logic.
+
+## Usage
+
+```
+/goal <task description>
+```
+
+Example: `/goal Add a /weekly-summary command that aggregates last 7 days of git activity`
+
+## Workflow
+
+1. **Parse objective**: Treat `<task>` as the concrete goal. Do NOT expand scope beyond what was asked.
+2. **Gap detection**: Invoke `ambiguity-gate` skill. Ask only for materially missing or risky requirements — no over-clarification on details that can be inferred.
+3. **Repo inspection**: Invoke `idea` skill (NL-intent codebase analysis) to identify relevant files, dependencies, and existing assets.
+4. **Plan generation** (scope-dependent):
+   - Trivial scope (single file, <30 LOC, no API design): proceed with brief inline plan.
+   - Non-trivial scope: invoke `sdd-dev` or `deep-plan` for research-validated planning.
+5. **Safe execution**: Follow R001 (safety), R009 (parallel), R010 (delegation). Delegate ALL file modifications to specialist agents.
+6. **Completion verification**: Apply R020 — verify ACTUAL outcome before declaring `[Done]`. Run task-type-specific checks (lint, build, test).
+7. **Report**: Output changed files, verification evidence, and remaining risks.
+
+## Output Format
+
+```
+[Goal] {original task verbatim}
+[Plan] {brief plan or reference to deep-plan/sdd-dev output}
+[Changes] {file list with paths}
+[Verified] {evidence — exit codes, test counts, build output}
+[Risks] {remaining concerns or "none"}
+```
+
+## When to Use
+
+- Generic multi-step task without obvious specialist routing
+- User wants a single, memorable entry point for "do this task with full discipline"
+- Work that benefits from planning + verification + structured reporting
+
+## When NOT to Use
+
+| Scenario | Use Instead |
+|----------|-------------|
+| Pure research/analysis | `research`, `idea`, `memory-recall` |
+| Specialist domain task | Routing skills (`dev-lead-routing`, `de-lead-routing`, `qa-lead-routing`) |
+| Trivial single-file edit | Delegate directly to specialist agent |
+| Bug debugging | `superpowers:systematic-debugging` |
+
+## Integration with Existing Skills
+
+| Stage | Skill | Role |
+|-------|-------|------|
+| Gap detection | `ambiguity-gate` | Score request clarity, ask only critical gaps |
+| Repo inspection | `idea` | NL-intent codebase analysis |
+| Planning (research-validated) | `deep-plan` | research → plan → verify cycle |
+| Planning (SDD discipline) | `sdd-dev` | Stage gates with planning-first workflow |
+| Verification | `superpowers:verification-before-completion` | Evidence before assertions |
+| Reporting | `result-aggregation` | Concise output composition |
+
+## Design Notes
+
+This skill is intentionally a **thin wrapper / orchestrator**. It does NOT duplicate planning, gap-detection, or verification logic. Its value:
+
+- Single memorable command for the disciplined workflow
+- Stable entry point that routes to whichever underlying skills are best at the moment
+- Documented contract that callers can rely on regardless of internal skill evolution
+
+If a future skill replaces `idea` or `sdd-dev`, only the integration table updates — `/goal` remains stable.
+
+## Cross-References
+
+- Issue: #1109 — Port /goal workflow to Claude Code skill surface
+- Rules: R001 (safety), R003 (response style), R010 (delegation), R020 (completion verification)
+- Original Codex /goal workflow this ports from: discipline-first goal execution

package/templates/.claude/skills/omcustom-release-notes/SKILL.md

@@ -99,13 +99,51 @@ The generated notes can be:
 2. **File**: Written to `release_notes.md` for review before use
 3. **Update**: Used with `gh release edit v{VERSION} --notes "{notes}"`
 
+### Phase 5: Promote `## [Unreleased]` in CHANGELOG.md (Optional but Recommended)
+
+After generating release notes, promote any pending `## [Unreleased]` entries to a versioned section so `release.yml` (awk extract at line ~217) finds the authored notes instead of falling back to GitHub auto-generated content.
+
+```bash
+# Promote [Unreleased] to [VERSION] with today's date
+DATE=$(date -u +%Y-%m-%d)
+python3 - "$VERSION" "$DATE" <<'PY'
+import sys, re, pathlib
+version, date = sys.argv[1], sys.argv[2]
+path = pathlib.Path("CHANGELOG.md")
+text = path.read_text()
+header = f"## [{version}] - {date}"
+if re.search(rf"^## \[{re.escape(version)}\]", text, flags=re.M):
+    print(f"[skip] [{version}] section already exists — manual reconciliation needed")
+    sys.exit(0)
+new = re.sub(
+    r"^## \[Unreleased\]\s*\n",
+    f"## [Unreleased]\n\n{header}\n",
+    text,
+    count=1,
+    flags=re.M,
+)
+if new == text:
+    print("[error] [Unreleased] section not found — CHANGELOG.md format unexpected")
+    sys.exit(1)
+path.write_text(new)
+print(f"[ok] promoted [Unreleased] -> [{version}]")
+PY
+```
+
+Behavior:
+- If `## [Unreleased]` content is empty, the promoted `## [VERSION]` will also be empty — `release.yml` falls back to auto-generated notes (existing behavior preserved).
+- If `## [VERSION]` already exists (re-run, manual edit), the script skips with a log message — no overwrite.
+- The skill caller commits the change: `git add CHANGELOG.md && git commit -m "chore(changelog): promote [Unreleased] to [VERSION]"`
+
+This is **optional** — the skill's release-notes generation (Phases 1-4) works independently. Phase 5 only ensures CHANGELOG consistency for projects that maintain Keep a Changelog format.
+
 ## Integration
 
 This skill is designed to be used during the release process:
 
 ```
 /omcustom:npm-version patch|minor|major  ->  version bump
-/omcustom-release-notes {version}         ->  generate notes
+/omcustom-release-notes {version}         ->  generate notes + promote [Unreleased] (Phase 5)
 mgr-gitnerd: gh release create           ->  create release with notes
 ```
 
@@ -115,6 +153,8 @@ mgr-gitnerd: gh release create           ->  create release with notes
 - Uses git history and gh CLI for data gathering
 - Claude Code analyzes and generates notes in-context
 - Resource count changes auto-detected from CLAUDE.md history
+- Phase 5 promotion is idempotent — safe to re-run; skips if `## [VERSION]` exists
+- See `CONTRIBUTING.md` for [Unreleased] entry guidance during PR authoring
 
 ## Permission Mode
 

package/templates/CLAUDE.md

@@ -116,7 +116,7 @@ project/
 +-- CLAUDE.md                    # 진입점
 +-- .claude/
 |   +-- agents/                  # 서브에이전트 정의 (49 파일)
-|   +-- skills/                  # 스킬 (116 디렉토리)
+|   +-- skills/                  # 스킬 (117 디렉토리)
 |   +-- rules/                   # 전역 규칙 (R000-R022)
 |   +-- hooks/                   # 훅 스크립트 (보안, 검증, HUD)
 |   +-- contexts/                # 컨텍스트 파일 (ecomode)

package/templates/manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.126.1",
+  "version": "0.128.0",
   "lastUpdated": "2026-04-24T07:30:00.000Z",
   "omcustomMinClaudeCode": "2.1.121",
   "omcustomMinClaudeCodeReason": "Sensitive-path direct Write/Edit on .claude/** under bypassPermissions (R010 deprecation, #1101)",
@@ -20,7 +20,7 @@
       "name": "skills",
       "path": ".claude/skills",
       "description": "Reusable skill modules (includes slash commands)",
-      "files": 116
+      "files": 117
     },
     {
       "name": "guides",