V0.3.0/new complementary skills

.github/workflows/validate-skill-templates.yml

@@ -0,0 +1,16 @@
+name: Validate Skill Templates
+
+on:
+  pull_request:
+
+jobs:
+  validate-skill-templates:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Run validator
+        shell: pwsh
+        run: pwsh -NoProfile -File ./scripts/validate-skill-templates.ps1

CHANGELOG.md

@@ -0,0 +1,68 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+## [0.3.0] - 2026-03-17
+
+This is a minor release that introduces two complementary git workflow skills, extracts a shared commit-language reference, and backs the whole skill suite with pull-request validation plus stricter skill metadata checks.
+
+### Added
+
+- `git-visual-squash-summary` skill that turns a noisy commit stack into grouped summary lines — preserving distinct high-signal efforts, merging overlapping commits, and dropping low-signal noise — without mutating git state,
+- `git-keep-a-changelog` skill that creates or updates `CHANGELOG.md` directly from the current branch, reads full commit message bodies for context, infers release headings from branch version hints, and writes a required SemVer-aware release highlight with natural prose,
+- GitHub Actions workflow that runs `validate-skill-templates.ps1` on pull requests as the merge safety net,
+- Per-skill `evals/evals.json` coverage for `git-visual-squash-summary` and `git-keep-a-changelog`.
+
+### Changed
+
+- Extracted the shared commit-language guidance into `references/commit-language.md`, used by both `git-visual-commits` and `git-visual-squash-summary`, so prefix, emoji, and wording rules have one maintained source,
+- Tightened git skill metadata so frontmatter descriptions stay within the repo limit and `git-visual-commits` points directly at `references/commit-language.md` instead of stale in-file “below” references,
+- Tightened `git-visual-commits` grouping rules to classify new repo capabilities, existing-skill refactors, and shared-reference sync as separate intents, with eval coverage for mixed-diff cases,
+- Hardened `validate-skill-templates.ps1` with UTF-8 and BOM handling, grouped squash summary rule checks, changelog formatting enforcement, repo-wide frontmatter description-length enforcement, and consistent behavior across Windows PowerShell and CI,
+- Updated `CONTRIBUTING.md` to explain the local-first validation workflow: run the script locally for fast feedback while GitHub Actions reruns the same checks as the safety net.
+
+## [0.2.0] - 2026-03-16
+
+### Added
+
+- Added per-skill `evals/evals.json` coverage across the repo, including deterministic validation for scaffold behavior and skill contracts.
+- Expanded `dotnet-new-app-slnx` with explicit web-family variants for Empty Web, Web API, MVC, and Web App / Razor scaffolds.
+- Introduced a NuGet-backed app package resolver so generated `Directory.Packages.props` files use current compatible versions.
+
+### Changed
+
+- Hardened the .NET app and library scaffold skills around required outputs, current-folder generation, supported TFM choices, and clearer usage guidance.
+- Tightened repo documentation and local skill-sync guidance so README, policy, and install expectations stay aligned.
+- Strengthened `git-visual-commits` with identity lock, `yolo` guardrails, post-commit verification, and clearer umbrella-commit rejection rules.
+
+### Fixed
+
+- Improved scaffold fidelity so generated assets stay complete, shared files remain synchronized, and emitted app templates are validation- and compile-ready.
+
+## [0.1.0] - 2026-03-15
+
+### Added
+
+- Launched the initial skill suite with `git-visual-commits`, `trunk-first-repo`, `dotnet-strong-name-signing`, `dotnet-new-lib-slnx`, and `dotnet-new-app-slnx`.
+- Added repo governance and contributor guidance, including the initial `README`, `CONTRIBUTING`, `AGENTS.md`, license, and ignore rules.
+- Added shared scaffold assets for CI, packaging, documentation, benchmarking, and TFM-aware test environments for the .NET skills.
+
+### Changed
+
+- Split the original combined .NET scaffolder into dedicated app and library skills with clearer scope boundaries and lower-friction prompts.
+- Refined scaffold defaults to derive more metadata from repo state, official .NET support data, and current package feeds instead of stale hardcoded values.
+- Evolved `git-visual-commits` from a basic commit helper into an opinionated workflow with reviewable commit plans, collaborative attribution modes, richer gitmoji coverage, and body-by-default support.
+
+### Fixed
+
+- 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.3.0...HEAD
+[0.3.0]: https://github.com/codebeltnet/agentic/compare/v0.2.0...v0.3.0
+[0.2.0]: https://github.com/codebeltnet/agentic/compare/v0.1.0...v0.2.0
+[0.1.0]: https://github.com/codebeltnet/agentic/compare/7eaf364...v0.1.0

