technical-feedback

Enforce a six-step code-review feedback protocol with project-principle verification.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/krwhynot/crispy-crm --skill technical-feedback
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: technical-feedback
Source: https://github.com/krwhynot/crispy-crm/tree/main/.claude/skills/technical-feedback
Command: npx skills add https://github.com/krwhynot/crispy-crm --skill technical-feedback

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishes a bidirectional code-review protocol that emphasizes verification before implementation and pushes back on principle violations, ensuring high-quality, principled changes.

Core Features & Use Cases

  • Receiving Feedback: Read, understand, verify against the codebase, evaluate against principles, respond, and implement item-by-item.
  • Giving Feedback: Prioritize project principles, provide specific, actionable guidance with exact fixes and paths forward.
  • Principle Violations: Automatic pushback for Fail-Fast, Single Data Provider, Zod-at-API-Boundary, and Design-System violations.

Quick Start

When reviewing a PR, respond with precise code-level changes or justification, following the pattern: identify issue, propose fix, and include a verification step.

Frequently Asked Questions about technical-feedback

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

FAQPage Schema
How do I structure code review feedback to be more actionable and consistent?

Structured feedback follows a six-step pattern: READ the code, UNDERSTAND the context, VERIFY against your codebase, EVALUATE against project principles, RESPOND with specific fixes, and IMPLEMENT item-by-item. This ensures consistency and reduces back-and-forth cycles in PR reviews.

What should I check for when reviewing pull requests against project principles?

Verify adherence to Fail-Fast, Single Data Provider, Zod-at-API-Boundary, Design System, and Deprecated Patterns principles. Automatic pushback on violations ensures high-quality changes aligned with your project's architecture and standards.

How do I give precise code-review feedback with exact fixes?

Identify the specific issue in the PR, propose an exact code-level change with file paths, and include a verification step to confirm the fix works. This replaces vague suggestions with actionable guidance developers can implement directly.

Can I use this feedback approach for AI tool suggestions and developer exchanges?

Yes, the bidirectional protocol works for feedback between developers, AI tools, and code review systems. It standardizes how suggestions are verified against the codebase and principles before implementation.

Why does principle-based pushback matter in code review?

Principle-based pushback prevents inconsistent implementations and technical debt by catching violations early. It enforces Single Data Provider, Zod validation at boundaries, and Design System compliance before code merges.

Should I implement feedback all at once or one item at a time?

Implement one item at a time after verification. This reduces complexity, makes testing straightforward, and simplifies rollback if issues arise during PR review cycles.