critical-review-local

Apply project-specific feedback patterns to critical review workflows.

Updated Jun 15, 2026
One-click install
npx skills add https://github.com/stumman/hermes-harness-skills --skill critical-review-local
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: critical-review-local
Source: https://github.com/stumman/hermes-harness-skills/tree/main/.agents/skills/critical-review-local
Command: npx skills add https://github.com/stumman/hermes-harness-skills --skill critical-review-local

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill offers companion guidance for applying project-specific feedback patterns without altering the core critical-review skill contract.

Core Features & Use Cases

  • Project-Specific Guidance: Specializes in recurring patterns, repository architecture, and team norms.
  • Safety Rules Preservation: Ensures core skill outputs, safety rules, and global behavior remain unchanged.
  • Use Case: For a team dealing with specific project issues, use this Skill to implement feedback patterns without modifying the main critical-review workflow.

Quick Start

Use the critical-review-local skill to implement project-specific feedback patterns in your critical review process.

Frequently Asked Questions about critical-review-local

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

FAQPage Schema
How do I apply project-specific code review patterns without altering core safety rules?

This skill provides specialized companion guidance for the critical-review process, catering to project-specific needs by applying team norms and repository architecture insights without altering the core contract.

What is the best way to customize a critical review process for a specific repository architecture?

Customizing a critical review process for a specific repository architecture involves implementing localized feedback patterns that address specific false-positive and false-negative patterns while keeping global behavior unchanged.

Can I add team-specific norms to my code review workflow without modifying the main critical-review skill?

Yes, you can add team-specific norms to your code review workflow by using a localized companion skill that implements feedback patterns independently, ensuring the main critical-review skill outputs and global behavior remain unchanged.

How do I handle recurring false-positive and false-negative patterns in project code reviews?

Handle recurring false-positive and false-negative patterns in project code reviews by configuring project-level review adjustments that target these specific issues without executing safety rule changes.

When should I use a localized critical review skill instead of modifying the core review workflow?

Use a localized critical review skill instead of modifying the core workflow when you need to address project-level review adjustments and specific feedback patterns while strictly preserving existing safety rules and global behavior.