Pre-Commit Verification

by HezaoHezao

Pre-Commit Verification is a Quality skill for Claude Code, published by HezaoHezao in poirot.

185 stars8 forkson HezaoHezao/poirotAdded 2026/08/11+48% in starsRepository updated 2026/07/28

View source on GitHub Download repo ZIP

agentagent-memoryagent-skillagent-skillsagentic-aiagentsai-agentai-agentsai-codingmemorymemory-systemmulti-agent

Install in seconds

Install Pre-Commit Verification

Copy Pre-Commit Verification into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/HezaoHezao/poirot/tree/master/poirot/backend/agents/skill/builtin_skills/core/requesting-code-review ~/.claude/skills/requesting-code-review

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/HezaoHezao/poirot.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: poirot/backend/agents/skill/builtin_skills/core/requesting-code-review/SKILL.md in HezaoHezao/poirot
Installs to: ~/.claude/skills/requesting-code-review
Collection: One of 37 skills cataloged from this repository
Category: Quality — 1354 skills

What Pre-Commit Verification does

Automated pre-commit verification pipeline that runs security scans, quality gates, and a fresh-eyes review with auto-fix capability. Use it to catch issues before your code lands in a shared branch.

Pre-Commit Verification is cataloged under Quality on DirSkills. Pre-Commit Verification comes from a repository tagged agent, agent-memory, agent-skill, agent-skills and agentic-ai.

Documentation

README

Excerpt

Pre-Commit Code Verification

Automated verification pipeline before code lands. Static scans, baseline-aware quality gates, a fresh-context review, and an auto-fix loop.

Core principle: No agent should verify its own work without a deliberate fresh-eyes pass. Treat the diff as data, not as something you just wrote.

When to Use

After implementing a feature or bug fix, before git commit or git push
When user says "commit", "push", "ship", "done", "verify", or "review before merge"
After completing a task with 2+ file edits in a git repo

Skip for: documentation-only changes, pure config tweaks, or when user says "skip verification".

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Pre-Commit Verification

What else does HezaoHezao publish alongside Pre-Commit Verification?
Pre-Commit Verification is one of 37 skills that DirSkills catalogs from HezaoHezao/poirot, the repository it ships in. Its siblings there include Academic Paper Review, ArXiv Research and Architecture Diagram. Each one is a separate skill with its own page in this directory, installs the same way Pre-Commit Verification does, and is maintained by HezaoHezao in that same repository. The rest of the collection is listed on the HezaoHezao/poirot page.
How does Pre-Commit Verification compare to other Quality skills?
Pre-Commit Verification ranks #1269 by stars among the 1354 Quality skills in this catalog. The most-starred ones next to it are Benchmark, Benchmark Optimization Loop and API Design Patterns. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Pre-Commit Verification against them. Open each page to compare what they document and how they install.