tone-check

Evaluate text tone, clarity, and professional register alignment.

2|Updated May 24, 2026
One-click install
npx skills add https://github.com/CivicActions/ai-runbook-jh --skill tone-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tone-check
Source: https://github.com/CivicActions/ai-runbook-jh/tree/main/skills/tone-check
Command: npx skills add https://github.com/CivicActions/ai-runbook-jh --skill tone-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates ambiguity and tone mismatches in professional communication, ensuring your writing is direct, clear, and aligned with project-specific voice standards.

Core Features & Use Cases

  • Tone Assessment: Evaluates text against specific registers like technical documentation, PR descriptions, or commit messages.
  • Actionable Rewrites: Identifies filler words, passive voice, and hedging, providing concrete suggestions for improvement.
  • Use Case: Use this skill to review a draft PR description or a sensitive tracker comment to ensure it sounds professional, concise, and aligned with your team's established voice.

Quick Start

Use the tone-check skill to review the tone and clarity of the text provided in this pull request description.

Frequently Asked Questions about tone-check

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

FAQPage Schema
How do I check the tone and clarity of a pull request description?

To check the tone of a pull request description, the skill evaluates the text against technical documentation registers and identifies passive voice or hedging, providing concrete rewrite suggestions to ensure professional, direct communication.

How do I review writing style for technical documentation?

Reviewing writing style for technical documentation involves assessing the text for filler words and professional register alignment, then applying project-specific voice configurations to generate context-aware feedback and style improvements.

Can I use a style guide to align commit messages with project voice standards?

Yes, you can align commit messages with project voice standards by integrating project-level style guides and audience norms, which allows the review process to provide context-aware feedback based on your specific configurations.

What is the best way to fix passive voice and hedging in tracker comments?

The best way to fix passive voice and hedging in tracker comments is to evaluate the text for tone mismatches and ambiguity, then apply actionable rewrites that make the communication concise and aligned with established team voice.

Does tone review work without configuring audience norms?

Tone review requires integration with project-level style guides and audience norms to function accurately, as these configurations provide the necessary context to evaluate professional register alignment and deliver relevant feedback.