Generate changelog using git-cliff, optionally bump version tag
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Generate or update CHANGELOG.md using git-cliff based on conventional commits.
Action: $ARGUMENTS
If no action was specified, determine the workflow by asking the user.
Branch and status: !git status -sb
Recent commits: !git log --oneline -10
Latest tag: !git describe --tags --abbrev=0 2>/dev/null || echo "No tags yet"
Unpushed commits: !git log --oneline @{u}..HEAD 2>/dev/null || echo "No upstream or no unpushed commits"
Working directory: !git status --porcelain | head -5 || echo "Clean"
Unreleased changes preview: !git-cliff --unreleased 2>/dev/null | head -20 || echo "No unreleased changes or git-cliff not configured"
If uncommitted changes exist (other than CHANGELOG.md), warn the user and ask whether to continue or abort.
If no conventional commits since last tag, inform user and stop.
preview: Show unreleased changes with git-cliff --unreleased. Report summary and stop.
generate: Run git-cliff -o CHANGELOG.md, show diff with git diff CHANGELOG.md, commit with message docs: update changelog.
release:
git-cliff --bump --bumped-versiongit-cliff --bump -o CHANGELOG.mddocs: update changelog for v<VERSION>git tag -a v<VERSION> -m "Release v<VERSION>"Report changelog diff summary, version change (if releasing), and next step:
git push"git push && git push --tags"No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Primary accessibility skill for VS Code. REQUIRED for new feature and contribution work, and also applies to updates of existing UI. Covers accessibility help dialogs, accessible views, verbosity settings, signals, ARIA announcements, keyboard navigation, and ARIA labels/roles.
The English summary is being prepared. Showing the original description.
Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.
The English summary is being prepared. Showing the original description.
Act on user feedback attached to the current session. Use when the user submits feedback on the session's changes via the Submit Feedback button.
The English summary is being prepared. Showing the original description.
Add educational comments to the file specified, or prompt asking for file to comment if one is not provided.
The English summary is being prepared. Showing the original description.
Use when adding, modifying, or reviewing VS Code configuration policies. Covers the full policy lifecycle from registration to export to platform-specific artifacts. Run on ANY change that adds a `policy:` field to a configuration property.
The English summary is being prepared. Showing the original description.
Patterns and techniques for adding governance, safety, and trust controls to AI agent systems. Use this skill when: - Building AI agents that call external tools (APIs, databases, file systems) - Implementing policy-based access controls for agent tool usage - Adding semantic intent classification to detect dangerous prompts - Creating trust scoring systems for multi-agent workflows - Building audit trails for agent actions and decisions - Enforcing rate limits, content filters, or tool restrictions on agents - Working with any agent framework (PydanticAI, CrewAI, OpenAI Agents, LangChain, AutoGen)
The English summary is being prepared. Showing the original description.