How do I install the Pull Request skill?

Run npx skillmds@latest add srobinson/pull-request 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 Pull Request safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pull Request?

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 Pull Request free to use?

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

Who published Pull Request?

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

Pull Request by srobinson — Agent Skill

Name: Pull Request
Author: srobinson

File contents

Pull Request Workflow

All helioy repos use squash merge. The PR title becomes the squash commit message, which release-please parses to generate changelogs and version bumps.

PR Title Format

PR titles MUST follow the Conventional Commits specification:

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

Types

Type	When	Appears in changelog
`feat`	New feature or capability	Yes (Features)
`fix`	Bug fix	Yes (Bug Fixes)
`perf`	Performance improvement	Yes (Performance)
`refactor`	Code restructuring, no behavior change	Hidden
`docs`	Documentation only	Hidden
`test`	Adding or updating tests	Hidden
`chore`	Maintenance, deps, CI	Hidden
`ci`	CI/CD changes	Hidden

Scope

Optional. Use the crate or component name when the change is localized:

feat(cm-store): add FTS5 prefix query support
fix(cm-cli): handle broken pipe on MCP shutdown
refactor(cm-core): extract ScopePath validation

Omit scope for cross-cutting changes:

feat: implement tools.toml codegen pipeline
chore: update workspace dependencies

Examples

feat: implement cx_recall tool with FTS5 search
feat(cm-store): add content deduplication via BLAKE3
fix: remove isError flag from MCP error responses
refactor: split monolithic tools.rs into per-tool modules
test: add 31 integration tests for MCP tool handlers
chore: add CI and release workflows
docs: update CLAUDE.md with tool conventions
perf(cm-store): optimize scope ancestor walk query

Branch Commits

Branch commits do NOT need conventional commit format. The existing convention works fine:

worker[ALP-1400]: Implement tools.toml codegen pipeline
review[ALP-1367]: Fix MCP instructions placement

Only the PR title matters for release-please.

Workflow

Push branch to remote with -u flag
Create PR with gh pr create
PR title follows conventional commits format above
PR body includes summary bullets and test plan
Squash merge into main preserves the PR title as the commit message

PR Body Template

## Summary
- <bullet points describing what changed and why>

## Test plan
- [ ] All workspace tests pass (`just test`)
- [ ] Clippy clean (`just check`)
- [ ] <additional verification steps>

---name: pull-requestdescription: Create pull requests with conventional commit titles for squash merge. Use when creating PRs, preparing branches for merge, or when the user says "create a PR", "open a PR", "prepare for merge", or "push this".---# Pull Request WorkflowAll helioy repos use squash merge. The PR title becomes the squash commit message, which release-please parses to generate changelogs and version bumps.## PR Title FormatPR titles MUST follow the Conventional Commits specification:```<type>(<scope>): <description>```### Types| Type | When | Appears in changelog ||------|------|---------------------|| `feat` | New feature or capability | Yes (Features) || `fix` | Bug fix | Yes (Bug Fixes) || `perf` | Performance improvement | Yes (Performance) || `refactor` | Code restructuring, no behavior change | Hidden || `docs` | Documentation only | Hidden || `test` | Adding or updating tests | Hidden || `chore` | Maintenance, deps, CI | Hidden || `ci` | CI/CD changes | Hidden |### ScopeOptional. Use the crate or component name when the change is localized:```feat(cm-store): add FTS5 prefix query supportfix(cm-cli): handle broken pipe on MCP shutdownrefactor(cm-core): extract ScopePath validation```Omit scope for cross-cutting changes:```feat: implement tools.toml codegen pipelinechore: update workspace dependencies```### Examples```feat: implement cx_recall tool with FTS5 searchfeat(cm-store): add content deduplication via BLAKE3fix: remove isError flag from MCP error responsesrefactor: split monolithic tools.rs into per-tool modulestest: add 31 integration tests for MCP tool handlerschore: add CI and release workflowsdocs: update CLAUDE.md with tool conventionsperf(cm-store): optimize scope ancestor walk query```## Branch CommitsBranch commits do NOT need conventional commit format. The existing convention works fine:```worker[ALP-1400]: Implement tools.toml codegen pipelinereview[ALP-1367]: Fix MCP instructions placement```Only the PR title matters for release-please.## Workflow1. Push branch to remote with `-u` flag2. Create PR with `gh pr create`3. PR title follows conventional commits format above4. PR body includes summary bullets and test plan5. Squash merge into main preserves the PR title as the commit message## PR Body Template```markdown## Summary- <bullet points describing what changed and why>## Test plan- [ ] All workspace tests pass (`just test`)- [ ] Clippy clean (`just check`)- [ ] <additional verification steps>```

Frequently asked questions

Pull Request