# Pull Request

> Use when a request should result in a focused, tested GitHub pull request.

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

---


# Pull-request workflow

## Before editing

- Resolve the exact allowed repository with `list_working_repos`.
- Materialize it with `add_source`; use only the returned source path.
- Read repository instructions, the affected code, and nearby tests.
- Restate the requested outcome in one sentence. Ask when acceptance criteria
  are genuinely unclear.

## Implement and verify

- Keep the patch narrow. Do not reformat or refactor unrelated code.
- Add or update a test that would fail before the change when practical.
- Run the smallest relevant test command, then inspect the complete diff.
- Never edit generated dependencies or commit build output unless the
  repository explicitly requires it.

## Publish

- Summarize the exact behavior change and tests.
- Call `github_publish_pull_request` once with the source name from
  `add_source`, a concrete title, and a body that explains what changed and how
  it was verified.
- Return the tool-authored PR URL. If the tool reports no changes or a recovery
  error, relay that result accurately instead of inventing success.