Review the diff, then commit - Agent Skills
SponsoredSkillry: Agent Skills with taste. Designed and tested in-house, so one prompt gives you polished slides, web pages and launch videos.Skillry: Agent Skills with taste Try free Skills
Agent Skills
  • Skills
  • Picks
  • ShopSoon
  • Solutions
  • Specification
  • Submit
Agent Skills
All picks

Scene picks

Review the diff, then commit

A test, a review, a commit message, then a changelog if a human will read it.

A marked-up diff strip next to a packed box

Why these

These four are a sequence, not a toolbox. Running the changelog skill on an uncommitted experiment writes release notes for work you may still throw away.

Install in this order

  1. 1tdd-workflow

    When the change is logic or a bugfix. Skip it for a layout tweak. The skill itself says UI layout is a poor fit, and exploratory work should be a spike first.

  2. 2code-reviewer

    On the diff, before you commit. It asks for a verdict. A review with no verdict is a summary.

  3. 3commit-work

    When you are ready to commit. Conventional Commits, and it wants you to look at the staged diff for secrets before the message.

  4. 4changelog-generator

    Only after the commits exist, and only if a user will read the notes. Do not run it on a private branch.

Not for this

CodeQL, which needs a database you build first. Jira, which needs an account. pr-creator, which follows Gemini CLI's title check and will nag you on any other repo.

Agent Skills

Discover and share powerful Agent Skills for AI assistants

GitHubX (Twitter)
Skills
  • View All
  • Install Guide
  • Documentation
  • Solutions
  • Product Launch Video
  • Submit
Tools
  • Claude Code
  • Cursor
  • OpenCode
  • Codex CLI
  • Gemini CLI
Resources
  • anthropics/skills
  • awesome-claude-skills
  • vercel-labs/agent-skills
  • kepano/obsidian-skills
Company
  • About
  • Changelog
  • Privacy Policy
  • Terms of Service

Sponsored by Vectrust @ OpenDev Org & NextRouter Alliance

© 2026 EvergreenAI. Built with JimmyLv