comment-checker

Interpret and respond to comment-checker feedback after Codex edits.

17|Updated May 29, 2026
One-click install
npx skills add https://github.com/code-yeongyu/lazyclaudecode --skill comment-checker-code-yeongyu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: comment-checker
Source: https://github.com/code-yeongyu/lazyclaudecode/tree/main/plugins/omo/components/comment-checker/skills/comment-checker
Command: npx skills add https://github.com/code-yeongyu/lazyclaudecode --skill comment-checker-code-yeongyu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use when Codex needs to understand or respond to automatic comment-checker feedback emitted after an edit-like PostToolUse hook.

Core Features & Use Cases

  • Interprets and relays comment-checker feedback after patches or edits to ensure required explanations or corrections before proceeding.
  • Integrates with PostToolUse hooks (apply_patch, write, edit, multi_edit, multiedit) to block progress until issues are resolved.

Quick Start

Review the latest patch and ensure any flagged comments are explained or corrected before moving on.

Frequently Asked Questions about comment-checker

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

FAQPage Schema
How do I handle PostToolUse feedback that blocks progress after applying a patch in Codex?

PostToolUse feedback that blocks progress after applying a patch in Codex is handled by automatically interpreting the comment-checker feedback and relaying required explanations or corrections before proceeding with the workflow.

What does a comment checker do when automated edit hooks flag missing explanations?

A comment checker used in automated edit hooks flags missing explanations and blocks workflow progress until the flagged comments on the latest patch are corrected or explained by the user.

Can I use PostToolUse hooks with apply_patch and write without exposing MCP tools?

PostToolUse hooks with apply_patch and write operate without exposing MCP tools, enforcing that non-edit tools are ignored and ensuring missing binaries do not disrupt normal work.

How do I fix flagged comments after a multi_edit operation in an automated workflow?

To fix flagged comments after a multi_edit operation in an automated workflow, review the latest patch and ensure any flagged comments are explained or corrected before moving on to the next step.

Why does my Codex workflow stop after an edit-like PostToolUse hook executes?

A Codex workflow stops after an edit-like PostToolUse hook executes because the comment-checker integrates with the hook to block progress until all flagged patch comments are resolved.

Does the comment checker disrupt normal work if required binaries are missing?

The comment checker does not disrupt normal work if required binaries are missing, as it is designed to ensure that missing binaries do not halt the automated workflow progress.