writing-style

Generate effect-focused commit messages, PR titles, and work item descriptions.

Updated Mar 31, 2026

Search Tags:#writing #commit #style #guidelines #pr #software

Ready to run

npx skills add https://github.com/shellicar/skills --skill writing-style-shellicar

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: writing-style
Source: https://github.com/shellicar/skills/tree/main/skills/writing-style
Command: npx skills add https://github.com/shellicar/skills --skill writing-style-shellicar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents commit messages, PR titles, and work item text from describing implementation details, ensuring they instead convey the effect and purpose of changes, which improves clarity for reviewers and stakeholders.

Core Features & Use Cases

Emphasizes describing the effect of a change rather than how it was implemented.
Defines prohibited styles such as em dashes and overly detailed implementation language.
Provides structured formats for PR descriptions, titles, commit messages, and work item entries, helping teams maintain consistent, concise communication across development workflows.

Quick Start

Rewrite my commit message to focus on what changed and why.

Frequently Asked Questions about writing-style

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

FAQPage Schema

How do I write commit messages that focus on the impact instead of implementation details?▼

Impact-focused commit messages describe what changed and why, omitting implementation details. This style enforces specific rules like avoiding em dashes and limiting bullet counts to ensure concise communication that improves clarity for reviewers and stakeholders.

What is the best way to structure PR titles and descriptions for software development workflows?▼

PR titles and descriptions should use structured formats that convey the effect and purpose of changes. Following consistent style guidelines across version control and project-management systems helps teams avoid overly detailed implementation language and maintain concise summaries.

Why should I avoid implementation details in my pull request summaries?▼

Avoiding implementation details in pull request summaries prevents clutter and ensures the text conveys effect and purpose. This approach improves clarity for stakeholders and reviewers by focusing on what changed and why, rather than how the code was written.

Does this writing style allow em dashes in work item descriptions and commit logs?▼

No, this writing style prohibits em dashes in commit logs, work item descriptions, and PR text. It enforces specific formatting constraints, including limiting bullet counts, to maintain concise and impact-focused communication across software development workflows.

Can I use these writing guidelines for task titles in project-management systems?▼

Yes, these writing guidelines apply to task titles in project-management systems. They provide structured formats for work item entries and task titles, helping teams maintain consistent, concise communication that explains what changed and why across development workflows.