skills.rest
pnewsam
pnewsamCOMMUNITY
Explore all skills by this author →
Website𝕏@paultakumaGitHub

writing-conventions

Applies sentence-level prose style rules to PRs, issues, plans, and commit messages.

1|Updated Apr 15, 2026
Search Tags:#writing#editing#commit messages#technical writing#style guide#pull requests#prose style
One-click install
npx skills add https://github.com/pnewsam/skills --skill writing-conventions-pnewsam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-conventions
Source: https://github.com/pnewsam/skills/tree/main/registry/writing-conventions
Command: npx skills add https://github.com/pnewsam/skills --skill writing-conventions-pnewsam

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Technical artifacts like PR descriptions, code reviews, Linear issues, and commit messages often drift into inconsistent, verbose, or hedged prose. This Skill provides one shared sentence-level style standard so every human-facing artifact reads in the same concise, direct voice. ## Core Features & Use Cases - Shared prose rules: Enforces one idea per sentence, active voice, plain words, and no hedging across all work artifacts. - Style-only scope: Governs how prose reads while leaving artifact structure (headings, sections, checklists) to each artifact's own standard or repository template. - Use Case: When drafting a PR body or Linear issue, apply these conventions to tighten a verbose paragraph into short declarative sentences, e.g. splitting chained clauses joined by em-dashes into separate statements. ## Quick Start Use the writing-conventions skill to rewrite this PR description in concise, active-voice prose.

Frequently Asked Questions about writing-conventions

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

FAQPage Schema
How do I write concise PR descriptions and commit messages?▼

Write one idea per sentence in active voice with plain words, and cut hedging phrases like "it's worth noting." Split sentences that chain multiple points with em-dashes or semicolons into short declarative statements.

What writing style standard applies to Linear issues and planning documents?▼

The shared prose conventions apply: one idea per sentence, active voice, plain words, and no meta-commentary. The structure of each artifact, such as headings and required sections, comes from that artifact's own template, not from these style rules.

Does this style guide define the structure of PRs or issues?▼

No. It governs sentence-level prose style only. Artifact structure, including headings, required sections, and checklists, lives in each artifact's own standard, and a repository template's structure takes precedence where one exists.

When should I not split a sentence under these conventions?▼

Split only when a sentence joins two or more distinct ideas. Length should track substance: say a thing once in as few sentences as it needs, without padding or restating the same point in two places.

Which skills reference these writing conventions?▼

The conventions are referenced by pr-conventions, review-work, create-issue, and create-project, so one voice carries across PRs, reviews, and Linear artifacts however each is produced.

Related Skills

Explore More Content & Communication Skills→
harnessprotocolharnessprotocol
9

capture

Append timestamped conversation facts to a session-staging markdown file.

Official
Intermediate
mcmurrymmcmurrym

kit-and-kaboodle

Automates Linear issue implementation through Playwright verification, Codex review, and PR creation.

Community
Advanced
forztfforztf
9

speckit-constitution-zh

Create or update project charters and synchronize dependent templates.

Community
Advanced
eboodyeboody

mds-css-conventions

Enforce CSS class naming and scoping conventions for generated components.

Community
Intermediate