# Handling Pull Requests

> Guides PR workflows: creating PRs, addressing review feedback, replying to comments. Use when creating PRs, responding to code review, or managing PR lifecycle. Triggers: create PR, open PR, new PR, make PR, draft PR, create draft, make draft, address feedback, review comments, respond to review, PR workflow, pull request creation, commit and push, push and PR.

- **Type:** Skill
- **Install:** `agentstack add skill-quatico-solutions-agent-skills-handling-pull-requests`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [quatico-solutions](https://agentstack.voostack.com/s/quatico-solutions)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [quatico-solutions](https://github.com/quatico-solutions)
- **Source:** https://github.com/quatico-solutions/agent-skills/tree/main/skills/handling-pull-requests

## Install

```sh
agentstack add skill-quatico-solutions-agent-skills-handling-pull-requests
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Handling Pull Requests

## When to Use This Skill

```dot
digraph pr_workflow {
    rankdir=TB;
    node [shape=diamond];

    start [label="PR-related task?" shape=ellipse];
    q1 [label="Creating a PR?"];
    q2 [label="Addressing review\nfeedback?"];
    q3 [label="SSO-gated page?"];

    node [shape=box];
    this [label="This skill\n(handling-pull-requests)"];
    bb [label="bb CLI\n(working-with-bitbucket-api)"];
    platform [label="Browser (last resort)\n(working-with-bitbucket-web)"];
    commit [label="commit-notation skill"];

    start -> q1;
    q1 -> this [label="yes"];
    q1 -> q2 [label="no"];
    q2 -> this [label="yes"];
    q2 -> q3 [label="no"];
    q3 -> platform [label="yes"];

    this -> bb [label="for BB operations\n(incl. image uploads)" style=dashed];
    this -> commit [label="for commits" style=dashed];
}
```

---

## PR Creation Workflow

### Pre-flight Checklist

```
- [ ] Branch pushed to remote
- [ ] All commits follow commit-notation
- [ ] Tests passing locally
- [ ] Reviewer identified
```

### PR Description Template

```markdown
## Summary
[1-3 sentences: what this PR does and why]

## Changes
- Change 1
- Change 2

## Test plan
- [ ] Test case 1
- [ ] Test case 2

---
Generated with Claude Code
```

### Steps

1. **Push branch** if not already pushed
2. **Determine target branch** — check the repo's default branch (usually `develop` for Quatico repos). Use `--base` if it differs from the repo default.
3. **Fill description** using template above
4. **Add reviewers** as identified
5. **Create PR**: `bb pr create --title "..." --body "..." --base develop --reviewer "Name"`
6. **Verify** with `bb pr view ` — **check the `Dest:` line** to confirm the target branch is correct

> **Always use `bb` CLI** for Bitbucket PR operations (create, edit, comment, approve, merge). It handles markdown descriptions, reviewer management, image uploads (`bb pr comment --image` / `bb download upload`), and all PR lifecycle operations. See `bb --help`. Browser is only needed for SSO-gated pages. If `bb` is not installed, stop and guide the user through setup (`install-dependencies.sh` + `bb auth login`) before proceeding.

> **Target branch matters.** `bb pr create` auto-detects the repo's default branch via the Bitbucket API. If auto-detection fails, it falls back to `main`. For repos that use `develop` (all Quatico repos), always pass `--base develop` explicitly to be safe. If a PR was created with the wrong target, fix it with `bb pr edit  --base develop`.

---

## Addressing Review Feedback

### Process

1. **Read ALL comments first** — don't fix piecemeal: `bb pr view  --comments`
2. **Categorize each comment**:
   - **Question** → needs reply
   - **Change request** → needs code change + reply
   - **Approval/praise** → acknowledge or resolve
3. **Make code changes** for all change requests
4. **Commit with notation**: `b: Address review feedback` (or more specific)
5. **Reply to comments** explaining what was done: `bb pr comment  --body "..."`
6. **Resolve comments** that were fully addressed: `bb pr comment  --resolve `
7. **Push changes**

### Comment Response Checklist

```
- [ ] Read all comments
- [ ] Make code changes
- [ ] Commit changes
- [ ] Reply to each comment
- [ ] Resolve fully-addressed comments (where possible)
- [ ] Push
```

---

## Replying to Comments

### When to Reply vs Resolve

| Action | Use When |
|--------|----------|
| **Reply** | Questions, discussions, explanations, disagreements |
| **Resolve** | Task completed, feedback acknowledged and implemented |

### AI Signature Convention

When Claude posts comments on behalf of a user, **always sign**.

**Format:** *🤖 – [Model Name]* in italic (if the editor supports it)

Example: *🤖 – Claude*

**Placement:**
- **Inline:** Add at end of your reply: `...fixed in commit abc123.` *🤖 – Claude*
- **Own line:** Start a new paragraph directly after your text—no blank line above or below

**Why:** Prevents impersonation and maintains transparency. The signature should be unobtrusive but always present.

### Reply Guidelines

- Be concise and direct
- Reference specific code changes if applicable
- Use platform's rich text editor carefully (see platform skill)

### Attaching Screenshots

Screenshots (before/after diffs, repros, measurements) are one of the highest-value
things a review can include — attach them directly, no browser needed:

```bash
bb pr comment 42 --image before-after.png --body "Layout regression below:"
```

The image is uploaded to the repo Downloads area and referenced inline. See the
`working-with-bitbucket-api` skill for details and caveats (private URLs, naming).

---

## Integration with Other Skills

| Skill | Use For |
|-------|---------|
| `working-with-bitbucket-api` | **Primary**: all Bitbucket operations via `bb` CLI |
| `commit-notation` | Commit messages (F:, B:, R:, etc.) |
| `markdown` | CommonMark formatting for PR descriptions and comments |
| `writing-clearly-and-concisely` | PR descriptions and comments |
| `working-with-bitbucket-web` | Last resort: SSO-gated pages only |

---

## Common Mistakes

| Mistake | Fix |
|---------|-----|
| Fixing comments one-by-one | Read ALL first, then batch changes |
| Forgetting AI signature | Always add `🤖 – Claude` to AI comments |
| Using markdown bullets in rich text | Use toolbar buttons or platform skill guidance |
| Not pushing after replying | Push after all replies done |
| PR targeting wrong branch | Always verify `Dest:` in `bb pr view` output. Fix with `bb pr edit  --base develop` |
| Assuming `main` is the target | Quatico repos use `develop`. Always pass `--base develop` or verify auto-detection |

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [quatico-solutions](https://github.com/quatico-solutions)
- **Source:** [quatico-solutions/agent-skills](https://github.com/quatico-solutions/agent-skills)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-quatico-solutions-agent-skills-handling-pull-requests
- Seller: https://agentstack.voostack.com/s/quatico-solutions
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.