hermes-commit

Name: hermes-commit
Availability: InStock
Author: Pandaworks

Verify code review and lint checks, then execute atomic commits.

Updated Mar 1, 2026

Search Tags:#git #workflow #commit #lint #code-review #format #atomic-commits

Ready to run

npx skills add https://github.com/pandaworks-software-plt/pandahrms-skills --skill hermes-commit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: hermes-commit
Source: https://github.com/pandaworks-software-plt/pandahrms-skills/tree/main/skills/hermes-commit
Command: npx skills add https://github.com/pandaworks-software-plt/pandahrms-skills --skill hermes-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verify that changes are reviewed and clean, then plan and execute atomic commits. This skill never changes code -- if something is wrong, it stops and tells you to fix it first.

Core Features & Use Cases

Gate Check: Require code review through /athena-review before committing; offer an option to skip review with explicit override.
Format/Lint Verification: Detect project type (.NET vs JS/TS) and run verify-no-changes or lint checks without auto-fixing.
Atomic Commit Planning: Group changes into small, independent commits with conventional messages and present a commit plan before execution.
Safe Execution: Stages commits individually and ensures no unintended code changes are made.

Quick Start

Trigger /hermes-commit after your changes have been reviewed and linted to begin the atomic-commit workflow.

Frequently Asked Questions about hermes-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce code review and lint checks before creating atomic git commits?▼

You can enforce review gates and lint checks before committing by triggering the workflow after changes are reviewed. It requires a review pass, runs format and lint verification without auto-fixing, then plans and executes atomic commits with conventional messages.

Does this commit workflow support both .NET and JavaScript/TypeScript projects?▼

Yes, the commit workflow supports both .NET and JavaScript/TypeScript projects. It automatically detects the project type to run the appropriate verify-no-changes or lint checks in verify-only mode before staging commits.

What is the best way to automate conventional commit messages after a code review?▼

Automating conventional commit messages after review involves gathering staged changes, grouping them into small independent commits, and generating conventional messages. The workflow presents a commit plan for approval before executing the atomic commits individually.

Why does my automated commit workflow stop and refuse to commit changes?▼

The automated commit workflow stops when format or lint verification fails, or when a code review gate is not satisfied. It never alters source code to fix issues, instead halting the process and instructing you to fix the underlying problems first.

Can I skip the code review gate when committing changes?▼

Yes, you can skip the code review gate when committing changes by using an explicit override option. This allows you to bypass the required review step and proceed directly to format verification and atomic commit planning.

How do I group staged changes into independent atomic commits?▼

To group staged changes into independent atomic commits, the workflow gathers all current changes and plans small, logical groupings. It generates conventional commit messages for each group and presents a complete commit plan before staging and executing them individually.