What is feature-branch-pr?

A workflow guide for making a change in the TT-Studio repository and opening a pull request, which is a proposed change for team review. It requires feature branches to start from dev and target dev.

Use it to create a feature branch, make and verify a small change, check health endpoints, prepare a human-written commit, and open a pull request.

It keeps changes isolated, limits the diff to the requested work, and verifies the running application before code is pushed. It also protects the production branch and other developers' branches.

How tenstorrent/tt-studio configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to tenstorrent/tt-studio. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/tenstorrent/tt-studio/main/.claude/skills/feature-branch-pr/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/tenstorrent/tt-studio

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/tenstorrent/tt-studio/feature-branch-pr/github.svg)](https://agentmods.dev/skills/tenstorrent/tt-studio/feature-branch-pr)

Your own site

<a href="https://agentmods.dev/skills/tenstorrent/tt-studio/feature-branch-pr"><img src="https://agentmods.dev/badge/skills/tenstorrent/tt-studio/feature-branch-pr/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/tenstorrent/tt-studio/feature-branch-pr"><img src="https://agentmods.dev/badge/skills/tenstorrent/tt-studio/feature-branch-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 126 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,980 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 1 finding, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

high Tool Misuse · line 24
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00126	$0.01980
Opus 5.5	$0.00050	$0.00792
Sonnet 5.5	$0.00025	$0.00396
Haiku 4.5	$0.00013	$0.00198

Measured 2mo ago against content hash 24f8423732fa, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

feature-branch-pr scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

| Backend (Django) | `curl -f http://localhost:8000/up/` → 200 |

.claude/skills/feature-branch-pr/SKILL.md · 212 lines

How it starts

The opening of the file, as written. The whole thing — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.

TT-Studio Feature Branch + PR Workflow

Follow this when asked to make a change and/or open a PR in tt-studio. The goal is a small, verified, professional change that touches nothing it shouldn't.

Guardrails (always true)

Base everything on dev. Features branch off dev and PRs target dev. main is production/tagged code only — never branch a feature off it or open a feature PR against it.
Never commit on dev or main directly, and never git push --force (or --force-with-lease) to a shared branch.
Leave other branches alone. No checkout-and-edit of unrelated branches, no rebasing or deleting branches you didn't create for this task.
No AI attribution anywhere. Commit messages, PR titles/descriptions, and review comments must read as a human wrote them. Do not add Co-Authored-By trailers for AI tools and do not mention "Claude", "Claude Code", "Cursor", "AI assistant", or similar.

Workflow checklist

Copy this and tick as you go:

- [ ] 1. Identify the username
- [ ] 2. Branch off dev
- [ ] 3. Make the minimal change
- [ ] 4. Verify (endpoints / tests)
- [ ] 5. Clean up instrumentation
- [ ] 6. Stage only intended files
- [ ] 7. Commit (human message)
- [ ] 8. Push + open PR against dev
- [ ] 9. Return to the original branch

1. Identify the username

Derive the branch prefix from git config:

git config user.name; git config user.email

Use the lowercased first name / email local-part (e.g. johnsingh@... → john). If it's ambiguous, ask the user which prefix to use. This repo's convention is <username>/<feature> (e.g. john/ttft-fix).

2. Branch off dev

Always start from the latest dev, and remember where you came from:

ORIG=$(git branch --show-current)        # so you can return in step 9
git fetch origin
git checkout -b <username>/<short-kebab-feature> origin/dev

Pick a short, descriptive kebab-case feature name (reset-view-fix, p100-support). Confirm git status is clean before editing.

Read the full file on GitHub · 212 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 212 lines · 126 tokens per session scan A 24f8423732fa

Subscribe to this mod's changes

feature-branch-pr is a skill published in the GitHub repository tenstorrent/tt-studio (52 stars, last pushed yesterday), licensed Apache-2.0. It adds 126 tokens to every session and 1,980 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Git and workflow React accelerator ai-agents backend-service chat-application ui-components

feature-branch-pr next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
feature-branch-prtenstorrent/tt-studio	Skill	52	yesterday	Apache-2.0	A	126	Claude Code
git-safetytamagui/tamagui	Skill	14k	today	MIT	A	0	Claude Code
release-safetytamagui/tamagui	Skill	14k	today	MIT	A	0	Claude Code
compiler-commitreact/react	Skill	252k	yesterday	MIT	A	42	Claude Code
merge-seedkriasoft/react-starter-kit	Skill	24k	4d ago	MIT	A	49	Claude Code, Codex
tamagui-upgrade-v3tamagui/tamagui	Skill	14k	today	MIT	A	120	Claude Code, Codex
tamaguitamagui/tamagui	Skill	14k	today	MIT	A	44	Claude Code, Codex

tt-studio: Skill for Claude Code