Agent skill · Security

requesting-code-review

Pre-commit review: security scan, quality gates, auto-fix.

HezaoHezaogithub.com/HezaoHezaoGitHub ↗
claude-codecan modify filesMIT
Install
npx skills add HezaoHezao/poirot --skill requesting-code-review --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Declared author: Adapted from hermes-agent (Nous Research, MIT); obra/superpowers + MorAlekss
Allowed tools: -bash-read_file-str_replace
Path: poirot/backend/agents/skill/builtin_skills/core/requesting-code-review/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 139
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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 skill vs github-code-review:** This skill verifies YOUR changes before committing. `github-code-review` reviews OTHER people's PRs on GitHub with inline comments. ## Step 1 — Get the diff ```bash git diff --cached ``` If empty, try `git diff` then `git diff HEAD~1 HEAD`. If `git diff --cached` is empty but `git diff` shows changes, tell the user to `git add <files>` first. If still empty, run `git status` — nothing to verify. If the diff exceeds 15,000 characters, split by file: ```bash git diff --name-only git diff HEAD -- sp

What's inside
Steps it walks through
  1. When to Use
  2. Step 1 — Get the diff
  3. Step 2 — Static security scan
  4. Step 3 — Baseline tests and linting
  5. Step 4 — Self-review checklist
  6. Step 5 — Fresh-eyes review
  7. Step 6 — Auto-fix loop
  8. Step 7 — Commit
  9. Reference: Common Patterns to Flag
  10. Python
  11. JavaScript
  12. Pitfalls
Commands it runs
git diff --cached
git diff --name-only
git diff HEAD -- specific_file.py
Hardcoded secrets
git diff --cached | grep "^+" | grep -iE "(api_key|secret|password|token|passwd)\s*=\s*['\"][^'\"]{6,}['\"]"
Shell injection
git diff --cached | grep "^+" | grep -E "os\.system\(|subprocess.*shell=True"
Dangerous eval/exec
git diff --cached | grep "^+" | grep -E "\beval\(|\bexec\("
Unsafe deserialization
More from poirot
All skills →
About this skill
What does the requesting-code-review skill do?

Pre-commit review: security scan, quality gates, auto-fix.

How do I install it?

Run `npx skills add HezaoHezao/poirot --skill requesting-code-review --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From HezaoHezao/poirot, a repository with 139 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going