Agent skill · Audited from source
Git.Backport
skill · coinbase/cdsNOASSERTION licenceAudited 14 Oct 2026 · source a03fbe3db14b
Is it safe? With care — CAUTION, grade B (89/100). We read this skill's source at commit a03fbe3db14b and found no filesystem, network or shell access and no hard-coded secrets. The audit raised 2 findings, 0 critical or high. What it does: Back-port a specific commit from master to a release branch via cherry-pick. Creates a dedicated backport branch, attempts the cherry-pick, pushes it, and opens a PR by default. Returns to the original branch when done…
Cite
Cite this page
ModelsAtlas. “Git.Backport (coinbase/cds)”. Retrieved 14 Oct 2026. https://modelsatlas.com/skills/coinbase/git-backport
Trust audit
Audit 0.4.1 · source read 14 Oct 2026
CAUTION means the audit found things worth knowing before you trust this skill. Grade B is shared by 17,406 of 18,389 audited skills.
What the source does
- FilesystemNone observedNo reads or writes in the source
- NetworkNone observedNo outbound calls in the source
- ShellNone observedNo commands run in the source
- DependenciesPinnedNothing floats
- SecretsNone foundNo keys in source
Five audit layers
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | WARN | 2 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | NA | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass.
Findings (2)
MEDIUMInventory / provenanceinv.symlink · .claude/skills/git.resolve-version-conflicts
.claude/skills/git.resolve-version-conflicts
- Why
- link not followed
- Fix
- —
MEDIUMInventory / provenanceinv.symlink · .claude/skills/skill-creator
.claude/skills/skill-creator
- Why
- link not followed
- Fix
- —
Audit 0.4.1 · source sha a03fbe3db14b · 14 Oct 2026Report an issue or request a re-scan
Provenance
Who published it, and what the verdict is pinned to
- Publishercoinbase GitHub organizationOwner of the repository this skill is read from
- Source foldercoinbase/cds/.claude/skills/git.backportThe exact folder we audited
- LicenceNOASSERTIONAs the repository states it
- Commit pinned for this verdicta03fbe3db14bA new audit runs when the source changes
- Repository statusNot archivedLast push 7 days ago
- Sandboxed runNot runSkills are read, not executed; layer L4 is skipped
What it tells the agent
Full source on GitHub ↗Its description: Back-port a specific commit from master to a release branch via cherry-pick. Creates a dedicated backport branch, attempts the cherry-pick, pushes it, and opens a PR by default. Returns to the original branch when done…
---
name: git.backport
description: Back-port a specific commit from master to a release branch via cherry-pick. Creates a dedicated backport branch, attempts the cherry-pick, pushes it, and opens a PR by default. Returns to the original branch when done (success or failure). If there are merge conflicts, diagnoses the root cause without attempting an autonomous resolution. Use when asked to "backport", "cherry-pick to release", or "port a fix to a release branch".
allowed-tools: Bash(git log:*), Bash(git show:*), Bash(git diff:*), Bash(git rev-parse:*), Bash(git apply:*), Bash(git add:*), Bash(git commit:*), Bash(git checkout:*), Bash(git branch:*), Bash(git status:*), Bash(git fetch:*), Bash(git merge-base:*), Bash(git push:*), Bash(git remote:*), Bash(git reset:*), Bash(gh pr create:*), Bash(gh pr view:*), Bash(gh api:*), Read, Grep, Glob
argument-hint: <commit-sha> <target-branch>
model: opus
---
## Your task
Back-port the commit given in `$ARGUMENTS` to a release branch using `git cherry-pick`. Your arguments are in the format `<commit-sha> <target-branch>`.
Parse `$ARGUMENTS` now: the first token is `COMMIT_SHA`, the second is `TARGET_BRANCH`.
---
## Step 0 — Record the starting branch
Before touching anything, capture where the user currently is so you can return them there at the end:
```
git rev-parse --abbrev-ref HEAD
```
Store this as `ORIGINAL_BRANCH`. You will check out this branch at the very end, regardless of whether the backport succeeds or fails.
---
## Step 1 — Validate inputs
1. **Fetch** from origin to ensure remote refs are up to date:
```
git fetch origin
```
2. Confirm `COMMIT_SHA` resolves using the remote ref (do NOT check it out locally):
```
git rev-parse --verify <COMMIT_SHA>^{commit}
```
If it still fails after fetching, stop and tell the user the SHA could not be resolved. Checkout `ORIGINAL_BRANCH` before stopping.
3. Confirm `origin/<TARGET_BRANCH>` exists on the remote:
```
git rev-parse --verify origin/<TARGET_BRANCH>
```
Always use the remote ref (`origin/<TARGET_BRANCH>`) as the source of truth — do not rely on a local checkout of the target branch. If the remote ref does not exist, stop and tell the user. Checkout `ORIGINAL_BRANCH` before stopping.
4. Check the working tree is clean (`git status --porcelain`). If it is not clean, stop and tell the user to stash or commit their in-progress work before proceeding. Do NOT checkout `ORIGINAL_BRANCH` in this case (they're already on it and have local changes).
---
## Step 2 — Summarize the commit
Show the user what they are about to cherry-pick. Use the remote ref for all inspection — never check out the source commit locally:
```
git show --stat <COMMIT_SHA>
```
Print:
- The commit subject
- The author and date
- The list of files changed with their stat line
---
## Step 3 — Derive source links
Extract the repo's GitHub URL from the remote:
```
git remote get-url origin
```
Convert SSH form (`[email protected]:org/repo.git`) or HTTPS form to a base URL: `https://github.com/org/repo`.
Build two links:
- **Commit link:** `https://github.com/org/repo/commit/<COMMIT_SHA>`
- **Original PR link:** Look for a `(#NNN)` pattern in the commit subject line. If found, build `https://github.com/org/repo/pull/NNN`. If the pattern is absent, omit the PR link and note that it could not be determined automatically.
---
## Step 4 — Create the backport branch
Derive `SHORT_SHA` = first 8 chars of `COMMIT_SHA`. Check the backport branch does not already exist:
```
git rev-parse --verify backport/<SHORT_SHA>-to-<TARGET_BRANCH>
```
If it exists locally or on origin, stop and tell the user rather than overwriting it. Checkout `ORIGINAL_BRANCH` before stopping.
Create the backport branch directly from the remote ref (no local checkout of target branch needed):
```
git checkout -b backport/<SHORT_SHA>-to-<TARGET_BRANCH> origin/<TARGET_BRANCH>
```
Tell the user the branch name.
---
## Step 5 — Apply the patch (source files only)
### 5a — Classify changed files
```
git show --name-only <COMMIT_SHA>
```
Separate all changed files into two buckets:
- **Versioning files** (always exclude): any path matching `**/package.json` or `**/CHANGELOG.md`
- **Source files** (apply these): everything else
If the commit only touches versioning files, stop and tell the user — there is nothing meaningful to backport. Return to `ORIGINAL_BRANCH` before stopping.
### 5b — Apply source-file patch
Extract and apply only the source-file diffs as a patch against the current `TARGET_BRANCH` state:
```
git show <COMMIT_SHA> -- <source-file1> <source-file2> ... | git apply --index
```
**CRITICAL: Never use `git checkout <COMMIT_SHA> -- <file>`.** That replaces the entire file with the master version, bringing in all unrelated changes that have accumulated between the two branches. Always use `git show | git apply --index` so only the diff lines from the commit are applied.
### 5c — If `git apply` succeeds — commit and proceed to Step 6
`git apply --index` stages the changes automatically. Commit:
```
git commit -m "<original commit subject> (backport to <TARGET_BRANCH>)
Backport of <commit-link> from master[, originally merged via <pr-link>].
Code-only backport — versioning and changelog applied separately.
Generated with Claude Code
Co-Authored-By: Claude <[email protected]>"
```
Then proceed to **Step 6** (versioning reminder).
### 5d — If `git apply` fails — CONFLICT PATH
The source-file patch does not apply cleanly. This usually means one of:
- `TARGET_BRANCH` has a structurally different version of the code that the patch's context lines no longer match
- The fix depends on a refactor or API change that exists in `master` but not in `TARGET_BRANCH` — making the backport potentially impossible without additional work
Do NOT attempt to modify files or force the patch. Return to `ORIGINAL_BRANCH` and report (see **Step 7**).
---
## Step 6 — Versioning reminExcerpt, first 6,000 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.
Install
Pinned to the audited commit a03fbe3
git clone https://github.com/coinbase/cds git -C cds checkout a03fbe3db14b
The author documents no install command, so this uses the repository directly. Our verdict covers commit a03fbe3db14b only.
Works in which agents?
What its own text says, not a test
| Agent | Status | More |
|---|---|---|
| Claude Code | Mentioned in its text, not tested | Skills for Claude Code · About Claude Code |
Audit history
Every audit, every source change
- !CAUTION B 89 / 100
first audit · source
a03fbe3db14b
README badge
For maintainers · shows the latest audit
[](https://modelsatlas.com/skills/coinbase/git-backport/)
The badge shows our verdict and grade for this skill, and links back to this page. It changes when the audit does.
Similar skills
mattpocock/skills
Implement a piece of work based on a spec or set of tickets.
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
mattpocock/skills
Pursue a long-running goal in a single session by co-ordinating subagents.
Add this badge to your README
[](https://modelsatlas.com/skills/coinbase/git-backport/)
<a href="https://modelsatlas.com/skills/coinbase/git-backport/"><img src="https://modelsatlas.com/skills/coinbase/git-backport/badge.svg" alt="ModelsAtlas: CAUTION B"></a>
Questions about Git.Backport
What does the Git.Backport skill do?
Is Git.Backport safe to install?
What can Git.Backport access on my machine?
Which assistants does Git.Backport work with?
How current is this page?
Sources
- github.com/coinbase/cds/tree/master/.claude/skills/git.backport — the audited source at commit a03fbe3db14b and every finding aboveObserved · 14 Oct 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- What does the Git.Backport skill do?
- Is Git.Backport safe to install?
- What can Git.Backport access on my machine?