skills.rest
EpicenterHQ
EpicenterHQOFFICIAL
Explore all skills by this author →
Website𝕏@EpicenterHQGitHub

honesty

Deliver blunt, actionable feedback on code reviews and technical discussions.

4.7k|374|Updated Mar 16, 2023
Search Tags:#feedback#quality#honesty#code-review#blunt-communication#technical-discussion
One-click install
npx skills add https://github.com/EpicenterHQ/epicenter --skill honesty
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: honesty
Source: https://github.com/EpicenterHQ/epicenter/tree/main/.agents/skills/honesty
Command: npx skills add https://github.com/EpicenterHQ/epicenter --skill honesty

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the need for direct, honest feedback to improve code quality and decision-making during technical discussions.

Core Features & Use Cases

  • Direct, blunt critique during code reviews with actionable suggestions.
  • Clarified expectations for honest, professional discourse in engineering conversations.
  • Use Case: When reviewing a PR, it calls out issues and proposes concrete improvements without softening critique.

Quick Start

Provide blunt, actionable feedback on a code snippet or pull request to improve quality.

Frequently Asked Questions about honesty

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

FAQPage Schema
How do I write blunt code review feedback that is actually actionable?▼

To write blunt code review feedback, identify poor code quality and deliver direct critique with concrete suggestions for improvement, avoiding passive language that softens the technical discussion.

What is the best way to give direct feedback during architectural discussions?▼

The best way to give direct feedback during architectural discussions is to enforce clear expectations for professional discourse, calling out issues and proposing concrete improvements without softening the critique.

Can I use blunt communication to correct poor code quality in pull requests?▼

Yes, you can use blunt communication to correct poor code quality in pull requests by identifying issues and proposing concrete improvements without softening critique.

How do you avoid passive language when giving technical feedback?▼

To avoid passive language when giving technical feedback, enforce clear expectations for honest discourse and require concrete suggestions for improvement rather than softening the critique.

When do I need brutal honesty during collaborative debugging?▼

You need brutal honesty during collaborative debugging when direct, honest feedback is required to improve code quality and decision-making across technical teams without softening the critique.

Does blunt communication work for code reviews across technical teams?▼

Yes, blunt communication works for code reviews across technical teams by enforcing clear expectations for honesty and delivering actionable feedback to improve code quality and decision-making.

Related Skills

Explore More Software Engineering Skills→
fartmonarchfartmonarch
1

chinese-code-review

Rewrite blunt code review feedback into tactful, prioritized Chinese comments.

Community
Intermediate
JeffallanJeffallan
10.9k

Code Reviewer

Automate pull request reviews for code quality, security, and maintainability.

Community
Basic
zajcazajca
2

go-linting

Configure golangci-lint with recommended Go linters for static analysis.

Community
Basic
48Nauts-Operator48Nauts-Operator
3

code-review

Review pull requests using a systematic code review checklist.

Community
Basic