CONTRIBUTING.md

@@ -106,6 +106,10 @@ Use the repo validation harness before submitting scaffold or template changes:
 powershell -NoProfile -ExecutionPolicy Bypass -File .\scripts\validate-skill-templates.ps1
 ```
 
+Run the validator locally first for the fastest feedback loop. GitHub
+Actions also runs the same script on pull requests, but CI is
+the backstop, not the primary authoring loop.
+
 To compare a change against the initial imported version, run the same harness against a git ref:
 
 ```powershell
@@ -120,6 +124,7 @@ powershell -NoProfile -ExecutionPolicy Bypass -File .\scripts\validate-skill-tem
 - [ ] At least one eval in `evals/evals.json`
 - [ ] The skill's `evals/evals.json` exists and its `skill_name` matches the folder/frontmatter name
 - [ ] `scripts/validate-skill-templates.ps1` passes for the current working tree when changing scaffold or template behavior
+- [ ] If CI is enabled for the branch, the GitHub Actions validation job passes too
 - [ ] Skill evals are intended to run from `$env:TEMP/<skill-name>-workspace/`, not from inside the repo
 - [ ] Changed skill files are synced across `skills/<name>/`, `~/.claude/skills/<name>/`, and `~/.agents/skills/<name>/`
 - [ ] Skill added to the table in `README.md`

README.md

@@ -13,6 +13,12 @@ Another repo rule is intentionally strict: every repo-managed skill ships with i
 There is also an interim Codex compatibility workaround in [AGENTS.md](AGENTS.md): the repo mirrors the current `~/.codex/AGENTS.override.md` decision and code-change rules so they still apply even when a Codex build fails to auto-load that personal override file.
 
 One more consistency rule matters for form-driven skills: native input fields are treated as a host feature, not something a model can rely on. Skills in this repo must stay usable with or without UI widgets, and must fall back to the same deterministic one-field-at-a-time flow when the host only supports plain chat.
+
+Validation follows the same philosophy: run
+`scripts/validate-skill-templates.ps1` locally for the fast feedback
+loop, and let GitHub Actions rerun that same script on pull requests as
+the safety net. That validator also checks skill frontmatter metadata
+such as the 1024-character YAML description limit.
 
 ## Install a skill
 
