critique-skill

Structured code review feedback is generated by invoking the skill with a file path, which automatically detects the code lens by extension and produces a strict, copy-pasteable assessment template with ordered critiques.

Yes, you can critique the assistant's previous response by omitting the file path argument, which triggers a focused editorial critique of the immediately preceding output using a structured assessment format.

No, the critique process enforces strict no-edit rules and never modifies original source files; it reads the specified file or previous response and handles large files by producing annotated copies instead.

The best way to enforce consistent editorial feedback is using template-driven outputs, which provide a strict writing critique format including Assessment, ordered Critiques, and an inline Document section for actionable review.

Automatic lens detection works by evaluating the file extension to select either a writing or code critique lens, though explicit flags can be used to force a specific lens regardless of the file type.

Yes, you can receive summary-only critique outputs by configuring the optional output settings, which omits the inline document or code section and provides only the assessment and ordered critiques.