# Validate Pr

> Validate the current Pull Request branch name, body, and status against Marshroom conventions

- Skill: `vkehfdl1/validate-pr` (Agent Skill)
- Install (CLI): `npx skillmds add vkehfdl1/validate-pr`
- Raw SKILL.md: https://api.skillmd.com/api/skills/vkehfdl1/validate-pr/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: vkehfdl1 (https://skillmd.com/u/vkehfdl1)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/vkehfdl1/validate-pr

---


Validate the current Pull Request against Marshroom conventions.

Steps:
1. Read `${MARSHROOM_STATE:-~/.config/marshroom/state.json}` and parse the JSON
2. Run `git branch --show-current` to get the current branch name
3. Find the cart entry whose `branchName` matches the current git branch. If no match, tell the user they're not on a cart issue branch
4. Get the current PR info: `gh pr view --json title,body,headRefName`
5. Validate the following:

**Branch Name Check:**
- The PR's head branch should match the matched cart entry's `branchName`
- Expected format: `Feature/#N` or `HotFix/#N`
- If mismatched, show: "Branch mismatch: expected '{branchName}', got '{actual}'"

**PR Body Check:**
- The body MUST contain `close #{issueNumber}`
- If missing, suggest: `gh pr edit --body "$(gh pr view --json body -q '.body')\n\nclose #<issueNumber>"`

**Status Check:**
- Read the `status` field from the matched cart entry
- After PR creation, status should be `"pending"`
- If status is still `"running"`, warn that the status was not updated (suggest running `marsh pr`)
- If status is `"soon"`, warn that `/start-issue` may not have been run

**Summary:**
- Show pass/fail status for each check
- If all checks pass, confirm the PR is valid
- If any check fails, provide the fix commands