メニュー
Curate user-facing project changelog entries from Logics release notes or completed tasks. Use when Codex should turn `logics/RELEASE_NOTES.md` into a cleaner project-level `logics/CHANGELOG.md` and remove internal references/noise.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | logics-changelog-curator |
| description | Curate user-facing project changelog entries from Logics release notes or completed tasks. Use when Codex should turn `logics/RELEASE_NOTES.md` into a cleaner project-level `logics/CHANGELOG.md` and remove internal references/noise. |
This skill is for project repositories importing the kit under logics/skills/.
It is not the canonical release workflow for the kit repository itself. For kit releases, use:
logics-version-changelog-manager for VERSION + changelogs/CHANGELOGS_<version>.mdlogics-version-release-manager for tag and GitHub release publicationpython logics/skills/logics-changelog-curator/scripts/curate_changelog.py --in logics/RELEASE_NOTES.md --out logics/CHANGELOG.md
The curation script stays deterministic. When you want a bounded wording review after generation, use:
python logics/skills/logics.py flow assist summarize-changelog --format json
Lint and validate the Logics Markdown conventions. Use when Codex should verify filenames, top headings, and required indicators across `logics/request`, `logics/backlog`, `logics/tasks`, `logics/product`, and `logics/architecture`, and report inconsistencies.
Update Logics indicators consistently. Use when Codex should update request/backlog/task indicators (`From version`, `Understanding`, `Confidence`, `Progress`, `Complexity`, `Theme`) or companion doc indicators in `logics/product|architecture/*.md` such as `Date`, `Status`, `Drivers`, related refs, and `Reminder`.
Manage this repository's Logics workflow (logics/request -> logics/backlog -> logics/tasks) and keep companion product or architecture refs aligned: create new request/backlog/task docs, promote between stages, keep From version, Understanding, Confidence, and Progress indicators consistent, and generate correctly-numbered filenames. Use when a user asks to triage an idea, write a request, promote it to a backlog item, or create an executable task plan.
Bootstrap the Logics directory structure in a new repository (create `logics/architecture`, `logics/product`, `logics/request`, `logics/backlog`, `logics/tasks`, `logics/specs`, `logics/external`) and add `.gitkeep` files for empty folders so the structure stays versioned. Use when setting up Logics in a fresh project or validating that required directories exist.
Generate Logics workflow Mermaid blocks with a deterministic fallback that stays compatible with the flow manager.
Generate a consolidated index of Logics documents. Use when Codex should build or refresh `logics/INDEX.md` summarizing requests, backlog items, and tasks with titles and progress.