Skip to content
Skills Library
Programming · Tool integration

edit-teammate-code

/edit-teammate-code

Propose changes to code a teammate wrote, without touching their branch - comment on their PR, or branch off their branch and open a PR into it for them to approve, or start a fresh branch for code already merged. Use when someone says "edit Sam's code", "fix their branch", "change something someone else wrote", or tries to push to a teammate's branch.

Licence
MIT
Last repository change
11.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 11.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Propose changes to code a teammate wrote, without touching their branch - comment on their PR, or branch off their branch and open a PR into it for them to approve, or start a fresh branch for code already merged. Use when someone says "edit Sam's code", "fix their branch", "change something someone else wrote", or tries to push to a teammate's branch.

Triggers from the description

edit Samfix their branchchange something someone else wrote
Original author description

Propose changes to code a teammate wrote, without touching their branch - comment on their PR, or branch off their branch and open a PR into it for them to approve, or start a fresh branch for code already merged. Use when someone says "edit Sam's code", "fix their branch", "change something someone else wrote", or tries to push to a teammate's branch.

How it works

  1. 0. Context
  2. A. Small suggestion on an open PR
  3. B. Bigger change to a teammate's open PR
  4. C. Code that's already in the default branch
Original SKILL.md headings · 42 lines, 337 words
SKILL.md preview
---
name: edit-teammate-code
description: Propose changes to code a teammate wrote, without touching their branch - comment on their PR, or branch off their branch and open a PR into it for them to approve, or start a fresh branch for code already merged. Use when someone says "edit Sam's code", "fix their branch", "change something someone else wrote", or tries to push to a teammate's branch.
---

# Edit someone else's code

Guide: if the repo has a CONTRIBUTING.md, the matching section is "I want to edit someone else's code". The steps below work without it.

**Never push commits directly to a teammate's branch.** Propose changes; the owner decides.

## 0. Context

- **In a GitHub repo with `gh` logged in?** `gh repo view --json nameWithOwner`. If it fails, use the `setup` skill.
- **Default branch** (`<default>`): `gh repo view --json defaultBranchRef -q .defaultBranchRef.name`.
- **Your name:** first name from `git config user.name`, lowercased; ask if empty.
- **Which code:** find their PR with `gh pr list` (ask which, if unclear). Note its number, author, and branch (`headRefName`, called `<their-branch>` below). If there's no open PR, the code is probably already in `<default>`: that's case C.

Then pick the case; ask if unclear.

## A. Small suggestion on an open PR

Don't edit. Use the `review-pr` skill to leave a comment.

## B. Bigger change to a teammate's open PR

1. **Save your own work first:** check `git status`; commit with `save-and-push` or ask about stashing.
2. **Branch off theirs:**
   ```bash
   gh pr checkout <number>
   git pull
   git checkout -b <name>/<their-branch>-<what-you-changed>
   ```
   Keep the name short, e.g. `alex/sam-signup-form-copy-edits`.
3. **Make the edits**, then commit and push with the `save-and-push` skill (it pushes your new branch, not theirs).
4. **Open a PR into their branch**, not `<default>`:
   ```bash
   gh pr create --base <their-branch> --fill
   ```
   Add a line to the PR body saying it's a suggested change to PR #<number>.
5. **Hand it to them.** Give the user the link to send to the author. The author reviews and merges it into their branch (`review-pr`, then `open-pr`'s merge steps). If the author's PR merges into `<default>` first, GitHub automatically retargets this PR to `<default>`.

## C. Code that's already in the default branch

Treat it as a new task: `start-work`, make the change, `save-and-push`, `open-pr`. Suggest asking the original author to review (`git log --format='%an' -- <file> | head -1` shows who last touched it).

Versions

The database has no other skills named edit-teammate-code.

Database snapshot: 13.11.2026 · package version c76bba899987 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100open-pr
    Get a finished branch merged - open a pull request into the default branch (or into a teammate's branch), and after a teammate reviews it, merge it and clean up. Use when someone says "open a PR", "get this into main", "merge my branch", or "it's ready".
  • 100update-branch
    Bring your branch up to date with the latest default branch (or the teammate branch it's based on) by merging it in. Use when someone says "my branch is out of date", "get the latest changes", "sync with main", or a PR says it's behind or has conflicts.
  • 100feature-branch
    Enforce the Atlassian feature-branch workflow for GitHub and GitLab repos: branch off the default branch, work, open a PR/MR, and delete the local + remote branch once merged. Use when the user says 'start a feature', 'fix a bug', 'work on X', 'open a PR', 'open an MR', 'merge…
  • 100branch
    Create a working branch from what you are about to work on. Use for /branch, or any request to start a new branch before making changes.
  • 100pr-review
    Use when the user asks to review a branch or PR against the base, or asks whether it can be approved or merged ("review this branch", "can I approve this?", "can this be merged?"), including a re-review after new commits. Also for a self-review of the user's own branch before…
  • 86branch
    Create a working branch from what you are about to work on. Use for /branch, or any request to start a new branch before making changes.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.