Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Write, refactor, or review tests in Personal AI Router using focused cases, descriptive subtests, explicit error handling, and structured assertions.
Install Pair Test Style
$ npx skills add NVIDIA/Personal-AI-Router --skill pair-test-style -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install NVIDIA/Personal-AI-Router pair-test-style --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/NVIDIA/Personal-AI-Router.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/pair-test-style .claude/skills/pair-test-style && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "pair-test-style" agent skill from https://github.com/NVIDIA/Personal-AI-Router/tree/develop/.agents/skills/pair-test-style into .claude/skills/pair-test-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pair-test-style", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/NVIDIA/Personal-AI-Router/tree/develop/.agents/skills/pair-test-styleType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add NVIDIA/Personal-AI-Router --skill pair-test-style -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install NVIDIA/Personal-AI-Router pair-test-style --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/Personal-AI-Router.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/pair-test-style .agents/skills/pair-test-style && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pair-test-style" agent skill from https://github.com/NVIDIA/Personal-AI-Router/tree/develop/.agents/skills/pair-test-style into .agents/skills/pair-test-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pair-test-style", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add NVIDIA/Personal-AI-Router --skill pair-test-style -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install NVIDIA/Personal-AI-Router pair-test-style --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/Personal-AI-Router.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/pair-test-style .cursor/skills/pair-test-style && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "pair-test-style" agent skill from https://github.com/NVIDIA/Personal-AI-Router/tree/develop/.agents/skills/pair-test-style into .cursor/skills/pair-test-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pair-test-style", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/NVIDIA/Personal-AI-Router.git --path .agents/skills/pair-test-style--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add NVIDIA/Personal-AI-Router --skill pair-test-style -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install NVIDIA/Personal-AI-Router pair-test-style --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/Personal-AI-Router.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/pair-test-style .gemini/skills/pair-test-style && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "pair-test-style" agent skill from https://github.com/NVIDIA/Personal-AI-Router/tree/develop/.agents/skills/pair-test-style into .gemini/skills/pair-test-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pair-test-style", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install NVIDIA/Personal-AI-Router pair-test-styleInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add NVIDIA/Personal-AI-Router --skill pair-test-style -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/NVIDIA/Personal-AI-Router.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/pair-test-style .github/skills/pair-test-style && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "pair-test-style" agent skill from https://github.com/NVIDIA/Personal-AI-Router/tree/develop/.agents/skills/pair-test-style into .github/skills/pair-test-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pair-test-style", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add NVIDIA/Personal-AI-Router --skill pair-test-style -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install NVIDIA/Personal-AI-Router pair-test-style --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/Personal-AI-Router.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/pair-test-style .opencode/skills/pair-test-style && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "pair-test-style" agent skill from https://github.com/NVIDIA/Personal-AI-Router/tree/develop/.agents/skills/pair-test-style into .opencode/skills/pair-test-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pair-test-style", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
pair-test-style- GitHub stars
- 1.6k
- Token cost
- ~1k tokens
- SKILL.md length
- 517 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Write, refactor, or review tests in Personal AI Router using focused cases, descriptive subtests, explicit error handling, and structured assertions.
- Changing Go service
- SKILL.md covers Focus each test, Share setup without hiding the…, Check errors and structured… and Fit the existing test suite
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Apply to the tests in scope rather than starting a repository-wide cleanup
What it does
Pair Test Style is an agent skill from NVIDIA/Personal-AI-Router, published by the product's own GitHub organization. Write, refactor, or review tests in Personal AI Router using focused cases, descriptive subtests, explicit error handling, and structured assertions. Use when adding or changing Go service or desktop tests; apply to the tests in scope rather than starting a repository-wide cleanup.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. The repository describes itself as: Router that virtually distributes inference across connected devices in the home. The licence is Apache-2.0.
When your agent uses it
- Changing Go service
- Apply to the tests in scope rather than starting a repository-wide cleanup
Example prompts
- “/pair-test-style”
What it can do on your machine
Read from SKILL.md and the folder at commit 4d1892b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Pair Test Style loads about 1k tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 517 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from NVIDIA/Personal-AI-Router at commit 4d1892b, republished under its Apache-2.0 licence (© NVIDIA). 517 words, ~1,005 tokens.
Download SKILL.mdSave it as
.claude/skills/pair-test-style/SKILL.md (or your agent's skills folder).- name
- pair-test-style
- description
- Write, refactor, or review tests in Personal AI Router using focused cases, descriptive subtests, explicit error handling, and structured assertions. Use when adding or changing Go service or desktop tests; apply to the tests in scope rather than starting a repository-wide cleanup.
<!--
SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
SPDX-License-Identifier: Apache-2.0
-->PAIR test style
Keep each test's setup, action, and expected behavior easy to follow. These conventions apply to contributors and coding agents working on repository tests. They guide test structure; they do not require new coverage or unrelated rewrites.
Focus each test
- Give each top-level test one behavior to prove. Split long tests that combine validation, persistence, restart, and recovery into independently readable tests.
- Keep a table-driven test dedicated to its related cases. Put an unrelated one-off assertion or scenario in its own test function.
- Prefer explicit cases over nested loops and boolean mode matrices when the combinations obscure what is being checked. Keep a matrix when the combinations themselves are the behavior under test and the names explain them.
- Name subtests after their scenario or outcome:
process mode,command mode,rejects bind override, orpreserves response body, rather thantrue,false, or an index.
Share setup without hiding the cases
For Go cases with the same setup and assertions, prefer a local helper closure
that captures shared setup and calls t.Run. List explicit, named calls below
it. A signature such as test := func(name, input, wantError string) often makes
cases easier to read than a large table with mode-dependent branches.
Use ordinary tables when they are clearer. Separate acceptance and rejection helpers when that removes branching and makes expected outcomes explicit. Keep mutable state fresh per case so cases do not depend on execution order.
Mark Go assertion and setup helpers with t.Helper(). Pass the subtest's
*testing.T to helpers that report failures so errors belong to the right case.
Keep helpers local unless reuse across tests justifies a shared fixture.
Show full SKILL.md (247 more words)Show less
Check errors and structured results
- Check setup, file I/O, encoding, decoding, and operation errors. Do not discard an error just because the fixture is expected to be valid. Fail at the operation that failed, with enough context to diagnose it.
- Prefer explicit
t.Fatalfchecks or a small test-only must-succeed helper that fails immediately. AMusthelper is optional; avoid adding an abstraction when an explicit check is clearer. - Decode JSON and other structured output, then assert the relevant fields.
Avoid
strings.Containsas evidence that a serialized response or persisted configuration has the correct values. Check parsing errors before fields. - Use substring assertions when the contract is actually unstructured text, such as a diagnostic, and the selected text is what the test intends to verify.
- Use named constants such as
http.StatusBadGatewayandhttp.MethodPutinstead of magic protocol values. Format multiline fixtures and header maps readably; rungofmton changed Go tests.
Fit the existing test suite
For desktop tests, carry over the same focus, naming, error handling, and structured assertions using Vitest's existing patterns. Follow desktop test conventions for typed mocks, module-boundary fakes, network isolation, and temporary-directory cleanup. Do not introduce a new framework or production-only test hooks for this style.
Run the relevant existing tests and required repository checks. In review, verify that each changed test has a clear failure condition, names the behavior it proves, checks its setup errors, and can be understood without tracing an unrelated scenario. State any verification that could not be run.
© NVIDIA, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/pair-test-style of NVIDIA/Personal-AI-Router.
Open the folder on GitHubat commit 4d1892b
Compare with similar skills
Pair Test Style next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Pair Test Style this skillNVIDIA/Personal-AI-Router | 1.6k | — | ~1k | Automated safety check: Pass | Apache-2.0 | |
| Finishing a Development Branchobra/superpowers | 296k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Typescript Advanced Typesrolling-scopes/rsschool-app | 10k | 24 repos | ~4.2k | Automated safety check: Pass | MPL-2.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Greplooponyx-dot-app/onyx | 32k | 4 repos | ~3.3k | Automated safety check: Pass | MIT |
Similar skills
Typescript Advanced Types
rolling-scopes/rsschool-app
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
Guidelines
akash-network/node
Behavioral guidelines to reduce common LLM coding mistakes. An agent skill from akash-network/node.
More from NVIDIA/Personal-AI-Router
- Official
Pair GitHub PR
NVIDIA/Personal-AI-Router
Fills GitHub pull request descriptions with the required PAIR pair-release-intent:v1 block so the release-intent check passes.
- Official
Kaizen UI
NVIDIA/Personal-AI-Router
Kaizen UI (KUI) component library and design-pattern advisor for NVIDIA applications.
- Official
Sync Backend
NVIDIA/Personal-AI-Router
Refresh services/ from upstream, resolve JSON-RPC drift, update contract docs, rebuild cli-bin, and verify.
Related
Categories
Questions about Pair Test Style
What does Pair Test Style do?
Write, refactor, or review tests in Personal AI Router using focused cases, descriptive subtests, explicit error handling, and structured assertions. Pair Test Style is an agent skill from NVIDIA/Personal-AI-Router, published by the product's own GitHub organization. Write, refactor, or review tests in Personal AI Router using focused cases, descriptive subtests, explicit error handling, and structured assertions.
When should I use Pair Test Style?
Pair Test Style fits situations like: changing Go service; apply to the tests in scope rather than starting a repository-wide cleanup.
How do I install Pair Test Style in Claude Code?
Run `npx skills add NVIDIA/Personal-AI-Router --skill pair-test-style -a claude-code`. Or copy the skill folder (.agents/skills/pair-test-style in NVIDIA/Personal-AI-Router) into .claude/skills/pair-test-style in your project. Claude Code loads it when a task matches its description.
How do I install Pair Test Style in Codex?
Run `npx skills add NVIDIA/Personal-AI-Router --skill pair-test-style -a codex`. Or copy the skill folder (.agents/skills/pair-test-style in NVIDIA/Personal-AI-Router) into .agents/skills/pair-test-style in your project. Codex loads it when a task matches its description.
Can I use Pair Test Style in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NVIDIA/Personal-AI-Router --skill pair-test-style -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pair-test-style, .gemini/skills/pair-test-style, .github/skills/pair-test-style and .opencode/skills/pair-test-style in your project.
What does Pair Test Style need to run?
SKILL.md names no scripts, command-line tools or credentials: Pair Test Style is instructions for the agent only.
Does Pair Test Style access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Pair Test Style safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Pair Test Style use?
Pair Test Style is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Pair Test Style use?
About 1k tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Pair Test Style?
Skills that share tags, products or a category with Pair Test Style: Finishing a Development Branch (obra/superpowers, 296k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars) and Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Pair Test Style?
NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/Personal-AI-Router, which has 1,566 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 6, 2026.
Source: NVIDIA/Personal-AI-Router on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.