How do I install the Qts Pr Review skill?

Run npx skillmds@latest add tetherto/qts-pr-review in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Qts Pr Review safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Qts Pr Review?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Qts Pr Review free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Qts Pr Review?

tetherto (@tetherto) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Qts Pr Review by tetherto — Agent Skill

Name: Qts Pr Review
Author: tetherto

Qts Pr Review

Reviews qvac-test-suite pull requests and diffs for package-surface risk, CLI/versioning behavior, dist hygiene, workflow parity, docs accuracy, and mobile template/runtime integrity. Use when reviewing a PR, a branch diff, or doing a senior engineer pass on framework changes.

tetherto 02f02a9 2.0 KB Updated Sep 17, 2026

File contents

QTS PR Review

Use this skill for qvac-test-suite only.

Review flow

Gather context from a PR URL or the current branch diff.
Read the touched files plus adjacent package metadata, README, workflow files, and .github/pull_request_template.md when the diff affects public behavior.
Review in this order:
- correctness and regression risk
- publish/package surface (exports, package metadata, install assumptions)
- CLI and config contract
- build reproducibility and framework/dist hygiene
- workflow parity versus intended behavior
- mobile template/runtime integrity
- documentation accuracy for package consumers
Validate the PR title/body against .cursor/rules/framework/commit-and-pr-format.mdc and .github/pull_request_template.md when they are relevant to the review.
Flag hidden breaking changes such as renamed commands, changed config keys, changed publish semantics, moved entrypoints, or docs that promise behavior the package does not implement.

Output format

Findings first, ordered by severity, with concrete file references.
Then open questions or assumptions.
Then a short summary of what changed well.

Review heuristics

Treat workflow diffs conservatively; accidental trigger, token, or registry changes are high risk.
A docs-only change is still incorrect if it documents behavior that does not exist.
A build change is suspect if it can leave stale artifacts or alter published contents unexpectedly.
A PR description is incomplete if it skips relevant template sections such as package surface changes, workflow or publish changes, docs changes, or migration notes.
Do not assume helper scripts, PR comment bots, team metadata, or downstream repo automation exist.

---name: qts-pr-reviewdescription: Reviews qvac-test-suite pull requests and diffs for package-surface risk, CLI/versioning behavior, dist hygiene, workflow parity, docs accuracy, and mobile template/runtime integrity. Use when reviewing a PR, a branch diff, or doing a senior engineer pass on framework changes.---# QTS PR ReviewUse this skill for `qvac-test-suite` only.## Review flow1. Gather context from a PR URL or the current branch diff.2. Read the touched files plus adjacent package metadata, README, workflow files, and `.github/pull_request_template.md` when the diff affects public behavior.3. Review in this order: - correctness and regression risk - publish/package surface (`exports`, package metadata, install assumptions) - CLI and config contract - build reproducibility and `framework/dist` hygiene - workflow parity versus intended behavior - mobile template/runtime integrity - documentation accuracy for package consumers4. Validate the PR title/body against `.cursor/rules/framework/commit-and-pr-format.mdc` and `.github/pull_request_template.md` when they are relevant to the review.5. Flag hidden breaking changes such as renamed commands, changed config keys, changed publish semantics, moved entrypoints, or docs that promise behavior the package does not implement.## Output format- Findings first, ordered by severity, with concrete file references.- Then open questions or assumptions.- Then a short summary of what changed well.## Review heuristics- Treat workflow diffs conservatively; accidental trigger, token, or registry changes are high risk.- A docs-only change is still incorrect if it documents behavior that does not exist.- A build change is suspect if it can leave stale artifacts or alter published contents unexpectedly.- A PR description is incomplete if it skips relevant template sections such as package surface changes, workflow or publish changes, docs changes, or migration notes.- Do not assume helper scripts, PR comment bots, team metadata, or downstream repo automation exist.

Frequently asked questions