Standardize GitHub issues, pull requests, commits, and documentation with Diataxis-aligned writing.
npx skills add https://github.com/juxt/claude-plugins --skill voice-juxt
Please help me install this Agent Skill. Skill: voice Source: https://github.com/juxt/claude-plugins/tree/main/plugins/chalk/skills/voice Command: npx skills add https://github.com/juxt/claude-plugins --skill voice-juxt
Inconsistent writing in GitHub issues, pull requests, commit messages, and project documentation leads to lost context, unclear reasoning, and wasted reader time, slowing down collaboration and code review for software engineering teams.
Invoke the voice skill when drafting GitHub issues, pull requests, commit messages, or project documentation to ensure your writing follows the project's standardized, reader-optimized structure and tone.
High-intent search queries and answers about installing and using this skill.
To standardize writing voice for GitHub issues and pull requests, apply a Diataxis-aligned structure that enforces consistent sections like summary, context, root cause, and decision rationale, eliminating ambiguous language and missing context.
The Diataxis framework for software documentation maps content to four reader need quadrants: explanation, tutorial, reference, and how-to. This ensures every piece of writing serves its intended purpose, from short commit messages to full documentation pages.
You can write clear commit messages with proper context by using standardized templates that map content to reader need quadrants, ensuring critical reasoning and necessary background are preserved rather than obscured by inconsistent or context-poor writing.
Structure pull request descriptions to reduce reviewer back-and-forth by including a consistent section palette: summary, context, tradeoff explanations, and test plans. This ensures no critical context is missing for reviewers or future contributors.
Yes, this writing voice standard works for existing project documentation. It maps content to reader need quadrants and applies a unified structure across all repository communication, ensuring documentation maintenance avoids marketing-heavy language.
dr-codeAutomate GitHub issues, pull requests, branches, CI/CD, and deployments via Rube MCP.
CapplequoppeAutomate GitHub pull request reviews by fetching diffs and posting comments via GitHub CLI.
EtaCassiopeiaOrchestrate GitHub issue lifecycle from triage to merge.
NetcrackerAudit Markdown files for markdownlint violations and fix them in-place.