@@ -42,6 +48,8 @@ If you want a bundle of skills always available, just install them all:
 
 ```bash
 npx skills add https://github.com/codebeltnet/agentic --skill git-visual-commits
+npx skills add https://github.com/codebeltnet/agentic --skill git-keep-a-changelog
+npx skills add https://github.com/codebeltnet/agentic --skill git-visual-squash-summary
 npx skills add https://github.com/codebeltnet/agentic --skill trunk-first-repo
 npx skills add https://github.com/codebeltnet/agentic --skill dotnet-strong-name-signing
 # npx skills add https://github.com/codebeltnet/agentic --skill another-skill
@@ -60,10 +68,12 @@ npx skills add https://github.com/codebeltnet/agentic --skill dotnet-strong-name
 
 ## Available Skills
 
-| Skill | Description |
-|-------|-------------|
-| [git-visual-commits](skills/git-visual-commits/SKILL.md) | AI-driven git commit workflow with emoji (gitmoji-first), conventional prefixes, 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, and auto-approval mode (`yolo` / `auto`). The agent does all the work either way. Stack-agnostic. |
-| [dotnet-new-lib-slnx](skills/dotnet-new-lib-slnx/SKILL.md) | Scaffold a new .NET NuGet library solution following codebeltnet engineering conventions. Dynamic defaults for TFM/repository metadata, latest-stable NuGet package resolution, tuning projects plus a tooling-based benchmark runner, TFM-aware test environments, strong-name signing, NuGet packaging, DocFX documentation, CI/CD pipeline, and code quality tooling. |
+| Skill | Description |
+|-------|-------------|
+| [git-visual-commits](skills/git-visual-commits/SKILL.md) | AI-driven git commit workflow with emoji (gitmoji-first), conventional prefixes, 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, 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, infers a release heading from a branch version hint like `v0.3.0/...` when available, creates a compliant changelog if the file does not exist yet, writes a required SemVer-aware release highlight, preserves natural prose wrapping, and curates `Added` / `Changed` / `Fixed` style sections instead of dumping raw commit logs. |
+| [git-visual-squash-summary](skills/git-visual-squash-summary/SKILL.md) | Non-mutating grouped-summary companion to `git-visual-commits`. Turns noisy commit stacks into a curated set of compact summary lines for PR or squash contexts, preserving technical identifiers, merging overlap, dropping low-signal noise, highlighting distinct meaningful efforts, and avoiding changelog-style wording or unsupported claims. |
+| [dotnet-new-lib-slnx](skills/dotnet-new-lib-slnx/SKILL.md) | Scaffold a new .NET NuGet library solution following codebeltnet engineering conventions. Dynamic defaults for TFM/repository metadata, latest-stable NuGet package resolution, tuning projects plus a tooling-based benchmark runner, TFM-aware test environments, strong-name signing, NuGet packaging, DocFX documentation, CI/CD pipeline, and code quality tooling. |
 | [dotnet-new-app-slnx](skills/dotnet-new-app-slnx/SKILL.md) | Scaffold a new .NET standalone application solution following codebeltnet engineering conventions. Supports Console, Web, and Worker host families with Startup or Minimal hosting patterns; Web expands into Empty Web, Web API, MVC, or Web App / Razor, plus functional tests and a simplified CI pipeline. |
 | [trunk-first-repo](skills/trunk-first-repo/SKILL.md) | Initialize a git repository following [scaled trunk-based development](https://trunkbaseddevelopment.com/#scaled-trunk-based-development). Seeds an empty `main` branch and creates a versioned feature branch (`v0.1.0/init`), enforcing a PR-first workflow where content only reaches main through peer-reviewed pull requests. |
 | [dotnet-strong-name-signing](skills/dotnet-strong-name-signing/SKILL.md) | Generate a strong name key (`.snk`) file for signing .NET assemblies using pure .NET cryptography — no Visual Studio Developer PowerShell or `sn.exe` required. Works in any terminal. Defaults to 1024-bit RSA (matching `sn.exe`), with 2048 and 4096 available as options. |
@@ -78,6 +88,18 @@ If your Markdown viewer supports code-block copy buttons, each command below sho
 npx skills add https://github.com/codebeltnet/agentic --skill git-visual-commits
 ```
 
