How do I install the Pr Writing skill?

Run npx skillmds@latest add tomevault-io/pr-writing-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pr Writing safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pr Writing?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pr Writing free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Pr Writing?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pr Writing by tomevault-io — Agent Skill

Name: Pr Writing
Author: tomevault-io

File contents

PR Writing

Announce at start: "Following the pr-writing skill for this submission."

Commit Messages

Use Conventional Commits format:

<type>(<scope>): <description>

[Optional body with context]

[Optional footer with references]

Commit Types

Type	When	Example
`feat`	New functionality	`feat(auth): add password reset flow`
`fix`	Bug fixes	`fix(api): handle null user in profile endpoint`
`refactor`	Code changes (no behavior change)	`refactor(db): extract query builder`
`test`	Adding/modifying tests	`test(auth): add edge cases for token expiry`
`docs`	Documentation changes	`docs: update API reference`
`chore`	Maintenance	`chore(deps): update express to 4.19`

Commit Rules

One logical change per commit
Imperative mood ("Add validation" not "Added validation")
Reference issues when applicable ("Fixes #123")
Separate refactors from feature changes

PR Template

## Summary
[One paragraph: what this PR does and why]

## Changes
- [Key change 1]
- [Key change 2]

## Testing
- [ ] Unit tests added/updated
- [ ] Integration tests pass
- [ ] Manually tested: [scenarios]

## Evidence
[Test output, screenshots, or other proof]

## Risks and Rollback
- Risk: [What could go wrong]
- Rollback: [How to undo]

Attribution Rules

Rule	Rationale
Human is always the author	Humans are accountable; AI is a tool
Never set AI as commit co-author	AI should not appear in git authorship
Never include "Generated with [AI tool]" in PR descriptions	Unless the PR directly relates to that tool
Note AI usage in PR body if significant	Transparency for reviewers

Branch Naming

<type>/<short-description>

Branch	Purpose
`feat/user-auth`	New feature
`fix/login-null-check`	Bug fix
`refactor/api-layer`	Code cleanup
`chore/deps-update`	Maintenance

When to Squash

Scenario	Action
Multiple iteration commits	Squash into one logical commit
Failed experiments	Drop entirely
Independent fixes	Keep separate
WIP "save work" commits	Squash

Related Skills

When	Invoke
PR needs tests	testing
PR needs code review	code-review
PR has security implications	secure-coding

Deep Reference

For principles, rationale, anti-patterns, and examples: guides/git-workflows-ai/git-workflows-ai.md

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: pr-writing-2description: Use when creating PRs, writing commit messages, managing branches, or preparing code for merge---# PR Writing**Announce at start:** "Following the pr-writing skill for this submission."## Commit MessagesUse Conventional Commits format:```text<type>(<scope>): <description>[Optional body with context][Optional footer with references]```### Commit Types| Type | When | Example || --- | --- | --- || `feat` | New functionality | `feat(auth): add password reset flow` || `fix` | Bug fixes | `fix(api): handle null user in profile endpoint` || `refactor` | Code changes (no behavior change) | `refactor(db): extract query builder` || `test` | Adding/modifying tests | `test(auth): add edge cases for token expiry` || `docs` | Documentation changes | `docs: update API reference` || `chore` | Maintenance | `chore(deps): update express to 4.19` |### Commit Rules- One logical change per commit- Imperative mood ("Add validation" not "Added validation")- Reference issues when applicable ("Fixes #123")- Separate refactors from feature changes## PR Template```markdown## Summary[One paragraph: what this PR does and why]## Changes- [Key change 1]- [Key change 2]## Testing- [ ] Unit tests added/updated- [ ] Integration tests pass- [ ] Manually tested: [scenarios]## Evidence[Test output, screenshots, or other proof]## Risks and Rollback- Risk: [What could go wrong]- Rollback: [How to undo]```## Attribution Rules| Rule | Rationale || --- | --- || **Human is always the author** | Humans are accountable; AI is a tool || **Never set AI as commit co-author** | AI should not appear in git authorship || **Never include "Generated with [AI tool]" in PR descriptions** | Unless the PR directly relates to that tool || **Note AI usage in PR body if significant** | Transparency for reviewers |## Branch Naming```text<type>/<short-description>```| Branch | Purpose || --- | --- || `feat/user-auth` | New feature || `fix/login-null-check` | Bug fix || `refactor/api-layer` | Code cleanup || `chore/deps-update` | Maintenance |## When to Squash| Scenario | Action || --- | --- || Multiple iteration commits | Squash into one logical commit || Failed experiments | Drop entirely || Independent fixes | Keep separate || WIP "save work" commits | Squash |## Related Skills| When | Invoke || --- | --- || PR needs tests | [testing](../testing/SKILL.md) || PR needs code review | [code-review](../code-review/SKILL.md) || PR has security implications | [secure-coding](../secure-coding/SKILL.md) |## Deep ReferenceFor principles, rationale, anti-patterns, and examples:`guides/git-workflows-ai/git-workflows-ai.md`---> Converted and distributed by [TomeVault](https://tomevault.io/claim/jerdaw) — claim your Tome and manage your conversions.

Frequently asked questions

Pr Writing