Conversation
Move the shared prefix and emoji guidance for git-visual-commits into a dedicated reference so the existing commit workflow keeps one maintained wording source.
Introduce a new squash-summary skill that turns noisy commit stacks into one GitHub-friendly subject line without mutating git state.
Extend the repo validator so the shared commit-language references stay in sync and the new squash-summary skill contract is enforced.
Document the new squash-summary skill in the README and capture the v0.1.0 and v0.2.0 release history in a Keep a Changelog-formatted changelog.
Clarify that new repo capabilities, existing-skill refactors, and shared reference sync guidance are separate intents. Add eval coverage so mixed capability and refactor diffs do not collapse into one commit.
Run the existing validator on every push and pull request, and harden UTF-8 handling so the same checks behave consistently in Windows PowerShell and CI.
Explain that contributors should run validate-skill-templates.ps1 locally for fast feedback while GitHub Actions reruns the same checks as the merge safety net.
Replace the subject-only squash contract with grouped summary lines that preserve distinct high-signal efforts, merge overlap, and drop low-signal noise.
Update squash summary checks so the validator expects grouped lines, distinct effort preservation, and the new anti-stitching wording instead of a single subject line.
Refresh the README so git-visual-squash-summary is presented as a grouped-summary companion that keeps distinct efforts visible instead of collapsing everything into one subject.
Add a git-aware Keep a Changelog skill that creates or updates CHANGELOG.md from the current branch by default, reads full commit bodies for context, infers release headings from branch version hints, and writes a required SemVer-aware release highlight with natural prose.
Add deterministic checks for the changelog skill so the repo enforces full-commit context, branch-version hints, SemVer-aware highlights, natural prose, and missing-file creation behavior.
Add install and discovery docs for git-keep-a-changelog, including its create-or-update behavior, SemVer-aware release highlights, and Keep a Changelog focus.
Remove fixed-width wrapping guidance from git-keep-a-changelog and require section bullets to end with commas, with the final bullet in each section ending with a period.
Update the changelog skill checks to expect natural prose without any fixed-width wrapping target and to enforce the section-bullet comma/period punctuation pattern.
Refresh the git-keep-a-changelog docs so they promise natural prose without fixed-width wrapping and the required bullet punctuation pattern.
Reflow existing changelog entries into natural prose so the release notes read cleanly in Markdown without narrow manual line wrapping.
Capture the 0.3.0 release in CHANGELOG.md with a SemVer-aware release highlight, curated Added and Changed sections, and updated compare links for the new version.
Review Summary by QodoAdd git-visual-squash-summary and git-keep-a-changelog skills with CI-backed validation
WalkthroughsDescription• Added two new complementary git workflow skills: git-visual-squash-summary for non-mutating grouped summaries and git-keep-a-changelog for changelog generation from branch context • Extracted shared commit-language guidance into references/commit-language.md for consistent prefix, emoji, and wording rules across git-visual skills • Implemented GitHub Actions CI workflow to enforce skill template integrity on every push and pull request • Hardened validation script with UTF-8/BOM handling, grouped squash summary checks, and changelog formatting enforcement • Tightened git-visual-commits grouping rules to classify new repo capabilities, existing-skill refactors, and shared-reference sync as separate intents with eval coverage • Updated documentation in README and CONTRIBUTING to explain local-first validation workflow and new skill descriptions Diagramflowchart LR
A["New Skills<br/>squash-summary<br/>keep-a-changelog"] --> B["Shared References<br/>commit-language.md"]
B --> C["Git Visual<br/>Commits"]
A --> D["Validation<br/>Hardening"]
D --> E["GitHub Actions<br/>CI Workflow"]
E --> F["Consistent<br/>Enforcement"]
C --> G["Tightened<br/>Grouping Rules"]
G --> F
File Changes1. scripts/validate-skill-templates.ps1
|
Code Review by Qodo
1. description: > in frontmatter
|
Limit the validation workflow to pull requests to avoid duplicate push and pull_request checks, and update the contributor docs to describe the PR-only safety net accurately.
There was a problem hiding this comment.
Pull request overview
Adds two new git-focused skills and reinforces repo-wide skill template integrity via shared references, expanded validation, and CI enforcement.
Changes:
- Introduces
git-visual-squash-summary(non-mutating grouped squash summary output) andgit-keep-a-changelog(Keep a Changelog–styleCHANGELOG.mdauthoring from git history). - Extracts/standardizes git-visual commit language guidance into per-skill
references/commit-language.mdand updatesgit-visual-commitsto reference it. - Hardens
scripts/validate-skill-templates.ps1(UTF-8 handling + new rule checks) and adds a GitHub Actions workflow to run it on push/PR; updates repo docs and adds a changelog entry.
Reviewed changes
Copilot reviewed 13 out of 13 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| skills/git-visual-squash-summary/references/commit-language.md | Adds commit-language reference (kept in lockstep with git-visual-commits). |
| skills/git-visual-squash-summary/evals/evals.json | Adds eval coverage for grouped squash summary behavior/constraints. |
| skills/git-visual-squash-summary/SKILL.md | Defines the new non-mutating grouped squash summary skill contract. |
| skills/git-visual-commits/references/commit-language.md | Adds shared commit-language reference for git-visual-commits. |
| skills/git-visual-commits/evals/evals.json | Adds an eval ensuring new-skill/validator/docs changes are bucketed by intent. |
| skills/git-visual-commits/SKILL.md | Replaces inline prefix/emoji tables with a reference file + expands intent-grouping guidance. |
| skills/git-keep-a-changelog/evals/evals.json | Adds eval coverage for changelog generation/updating behavior. |
| skills/git-keep-a-changelog/SKILL.md | Defines the new Keep a Changelog automation skill contract. |
| scripts/validate-skill-templates.ps1 | Adds UTF-8 no-BOM handling and validates new skills + shared reference sync. |
| README.md | Documents new skills, install commands, and validator/CI guidance. |
| CONTRIBUTING.md | Adds CI validation expectations and local-first workflow guidance. |
| CHANGELOG.md | Adds Keep a Changelog–style changelog with a new 0.3.0 entry and compare links. |
| .github/workflows/validate-skill-templates.yml | Adds CI job to run skill template validation on pushes/PRs. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 35ab38ee00
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| description: > | ||
| Turn many commits into a curated grouped squash summary that | ||
| stays compatible with the opinionated wording style of | ||
| git-visual-commits. Use this skill whenever the user asks to squash a | ||
| branch into a concise summary, write a squash-and-merge summary, |
There was a problem hiding this comment.
Keep frontmatter description within 1024-character limit
The new skill’s YAML description exceeds the repository’s required limit from /workspace/agentic/AGENTS.md (Anthropic Skill Authoring Reference: “description … max 1024 chars”): this block is currently 1041 characters, which can cause skill ingestion/trigger metadata validation to fail in tooling that enforces the schema. Please shorten this description by at least 17 characters while preserving the trigger phrases.
Useful? React with 👍 / 👎.
| --- | ||
| name: git-keep-a-changelog | ||
| description: > | ||
| Create or update CHANGELOG.md from git history using Keep a Changelog |
There was a problem hiding this comment.
1. description: > in frontmatter 📘 Rule violation ✓ Correctness
skills/git-keep-a-changelog/SKILL.md YAML frontmatter contains a > character via the folded-scalar indicator description: >, which is disallowed. This can cause frontmatter validation to fail under the angle-bracket prohibition rule.
Agent Prompt
## Issue description
The SKILL frontmatter uses `description: >`, which includes a literal `>` character inside the YAML frontmatter. This violates the rule that forbids any `<` or `>` characters anywhere in the frontmatter.
## Issue Context
The prohibition applies to any `<`/`>` characters inside the frontmatter block, including YAML scalar indicators like `>`.
## Fix Focus Areas
- skills/git-keep-a-changelog/SKILL.md[1-18]
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools
Trim git skill frontmatter descriptions to satisfy the repo metadata limit and replace stale "below" wording with direct references to references/commit-language.md.
Add a repo-wide check that normalizes folded YAML descriptions and fails when any skill frontmatter description exceeds the 1024-character limit.
Document the new frontmatter metadata validation in the README and fix v0.3.0 release notes so the changelog matches the current pull-request-only validation workflow.
Refine the 0.3.0 release notes so the summary and Changed section capture the metadata-limit fix, stale git-skill reference cleanup, and the repo-wide frontmatter validation rule.
This pull request introduces two new git workflow skills, strengthens validation and documentation, and adds CI enforcement for skill template integrity. The most important changes are the addition of the
git-visual-squash-summaryandgit-keep-a-changelogskills, extraction of shared commit-language guidance, and implementation of a GitHub Actions workflow for template validation. Documentation and validation scripts have also been updated to reflect these enhancements.New skills and shared references:
git-visual-squash-summaryskill for non-mutating grouped summary lines and thegit-keep-a-changelogskill for changelog generation from branch context. [1] [2] [3] [4] [5]references/commit-language.mdfor consistent prefix, emoji, and wording rules across git-visual skills.Continuous integration and validation:
.github/workflows/validate-skill-templates.yml) to runvalidate-skill-templates.ps1on every push and pull request, enforcing skill template integrity.scripts/validate-skill-templates.ps1) for UTF-8/BOM handling, improved rule checks, and consistent CI behavior. [1] [2] [3]Documentation updates:
README.mdandCONTRIBUTING.mdwith guidance on running validation locally and via CI, new skill descriptions, and changelog formatting enforcement. [1] [2] [3] [4] [5]Changelog and eval coverage:
CHANGELOG.mdto document all notable changes, including new skills, validation improvements, and eval coverage for the new skills.Skill grouping and intent classification:
git-visual-commitsto classify repo capability additions, refactors, and shared-reference sync as separate intents, with eval coverage for mixed-diff cases.