{"slug": "a-command-file-for-use-with-ai-coding-harness-to-automate-creation-of-structured", "title": "A command file for use with AI coding harness, to automate creation of structured changelog entries.", "summary": "A developer created a Kilo CLI command called 'release-note' that automates the generation of structured changelog entries from staged and unstaged Git changes. The tool scans modified files, prompts for version number and descriptions, and appends formatted entries to RELEASE_NOTE.md under the # CHANGELOG header, ensuring consistent documentation.", "body_md": "| --- | |\n| description: Append release notes to RELEASE_NOTE.md from staged/unstaged changes | |\n| release-note is a custom Kilo CLI command that automates the creation of structured changelog entries. | |\n| It scans the working directory for staged and unstaged changes (git diff --name-only HEAD), presents a summary of modified files, | |\n| then interactively prompts for a version number, a descriptive heading, and one-line summaries for each change group. | |\n| It maps each change to the relevant files and appends the entry — version, heading, numbered descriptions, | |\n| and file paths — directly under the # CHANGELOG header in RELEASE_NOTE.md, with the newest entry always at the top. | |\n| This ensures every release is consistently documented without manual formatting. | |\n| sample usage : /release-note | |\n| --- | |\n| First, get the list of changed files: | |\n| Run: `git diff --name-only HEAD` (for unstaged + staged). Also run `git status --short` for context. | |\n| Present the user with a summary of what files have changed, then ask: | |\n| 1. Version number (e.g. v1.1.2) | |\n| 2. Brief heading describing the change group (e.g. \"Booking - Bug Fix\") | |\n| 3. For each distinct change, ask: | |\n| - A one-line description of what was done | |\n| - Which of the changed files are relevant (the user can say \"all\" or pick specific files) | |\n| Then append to RELEASE_NOTE.md directly under `# CHANGELOG` using this format: | |\n| ``` | |\n| ## {version} | |\n| ### {heading} | |\n| 1) {description} | |\n| - Files affected: | |\n| - {file path} | |\n| - {file path} | |\n| ``` | |\n| Important: | |\n| - Use forward slashes in file paths | |\n| - Keep descriptions concise | |\n| - Group related changes under the same heading | |\n| - Only ask user for version/description — don't guess | |\n| - Append after the `# CHANGELOG` line (i.e. as the newest entry at top) |", "url": "https://wpnews.pro/news/a-command-file-for-use-with-ai-coding-harness-to-automate-creation-of-structured", "canonical_source": "https://gist.github.com/muhadmr/3fe1431076d9946f4183b82887763c9b", "published_at": "2026-07-08 01:50:38+00:00", "updated_at": "2026-07-08 01:57:58.624610+00:00", "lang": "en", "topics": ["developer-tools"], "entities": ["Kilo CLI", "Git", "RELEASE_NOTE.md"], "alternates": {"html": "https://wpnews.pro/news/a-command-file-for-use-with-ai-coding-harness-to-automate-creation-of-structured", "markdown": "https://wpnews.pro/news/a-command-file-for-use-with-ai-coding-harness-to-automate-creation-of-structured.md", "text": "https://wpnews.pro/news/a-command-file-for-use-with-ai-coding-harness-to-automate-creation-of-structured.txt", "jsonld": "https://wpnews.pro/news/a-command-file-for-use-with-ai-coding-harness-to-automate-creation-of-structured.jsonld"}}