How do I install the Tsz CI Pr skill?

Run npx skillmds@latest add tsz-org/tsz-ci-pr 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 Tsz CI Pr 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 Tsz CI Pr?

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 Tsz CI Pr free to use?

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

Who published Tsz CI Pr?

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

Tsz CI Pr by tsz-org — Agent Skill

Name: Tsz CI Pr
Author: tsz-org

Tsz CI Pr

Drive TSZ GitHub PRs through review, CI, and the merge queue. Use when checking PR status, debugging failing GitHub Actions, deciding whether a PR is WIP, marking draft PRs ready, enqueueing or verifying the queue, landing a PR, or interpreting TSZ CI gates.

tsz-org 72c9526 2.5 KB Updated Sep 17, 2026

File contents

TSZ CI And PR

Use for PR checks, CI triage, ready state, queue evidence, and landing. Use tsz-pr-coordination for PR body/label contract.

Rules

Use gh; sign substantive comments with a provenance line (e.g. Machine: studio or Provenance: studio / claude-code / claude-opus-4-8 / high).
The PR author lands their own PR; never idle-wait on CI between pushes.
Never merge draft/WIP PRs (draft, WIP, [WIP], or body/branch says WIP).
Every open PR runs the full CI suite (draft or not); path-based content skips apply only to docs-only or tooling-only diffs.
Ready PRs land through GitHub's native merge queue.
If asked to land, verify state: MERGED; an armed queue request alone is not enough.

Inspect

gh pr view <pr> --json state,isDraft,mergeStateStatus,mergeable,autoMergeRequest,mergedAt,labels,title,url,headRefName,headRefOid
gh pr checks <pr> --json name,state,bucket,link,completedAt
gh run view <run-id> --log-failed
gh run view <run-id> --job <job-id> --log

Use gh pr checks <pr> --watch --interval 20 only when the result is needed now.

Landing

Confirm not WIP and head SHA matches inspected checks.
Fix failures in-PR; comment with root cause and verification.
Mark ready only after implementation and verification: gh pr ready <pr>.
Queue with GitHub's native merge queue only when exact-head PR-head checks such as CI Summary pass and policy permits: gh pr merge <pr> --match-head-commit <sha>. Do not pass --auto; with branch protection and passing checks, current gh adds the PR to the native merge queue directly.
Inspect merge_group CI runs if queue validation stalls.
Verify final merge: gh pr view <pr> --json state,mergedAt,mergedBy,url.

Failure Hints

CI Summary: umbrella PR-head status.
merge_group CI: native queued-merge summary validation.
conformance-aggregate: accepted-regression drift can fail aggregate even when shards pass.
unit-cloudbuild: often exposes memory, linking, or architecture guard failures.
Docs-only and bench-shell-only paths short-circuit most jobs.

Comment shape: provenance line, root cause, files changed, verification/CI URL, remaining risk.

---name: tsz-ci-prdescription: Drive TSZ GitHub PRs through review, CI, and the merge queue. Use when checking PR status, debugging failing GitHub Actions, deciding whether a PR is WIP, marking draft PRs ready, enqueueing or verifying the queue, landing a PR, or interpreting TSZ CI gates.---# TSZ CI And PRUse for PR checks, CI triage, ready state, queue evidence, and landing. Use`tsz-pr-coordination` for PR body/label contract.## Rules- Use `gh`; sign substantive comments with a provenance line (e.g. `Machine: studio` or `Provenance: studio / claude-code / claude-opus-4-8 / high`).- The PR author lands their own PR; never idle-wait on CI between pushes.- Never merge draft/WIP PRs (`draft`, `WIP`, `[WIP]`, or body/branch says WIP).- Every open PR runs the full CI suite (draft or not); path-based content skips apply only to docs-only or tooling-only diffs.- Ready PRs land through GitHub's native merge queue.- If asked to land, verify `state: MERGED`; an armed queue request alone is not enough.## Inspect```bashgh pr view <pr> --json state,isDraft,mergeStateStatus,mergeable,autoMergeRequest,mergedAt,labels,title,url,headRefName,headRefOidgh pr checks <pr> --json name,state,bucket,link,completedAtgh run view <run-id> --log-failedgh run view <run-id> --job <job-id> --log```Use `gh pr checks <pr> --watch --interval 20` only when the result is needednow.## Landing1. Confirm not WIP and head SHA matches inspected checks.2. Fix failures in-PR; comment with root cause and verification.3. Mark ready only after implementation and verification: `gh pr ready <pr>`.4. Queue with GitHub's native merge queue only when exact-head PR-head checks such as `CI Summary` pass and policy permits: `gh pr merge <pr> --match-head-commit <sha>`. Do not pass `--auto`; with branch protection and passing checks, current `gh` adds the PR to the native merge queue directly.5. Inspect `merge_group` CI runs if queue validation stalls.6. Verify final merge: `gh pr view <pr> --json state,mergedAt,mergedBy,url`.## Failure Hints- `CI Summary`: umbrella PR-head status.- `merge_group` CI: native queued-merge summary validation.- `conformance-aggregate`: accepted-regression drift can fail aggregate even when shards pass.- `unit-cloudbuild`: often exposes memory, linking, or architecture guard failures.- Docs-only and bench-shell-only paths short-circuit most jobs.Comment shape: provenance line, root cause, files changed, verification/CIURL, remaining risk.

Frequently asked questions