skills.rest
wellcrafted-dev
wellcrafted-devOFFICIAL
Explore all skills by this author →
GitHub

honesty

Enforce direct, critical feedback in code reviews and technical discussions.

35|4|Updated Dec 18, 2024
Search Tags:#code review#feedback#communication#honesty#constructive criticism#technical discussion
One-click install
npx skills add https://github.com/wellcrafted-dev/wellcrafted --skill honesty-wellcrafted-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: honesty
Source: https://github.com/wellcrafted-dev/wellcrafted/tree/main/.claude/skills/honesty
Command: npx skills add https://github.com/wellcrafted-dev/wellcrafted --skill honesty-wellcrafted-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that feedback provided during code reviews and technical discussions is direct, unambiguous, and focused on constructive criticism, preventing superficial agreement and promoting genuine improvement.

Core Features & Use Cases

  • Direct Feedback: Encourages blunt and clear identification of errors or areas for improvement.
  • Core Interaction Expectation: Sets a baseline for how all interactions should be conducted, prioritizing truthfulness over politeness.
  • Use Case: When reviewing a pull request, this skill ensures the reviewer points out any logical flaws or inefficiencies without softening the critique.

Quick Start

Provide honest feedback on the attached code snippet.

Frequently Asked Questions about honesty

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

FAQPage Schema
What is brutally honest feedback in code reviews?▼

Brutally honest feedback in code reviews is direct, unambiguous critique that prioritizes truthfulness over politeness to identify logical flaws and inefficiencies, prevent superficial agreement, and promote genuine improvement.

How do I provide constructive criticism during technical discussions?▼

Provide constructive criticism during technical discussions by enforcing blunt communication that clearly identifies errors or areas for improvement without softening the critique, ensuring collaborative problem-solving avoids groupthink.

Can I use direct feedback for design discussions and collaborative problem-solving?▼

Yes, direct feedback is applicable to design discussions and any collaborative problem-solving scenario, enforcing a behavioral guideline that requires adherence to blunt communication to ensure genuine improvement.

Why does preventing superficial agreement matter in code reviews?▼

Preventing superficial agreement matters in code reviews because it enforces critical feedback that stops polite approval of logical flaws, breaking groupthink and ensuring the technical baseline prioritizes truthfulness for genuine improvement.

What are the limitations of blunt communication in technical feedback?▼

The limitation of blunt communication in technical feedback is its strict enforcement of prioritizing truthfulness over politeness, which may feel harsh during collaborative problem-solving but is required to prevent superficial agreement.

Related Skills

Explore More Software Engineering Skills→
lidge-junlidge-jun
5

receiving-code-review

Guide users through verifying and responding to code review feedback.

Community
Intermediate
Abrahan-EagleAbrahan-Eagle

code-review-excellence

Guide structured, constructive feedback for code reviews with checklists and templates.

Community
Advanced
eliottbusinesseliottbusiness

requesting-code-review

Automate pre-commit code review with static analysis and security scanning.

Community
Advanced
knopkiknopki
1

professional-honesty

Verify claims and provide evidence-based reasoning in responses.

Community
Basic