+`git-keep-a-changelog`
+
+```bash
+npx skills add https://github.com/codebeltnet/agentic --skill git-keep-a-changelog
+```
+
+`git-visual-squash-summary`
+
+```bash
+npx skills add https://github.com/codebeltnet/agentic --skill git-visual-squash-summary
+```
+
 `dotnet-new-lib-slnx`
 
 ```bash
@@ -117,12 +139,50 @@ Commit messages are the most-read documentation in any codebase — yet they're
 - **Commit body by default** — every commit explains *why*, not just *what* — opt out with "tmi" or "no-body"
 - **Commit bodies are verified after write** — the workflow now checks the stored commit body so literal escape sequences like `\n` do not leak into history
 - **Short bodies stay readable** — the workflow no longer hard-wraps short commit bodies at 72 characters and instead prefers normal prose with sentence-level judgment
+- **Repo capability additions stay explicit** — adding a brand-new skill is grouped separately from refactoring an existing skill to support it
+- **Shared wording rules stay in lockstep** — the duplicated `commit-language.md` reference is kept byte-for-byte identical across both git-visual skills and checked locally plus in CI
 - **Semantic intent splitting** — groups commits by rationale, not just file type — config and test logic are always separate
 - **Umbrella commits are rejected** — mixed diffs spanning skill instructions, templates, validators, and repo docs must be split into separate commits instead of bundled into one blob
 - **Stack-agnostic** — works with any language, framework, or project type
-- **Squash-and-merge friendly** — structured commits make PR squash summaries read like a changelog
-
-### Why dotnet-new-lib-slnx and dotnet-new-app-slnx?
+- **Squash-and-merge friendly** — structured commits make PR squash summaries read like a changelog
+
+### Why git-visual-squash-summary?
+
+Sometimes the history is already written and the only thing you need is
+the final grouped summary. A long branch with fixups, rename follow-ups,
+review nits, and repeated attempts often contains a few real change
+themes buried inside a messy chronological story. That is where
+**git-visual-squash-summary** fits: it reads the real history and diff,
+then compresses them into a small set of truthful grouped lines.
+
+- **Same visual language** — reuses the same prefix and emoji rules as `git-visual-commits`
+- **Grouped-lines only** — returns compact grouped lines only, not a title or body
+- **Non-mutating by design** — drafts the wording only and does not touch git state
+- **Distinct efforts stay distinct** — preserves meaningful change groups instead of forcing one umbrella line
+- **Intent over chronology** — collapses noisy commit stacks into the retained grouped effort
+- **Low-signal noise gets dropped** — typo-only and trivial fixup churn do not deserve their own lines
+- **Identifier-safe wording** — preserves technical names, paths, flags, and types where possible
+- **Readable in GitHub and terminals** — optimized for compact PR and squash-summary views
+- **Strict 72-char lines** — every summary line stays compact and scannable
+- **Not a changelog** — avoids release-note phrasing and commit-subject dumps
+- **No unsupported claims** — summarizes only what the inspected diff can justify
+
+### Why git-keep-a-changelog?
+
+Writing `CHANGELOG.md` well is harder than it looks. Raw commit subjects are too noisy, PR titles often miss migration context, and release notes get much better when the writer actually reads the commit bodies and understands the net diff. That is where **git-keep-a-changelog** fits: it turns the current branch into a curated Keep a Changelog entry and creates or updates the file directly for review.
+
+- **Keep a Changelog first** — writes `Added`, `Changed`, `Deprecated`, `Removed`, `Fixed`, and `Security` sections in the expected style
+- **Full-commit context** — reads complete commit messages and the net diff before writing
+- **Version-aware by branch** — uses a branch prefix like `v0.3.0/...` as the release heading hint when present
+- **SemVer-aware highlight** — always writes a short release TL;DR that explicitly says `major`, `minor`, or `patch`
+- **Creates the file when needed** — seeds a compliant `CHANGELOG.md` if the repo does not have one yet
+- **Natural prose** — preserves human-readable line breaks without any fixed-width wrapping target
+- **Predictable bullet punctuation** — bullets end with `,` and the last bullet in each section ends with `.`
+- **Direct file edit** — creates or updates `CHANGELOG.md` directly, then stops for human review
+- **Compare-link aware** — can update bottom-of-file compare links when a concrete release heading is added
+- **Not a commit dump** — curates the release story instead of copying git log output into Markdown
+
+### Why dotnet-new-lib-slnx and dotnet-new-app-slnx?
 
 Starting a new .NET solution "from scratch" usually means copying from your last project, deleting half of it, and spending an hour wiring up CI, MSBuild props, versioning, and code quality tooling. Every new repo drifts slightly from the last one. Six months later, no two solutions look the same.