Generate effect-focused commit messages, PR titles, and work item descriptions.
npx skills add https://github.com/shellicar/skills --skill writing-style-shellicar
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
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.
Rewrite my commit message to focus on what changed and why.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
jim60105Generate Conventional Commits messages with issue resolution links from code changes.
mathiasbourgoinStandardize git commit messages, branch names, and pull request descriptions.
ascerra-fullsend-rehearsalAnalyze code changes for correctness, security, intent, style, and documentation compliance.
handsomelong922Enforce development conventions and conventional commit patterns for everything-claude-code.
