oh-my-customcode 0.127.0 → 0.129.0

package/dist/cli/index.js

@@ -2334,7 +2334,7 @@ var init_package = __esm(() => {
     workspaces: [
       "packages/*"
     ],
-    version: "0.127.0",
+    version: "0.129.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.127.0",
+  version: "0.129.0",
   description: "Batteries-included agent harness for Claude Code",
   type: "module",
   bin: {

package/package.json

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

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

@@ -1,6 +1,7 @@
 ---
 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
 ---
 

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

@@ -3,7 +3,7 @@ name: omcustom-release-notes
 description: Generate structured release notes from git history and closed issues within Claude Code session
 scope: harness
 user-invocable: true
-argument-hint: "<version> [--previous-tag <tag>]"
+argument-hint: "<version> [--previous-tag <tag>] | --backfill <range>"
 ---
 
 # Release Notes Generator
@@ -19,6 +19,7 @@ Replaces the CI-based `release-notes.yml` workflow that previously used Claude A
 ```
 /omcustom-release-notes 0.36.0
 /omcustom-release-notes 0.36.0 --previous-tag v0.35.3
+/omcustom-release-notes --backfill v0.36.0..v0.127.0
 ```
 
 ## Workflow
@@ -99,13 +100,101 @@ 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.
+
+## Backfill Mode
+
+For projects with historical CHANGELOG.md gaps (releases shipped without `[Unreleased]` promotion), the skill provides a deterministic batch backfill.
+
+### Usage
+
+```bash
+python3 scripts/backfill_changelog.py <START_TAG>..<END_TAG> [--output FILE]
+```
+
+Or invoked via skill: `/omcustom-release-notes --backfill v0.36.0..v0.127.0`
+
+### Behavior
+
+For each tag in range (in reverse semver order), the script:
+
+1. Determines previous tag (semver-immediately-before)
+2. Reads `git log <prev>..<tag> --pretty=%s --no-merges` to extract commit subjects
+3. Maps Conventional Commits prefix to Keep a Changelog category:
+   - `feat` → Added
+   - `fix` → Fixed
+   - `security` → Security
+   - `perf`, `refactor`, `chore`, `build`, `deps`, `revert` → Changed
+   - `docs`, `test`, `ci`, `style` → SKIPPED (internal-only, unless `!` breaking marker)
+   - Non-conventional → Changed (full subject as message)
+4. Special handling for `release:` / `chore(release):` commits — extracts description after version (e.g., `release: v0.127.0 — DESC` → DESC under Changed)
+5. Extracts issue refs (`#NNN`) and appends as `(#1, #2)` suffix
+6. Renders per-version section with categories sorted: Added, Changed, Fixed, Security, Removed, Deprecated
+7. Empty sections (zero qualifying commits) render as `_No user-visible changes (internal only)._`
+
+### Output
+
+Markdown text suitable for prepending to CHANGELOG.md between `## [Unreleased]` and the first existing version section.
+
+### When to Use
+
+- Adopting Keep a Changelog format on an existing project with N historical releases
+- Recovering after a CHANGELOG drift period
+- One-time bulk operation — afterward, use Phase 5 promotion (forward-looking) for ongoing maintenance
+
+### Limitations
+
+- Only as good as commit message quality. Squash-merge release commits typically contain only the PR title — backfill produces 1-2 lines per version, not exhaustive change lists
+- Non-conventional or pre-Conventional Commits adoption commits land in Changed
+- Manual curation may improve specific entries; the script provides the baseline
+
+### Tests
+
+`tests/scripts/test_backfill_changelog.py` covers parser correctness, semver sorting, category mapping, edge cases (40 tests).
+
 ## 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 +204,9 @@ 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
+- For one-time historical backfill, see Backfill Mode above (script: `scripts/backfill_changelog.py`)
 
 ## Permission Mode
 

package/templates/manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.127.0",
+  "version": "0.129.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)",