From ab0195d4f8842cce3d3dd4d5f538b07ce42fa72f Mon Sep 17 00:00:00 2001 From: "aicia[bot]" Date: Tue, 30 Jun 2026 22:21:20 +0200 Subject: [PATCH 1/5] =?UTF-8?q?=E2=99=BB=EF=B8=8F=20restructure=20step=204?= =?UTF-8?q?:=20manifest=20diff=20before=20commit=20bodies?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Separate manifest-diff reading (4a–4b) from commit-body reading (4c) to ensure the skill captures the full cumulative dependency picture when multiple commits touched version files. Add test case 13 to validate this behavior handles multi-commit manifest updates correctly. --- skills/git-keep-a-changelog/SKILL.md | 49 +++++++++++++++----- skills/git-keep-a-changelog/evals/evals.json | 12 +++++ 2 files changed, 50 insertions(+), 11 deletions(-) diff --git a/skills/git-keep-a-changelog/SKILL.md b/skills/git-keep-a-changelog/SKILL.md index bfb0b65..c6071cf 100644 --- a/skills/git-keep-a-changelog/SKILL.md +++ b/skills/git-keep-a-changelog/SKILL.md @@ -182,24 +182,50 @@ git ls-files --others --exclude-standard ### Step 4: Read the full history and net effect -Read enough git history to understand what the release actually changed. +Follow these sub-steps in order. Sub-steps 4a and 4b are mandatory whenever manifests were touched and must run before reading commit bodies. -- Read the full commit message bodies, not just `--oneline`. -- Inspect the net diff so fixups and partial reversals do not distort the changelog. -- When dependency or version manifests changed anywhere in the selected range, diff those manifests from the resolved base to `HEAD` so you capture the full cumulative update set, not just whichever commit last touched the file. -- Treat manifest files such as `Directory.Packages.props`, `package.json`, lockfiles, `pom.xml`, `go.mod`, or similar version baselines as range-level evidence. If several commits touched them, use the base-to-`HEAD` diff to understand every package/version change that survived into the release. -- When the user approved pending changes, inspect the selected staged, unstaged, and/or untracked worktree deltas too. -- Prefer the final user-visible or maintainer-meaningful outcome over the implementation path. +**4a — Detect manifest changes.** Before reading any commit messages, check which files changed in the range: -Helpful commands: +```bash +git diff --name-only ..HEAD +``` + +If any dependency or version manifest appears in the output — `Directory.Packages.props`, `Directory.Build.props`, `package.json`, `pnpm-lock.yaml`, `yarn.lock`, `pom.xml`, `build.gradle`, `go.mod`, `go.sum`, or similar — proceed to 4b immediately. Do not skip ahead to reading commit bodies. + +**4b — Diff each touched manifest base-to-HEAD (mandatory).** For every manifest found in 4a, run a full range-level diff: + +```bash +git diff ..HEAD -- Directory.Packages.props +git diff ..HEAD -- package.json +git diff ..HEAD -- go.mod +# Repeat for every manifest file identified in 4a +``` + +Parse the cumulative delta: which packages were added, removed, upgraded, or downgraded, and what the exact before → after versions are across the full selected range. This is the **authoritative source of truth** for dependency changes. Individual commit messages may describe partial steps because multiple commits touched the same file; the manifest diff captures the net outcome that survived into the release. + +When an individual commit says "upgrade X from A → B" but the manifest diff shows X ended at C (because a later commit in the same range bumped it again), the manifest diff result is authoritative. Use C in the changelog, not B. + +**4c — Read the full commit log.** After completing 4a–4b, read individual commit bodies for context and non-manifest changes: ```bash git log --reverse --format=medium git log --reverse --stat --format=medium +``` + +Use commit bodies to understand *why* packages were updated, what behavioral changes were made, and whether any migration guidance is warranted. Treat commit messages as supporting context; do not let them override the version facts established in 4b. + +**4d — Inspect the net diff for non-manifest changes.** + +```bash git diff --stat ..HEAD git diff ..HEAD -git diff ..HEAD -- Directory.Packages.props -git diff ..HEAD -- package.json +``` + +Verify that fixups and partial reversals do not distort the changelog. Prefer the final user-visible or maintainer-meaningful outcome over the implementation path. + +**4e — Include approved pending changes.** When the user approved pending changes in Step 3, also inspect the selected worktree deltas: + +```bash git diff --cached git diff git ls-files --others --exclude-standard @@ -250,7 +276,7 @@ After updating `CHANGELOG.md`, stop and let the user review the file. Do not com - Includes a required SemVer-aware release highlight. - Creates a compliant `CHANGELOG.md` scaffold when the file is missing. - Reflects the meaning of full commit bodies and the net diff. -- Uses base-to-`HEAD` manifest diffs to preserve the cumulative dependency/version picture when release-range commits touched version baselines multiple times. +- Runs base-to-`HEAD` manifest diffs as the first evidence step (4a–4b) whenever any manifest was touched, capturing the full cumulative dependency/version picture before reading individual commit messages. - Treats the selected branch or range as author-agnostic scope and includes every contributor's commits unless the user explicitly narrows by author. - Treats Step 3 as a mandatory confirmation gate for concrete releases and asks the `Yes / No / Custom` question before including pending worktree changes (or skips Step 3 entirely and includes all changes when yolo/auto mode is active). - Maintains or inserts the compare-link footer at the bottom of the file on both create and update paths. @@ -272,3 +298,4 @@ After updating `CHANGELOG.md`, stop and let the user review the file. Do not com - Claiming breaking changes, fixes, or security work not supported by git. - Filtering the selected branch or range to the current user's or current contributor's commits, or treating "my changes" as the default release scope. - Understating dependency or version changes because the skill only read individual commit diffs and never inspected the surviving manifest delta from base to `HEAD`. +- Reading commit messages before running manifest diffs, then reporting only the packages mentioned in whichever commits happened to be read first, rather than the full cumulative set from the manifest diff. diff --git a/skills/git-keep-a-changelog/evals/evals.json b/skills/git-keep-a-changelog/evals/evals.json index b0ad8ec..2d759b9 100644 --- a/skills/git-keep-a-changelog/evals/evals.json +++ b/skills/git-keep-a-changelog/evals/evals.json @@ -140,6 +140,18 @@ "Does not understate dependency updates simply because they were spread across multiple commits", "Keeps the changelog grounded in the net manifest delta that reached HEAD" ] + }, + { + "id": 13, + "prompt": "Update CHANGELOG.md for this release. Directory.Packages.props was changed in two separate commits across the range: the first upgraded three packages and the second upgraded a fourth. Make sure all four package upgrades appear in the changelog.", + "expected_output": "The changelog lists all four package upgrades in the Changed section, derived from a base-to-HEAD manifest diff rather than from individual commit messages alone.", + "expectations": [ + "Runs a base-to-HEAD diff of Directory.Packages.props before reading individual commit bodies", + "Treats the manifest diff as the authoritative source of truth for all package version changes in the range", + "Captures package upgrades from both commits even when the same manifest file was touched multiple times", + "Does not underreport package updates because they were spread across separate commits", + "Does not let commit-message version descriptions override manifest diff version facts when the two differ" + ] } ] } From b147a934905c2a2691d2dca81eb9f4feb8f688a1 Mon Sep 17 00:00:00 2001 From: "aicia[bot]" Date: Tue, 30 Jun 2026 22:47:02 +0200 Subject: [PATCH 2/5] =?UTF-8?q?=E2=9C=A8=20update=20git-keep-a-changelog?= =?UTF-8?q?=20skill=20description=20for=20clarity?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 1689917..a9d5242 100644 --- a/README.md +++ b/README.md @@ -102,7 +102,7 @@ npx skills add https://github.com/codebeltnet/agentic --skill dotnet-docfx-diges | Skill | Description | |-------|-------------| | [git-visual-commits](skills/git-visual-commits/SKILL.md) | AI-driven git commit workflow with emoji-first subjects (gitmoji-first), optional conventional prefixes only on explicit request, and three identity modes: bot-attributed (`git bot commit`), human-attributed (`git commit`), and collaborative (`git our commit` — agent analyzes authorship, human picks attribution). Includes commit body by default (opt out with `no-body`), semantic intent splitting, bundled `commit-language.md` validation from the skill resource path rather than repo-root guesses, clarification-before-correction safety, and auto-approval mode (`yolo` / `auto`). The agent does all the work either way. Stack-agnostic. | -| [git-keep-a-changelog](skills/git-keep-a-changelog/SKILL.md) | Git-aware Keep a Changelog companion that creates or updates `CHANGELOG.md` from the current branch by default. Reads full commit subjects and bodies plus the net diff, treats the selected branch or range as author-agnostic scope by default so all contributors are included unless explicitly narrowed, infers a release heading from a branch version hint like `v0.3.0/...` when available, must ask a mandatory `Yes / No / Custom` confirmation question before including pending staged, unstaged, or untracked worktree changes in a concrete release draft, now backed by `FORMS.md` so compatible hosts can render a native choice UI while preserving the same text fallback, creates a compliant changelog if the file does not exist yet, writes a required SemVer-aware release highlight, maintains or inserts the Keep a Changelog compare-link footer on both create and update paths, preserves natural prose wrapping, and curates `Added` / `Changed` / `Fixed` style sections instead of dumping raw commit logs. | +| [git-keep-a-changelog](skills/git-keep-a-changelog/SKILL.md) | Git-aware Keep a Changelog companion that creates or updates `CHANGELOG.md` from the current branch by default. Inspects dependency and version manifests first (mandatory 4a–4b), then reads full commit subjects and bodies plus the net diff, treats the selected branch or range as author-agnostic scope by default so all contributors are included unless explicitly narrowed, infers a release heading from a branch version hint like `v0.3.0/...` when available, must ask a mandatory `Yes / No / Custom` confirmation question before including pending staged, unstaged, or untracked worktree changes in a concrete release draft, now backed by `FORMS.md` so compatible hosts can render a native choice UI while preserving the same text fallback, creates a compliant changelog if the file does not exist yet, writes a required SemVer-aware release highlight, maintains or inserts the Keep a Changelog compare-link footer on both create and update paths, preserves natural prose wrapping, and curates `Added` / `Changed` / `Fixed` style sections instead of dumping raw commit logs. | | [git-nuget-release-notes](skills/git-nuget-release-notes/SKILL.md) | Git-aware NuGet release-notes companion for .NET repos that keep cumulative `.nuget/{ProjectName}/PackageReleaseNotes.txt` files. Discovers packable `src/` projects, resolves concrete package version and availability, creates missing files when needed, and writes per-package `ALM` / `Breaking Changes` / `New Features` / `Improvements` / `Bug Fixes` style notes from full commit context plus the net diff instead of dumping commit subjects. | | [git-nuget-readme](skills/git-nuget-readme/SKILL.md) | Git-aware NuGet README companion for .NET repos that advertise a package from `src/`. Resolves the real packable project the README should sell, combines git history with actual package metadata, source capabilities, and relevant tests when feasible, preserves honest badge/docs/contributing sections, and writes a forthcoming, adoption-friendly `README.md` with repo-derived branding, clear value, install, framework-support, and quick-start guidance. | | [git-visual-squash-summary](skills/git-visual-squash-summary/SKILL.md) | Non-mutating grouped-summary companion to `git-visual-commits`. Turns the full current feature branch into a curated set of compact lowercase-start summary lines for PR or squash-and-merge contexts by default, comparing against the repository base branch rather than a same-named tracking remote, including commits from all authors unless explicitly narrowed, preserving technical identifiers, merging overlap, dropping low-signal noise, retaining dependency and version-pin changes as hard-rule semantic groups before net-effect collapsing, highlighting distinct meaningful efforts, and avoiding changelog-style wording, unsupported claims, yolo prompts, needless commit-range questions, or commit-selection UI for ordinary branch-level squash requests. | From 53c7013c35e7b7a29b2de0ec20b226e881312da5 Mon Sep 17 00:00:00 2001 From: "aicia[bot]" Date: Tue, 30 Jun 2026 23:34:38 +0200 Subject: [PATCH 3/5] =?UTF-8?q?=F0=9F=93=9D=20enhance=20git-keep-a-changel?= =?UTF-8?q?og=20base-commit=20handling?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Add a mandatory Step 4a for concrete releases to inspect the base commit before reading manifests. The base commit often contains release-prep changes and version bumps that are foundational to the release narrative. Update all subsequent steps (4a→4b, 4b→4c, etc.) and clarify when to use ^..HEAD for concrete releases versus ..HEAD for unreleased changelogs. Add quality-gate reminder to never omit the base commit from concrete release changelogs. --- skills/git-keep-a-changelog/SKILL.md | 58 +++++++++++++++++++++------- 1 file changed, 45 insertions(+), 13 deletions(-) diff --git a/skills/git-keep-a-changelog/SKILL.md b/skills/git-keep-a-changelog/SKILL.md index c6071cf..1df18b3 100644 --- a/skills/git-keep-a-changelog/SKILL.md +++ b/skills/git-keep-a-changelog/SKILL.md @@ -182,48 +182,78 @@ git ls-files --others --exclude-standard ### Step 4: Read the full history and net effect -Follow these sub-steps in order. Sub-steps 4a and 4b are mandatory whenever manifests were touched and must run before reading commit bodies. +Follow these sub-steps in order. Sub-steps 4b and 4c are mandatory whenever manifests were touched and must run before reading commit bodies. -**4a — Detect manifest changes.** Before reading any commit messages, check which files changed in the range: +**Range extension for concrete releases:** When the changelog target is a concrete version heading (e.g., `## [X.Y.Z]`), use `^..HEAD` throughout Step 4 to include the base commit itself. The base commit frequently contains the initial version bumps or release-prep changes that are part of the complete deliverable. For `## [Unreleased]`, continue using `..HEAD` — no change. + +**4a — Inspect the base commit (concrete releases only).** Before detecting manifest changes or reading commit bodies, inspect the base commit itself: ```bash +git show --format=medium +git diff ^.. --stat +``` + +This reveals what the branch author prepared as the foundation: release prep, version bumps, or initial dependency updates. If the base commit contains manifest changes, treat those as the starting point for the dependency picture established in 4b–4c. + +**4b — Detect manifest changes.** Check which files changed across the full range: + +```bash +# For concrete releases (## [X.Y.Z]): +git diff --name-only ^..HEAD + +# For [Unreleased]: git diff --name-only ..HEAD ``` -If any dependency or version manifest appears in the output — `Directory.Packages.props`, `Directory.Build.props`, `package.json`, `pnpm-lock.yaml`, `yarn.lock`, `pom.xml`, `build.gradle`, `go.mod`, `go.sum`, or similar — proceed to 4b immediately. Do not skip ahead to reading commit bodies. +If any dependency or version manifest appears in the output — `Directory.Packages.props`, `Directory.Build.props`, `package.json`, `pnpm-lock.yaml`, `yarn.lock`, `pom.xml`, `build.gradle`, `go.mod`, `go.sum`, or similar — proceed to 4c immediately. Do not skip ahead to reading commit bodies. -**4b — Diff each touched manifest base-to-HEAD (mandatory).** For every manifest found in 4a, run a full range-level diff: +**4c — Diff each touched manifest (mandatory).** For every manifest found in 4b, run the following diffs. For concrete releases, inspect the base commit's manifest changes first, then the full range: ```bash -git diff ..HEAD -- Directory.Packages.props -git diff ..HEAD -- package.json -git diff ..HEAD -- go.mod -# Repeat for every manifest file identified in 4a +# Base commit manifest changes first (concrete releases only): +git diff ^.. -- Directory.Packages.props +git diff ^.. -- package.json +# Repeat for every manifest identified in 4b + +# Full range diff: +git diff ^..HEAD -- Directory.Packages.props # concrete release +git diff ..HEAD -- Directory.Packages.props # [Unreleased] +# Repeat for every manifest identified in 4b ``` Parse the cumulative delta: which packages were added, removed, upgraded, or downgraded, and what the exact before → after versions are across the full selected range. This is the **authoritative source of truth** for dependency changes. Individual commit messages may describe partial steps because multiple commits touched the same file; the manifest diff captures the net outcome that survived into the release. When an individual commit says "upgrade X from A → B" but the manifest diff shows X ended at C (because a later commit in the same range bumped it again), the manifest diff result is authoritative. Use C in the changelog, not B. -**4c — Read the full commit log.** After completing 4a–4b, read individual commit bodies for context and non-manifest changes: +**4d — Read the full commit log.** After completing 4b–4c, read individual commit bodies for context and non-manifest changes. For concrete releases, include the base commit: ```bash +# For concrete releases (## [X.Y.Z]): +git log --reverse --format=medium ^..HEAD +git log --reverse --stat --format=medium ^..HEAD + +# For [Unreleased]: git log --reverse --format=medium git log --reverse --stat --format=medium ``` -Use commit bodies to understand *why* packages were updated, what behavioral changes were made, and whether any migration guidance is warranted. Treat commit messages as supporting context; do not let them override the version facts established in 4b. +Use commit bodies to understand *why* packages were updated, what behavioral changes were made, and whether any migration guidance is warranted. Treat commit messages as supporting context; do not let them override the version facts established in 4c. -**4d — Inspect the net diff for non-manifest changes.** +**4e — Inspect the net diff for non-manifest changes.** ```bash +# For concrete releases (## [X.Y.Z]): +git diff --stat ^..HEAD +git diff ^..HEAD + +# For [Unreleased]: git diff --stat ..HEAD git diff ..HEAD ``` Verify that fixups and partial reversals do not distort the changelog. Prefer the final user-visible or maintainer-meaningful outcome over the implementation path. -**4e — Include approved pending changes.** When the user approved pending changes in Step 3, also inspect the selected worktree deltas: +**4f — Include approved pending changes.** When the user approved pending changes in Step 3, also inspect the selected worktree deltas: ```bash git diff --cached @@ -276,7 +306,8 @@ After updating `CHANGELOG.md`, stop and let the user review the file. Do not com - Includes a required SemVer-aware release highlight. - Creates a compliant `CHANGELOG.md` scaffold when the file is missing. - Reflects the meaning of full commit bodies and the net diff. -- Runs base-to-`HEAD` manifest diffs as the first evidence step (4a–4b) whenever any manifest was touched, capturing the full cumulative dependency/version picture before reading individual commit messages. +- Inspects the base commit before anything else for concrete releases (4a), then runs base-to-`HEAD` manifest diffs as the first evidence steps (4b–4c) whenever any manifest was touched, capturing the full cumulative dependency/version picture before reading individual commit messages. +- Includes the base commit in concrete release changelogs by using `^..HEAD`, so foundational version bumps and release-prep changes are never omitted from the release narrative. - Treats the selected branch or range as author-agnostic scope and includes every contributor's commits unless the user explicitly narrows by author. - Treats Step 3 as a mandatory confirmation gate for concrete releases and asks the `Yes / No / Custom` question before including pending worktree changes (or skips Step 3 entirely and includes all changes when yolo/auto mode is active). - Maintains or inserts the compare-link footer at the bottom of the file on both create and update paths. @@ -299,3 +330,4 @@ After updating `CHANGELOG.md`, stop and let the user review the file. Do not com - Filtering the selected branch or range to the current user's or current contributor's commits, or treating "my changes" as the default release scope. - Understating dependency or version changes because the skill only read individual commit diffs and never inspected the surviving manifest delta from base to `HEAD`. - Reading commit messages before running manifest diffs, then reporting only the packages mentioned in whichever commits happened to be read first, rather than the full cumulative set from the manifest diff. +- Omitting the base commit from a concrete release changelog, causing the release narrative to miss foundational version bumps, release prep, or initial dependency updates that form part of the complete deliverable. From 29332aefe5bc168ddd2d625e0c364816c02d373e Mon Sep 17 00:00:00 2001 From: "aicia[bot]" Date: Wed, 1 Jul 2026 00:36:43 +0200 Subject: [PATCH 4/5] =?UTF-8?q?=F0=9F=94=A7=20fix=20manifest=20inspection?= =?UTF-8?q?=20steps=20in=20changelog=20skill=20documentation?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- skills/git-keep-a-changelog/SKILL.md | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/skills/git-keep-a-changelog/SKILL.md b/skills/git-keep-a-changelog/SKILL.md index 4f70699..5b6efe9 100644 --- a/skills/git-keep-a-changelog/SKILL.md +++ b/skills/git-keep-a-changelog/SKILL.md @@ -188,15 +188,13 @@ Follow these sub-steps in order. Sub-steps 4b and 4c are mandatory whenever mani **4a — Inspect the base commit (concrete releases only).** Before detecting manifest changes or reading commit bodies, inspect the base commit itself: -If any dependency or version manifest appears in the output — `Directory.Packages.props`, `Directory.Build.props`, `package.json`, `pnpm-lock.yaml`, `yarn.lock`, `pom.xml`, `build.gradle`, `go.mod`, `go.sum`, or similar — proceed to 4b immediately. Do not skip ahead to reading commit bodies. - -**4b — Diff each touched manifest base-to-HEAD (mandatory).** For every manifest found in 4a, run a full range-level diff: - ```bash git show --format=medium git diff ^.. --stat ``` +If any dependency or version manifest appears in the output — `Directory.Packages.props`, `Directory.Build.props`, `package.json`, `pnpm-lock.yaml`, `yarn.lock`, `pom.xml`, `build.gradle`, `go.mod`, `go.sum`, or similar — proceed to 4b immediately. Do not skip ahead to reading commit bodies. + This reveals what the branch author prepared as the foundation: release prep, version bumps, or initial dependency updates. If the base commit contains manifest changes, treat those as the starting point for the dependency picture established in 4b–4c. **4b — Detect manifest changes.** Check which files changed across the full range: @@ -237,7 +235,6 @@ git log --reverse --format=medium ^..HEAD git log --reverse --stat --format=medium ^..HEAD # For [Unreleased]: -``` git log --reverse --format=medium git log --reverse --stat --format=medium ``` @@ -252,7 +249,6 @@ git diff --stat ^..HEAD git diff ^..HEAD # For [Unreleased]: -``` git diff --stat ..HEAD git diff ..HEAD ``` From 6b4434b0b188ef015b293be1bfc89a7d5e26994a Mon Sep 17 00:00:00 2001 From: "aicia[bot]" Date: Wed, 1 Jul 2026 00:39:54 +0200 Subject: [PATCH 5/5] =?UTF-8?q?=F0=9F=93=9D=20update=20changelog=20for=20v?= =?UTF-8?q?0.7.3=20with=20skill=20and=20documentation=20improvements?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- CHANGELOG.md | 25 ++++++++++++++++++++++++- 1 file changed, 24 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 76443b3..2d0e573 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -6,6 +6,28 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), ## [Unreleased] +## [0.7.3] - 2026-07-01 + +This is a patch release focused on skill refinement and documentation improvements, including xref member-link validation enhancements to dotnet-docfx-digest, structural improvements to git-keep-a-changelog's manifest-diff reading, and emoji discipline improvements across git-visual skills. + +### Added + +- xref member link validator to docfx diagnostic engine for precise cross-assembly reference validation, +- Expanded test coverage in docfx-digest `test-quality.ps1` for xref member-link scenarios. + +### Changed + +- git-keep-a-changelog: restructured Step 4 to read manifest diffs before commit bodies, ensuring the full cumulative dependency picture when multiple commits touched version files, +- git-keep-a-changelog: added mandatory Step 4a for concrete releases to inspect the base commit before reading manifests, capturing foundational release-prep changes and version bumps, +- dotnet-docfx-digest: enhanced SKILL.md documentation to cover xref member link validation rules for interface and abstract types, +- git-visual-commits and git-visual-squash-summary: improved emoji discipline and alignment across commit-language references, +- README: updated skill inventory and capability summaries to reflect enhanced xref validation and changelog-automation improvements. + +### Fixed + +- xref member-link false positives for interface and abstract types in docfx diagnostic engine, +- manifest inspection steps documentation in git-keep-a-changelog to reflect new Step 4a–4b–4c sequencing for concrete releases. + ## [0.7.2] - 2026-06-29 This is a minor release that further refines adaptive execution profiles, enhances heartbeat suppression options, strengthens parallel skill validation support, and expands evaluation coverage for git-visual-squash-summary. @@ -396,7 +418,8 @@ This is a minor release that introduces two complementary git workflow skills, e - Improved scaffold fidelity with hidden `.bot` asset preservation, explicit UTF-8 and BOM handling, and checks aimed at preventing mojibake or incomplete generated output. -[Unreleased]: https://github.com/codebeltnet/agentic/compare/v0.7.2...HEAD +[Unreleased]: https://github.com/codebeltnet/agentic/compare/v0.7.3...HEAD +[0.7.3]: https://github.com/codebeltnet/agentic/compare/v0.7.2...v0.7.3 [0.7.2]: https://github.com/codebeltnet/agentic/compare/v0.7.1...v0.7.2 [0.7.1]: https://github.com/codebeltnet/agentic/compare/v0.7.0...v0.7.1 [0.7.0]: https://github.com/codebeltnet/agentic/compare/v0.6.0...v0.7.0