winappCli: Skill for Claude Code

PR lifecycle: Prepare, Present, Finish

Use this for work on this repository, not as a shipped winapp plugin skill. The outcome is a clear PR and an honest readiness state, not a merge.

Authority and repository policy

• Establish the requested scope first. "Draft a PR body" returns text only; "review this PR" returns findings only. Neither authorizes changing code, pushing, posting, requesting reviews, or changing labels. A request to create or take a PR through readiness authorizes the necessary in-scope work, not unrelated changes or merging. Confirm any additional authority you need.
• Read AGENTS.md, the PR template, affected workflow definitions in .github\workflows, and applicable .pipelines instructions. Live branch protection/rulesets are the source of truth for required checks and approvals; do not freeze their names or counts here.
• pr-review owns independent, practical review of correctness, compatibility and performance. Use it for a full feature review; keep a narrow docs/fix review proportional rather than copying its entire orchestration. spec-review is for unresolved design questions before implementation, not another mandatory post-code ceremony.
• Fix findings in the existing PR by default. Create a follow-up fix PR only when the user asks. Preserve the review-only default of pr-review.
• Use the host's create_pull_request, update_pull_request, and reply_and_resolve_review_thread tools when available; obey their contracts rather than substituting shell commands. Other GitHub reads/actions may use gh. Never merge, enable auto-merge, bypass protection, dismiss a human changes-request review, or manufacture an approval.

Prepare

1. Identify the real comparison. Read the live PR (if it exists): repository, number, state, head repository/ref/SHA, base ref/SHA, draft state, checks, reviews and mergeability. Inspect local status, tracking refs and the full diff including relevant untracked files. Fetch the actual head and base; do not assume the local branch or origin/main is current. Record immutable head/base SHAs for the assessment.
2. Preserve other work. Do not stage unrelated files, delete scratch files, discard a dirty tree, or overwrite collaborator commits. If the remote head differs from your expected head, inspect it before continuing; stop and coordinate overlapping edits. Prefer a normal non-rewriting update. Rewrite only with permission and an explicit expected-SHA lease (--force-with-lease=<ref>:<expected-sha>); a failed lease means re-inspect, not force harder.
3. Respect stacks. Review against the actual parent branch, not the entire stack against main. Use the available native stack skill/tool to synchronize parents and propagate updates. Check the parent and ultimate main as appropriate to repository policy; do not blindly retarget to main or merge main into a child. For an ordinary PR, incorporate required base updates safely and resolve conflicts before assessing readiness.
4. Review and repair. Get independent review of the actual final diff. Review concrete user paths, supported released compatibility contracts and meaningful performance risks, not speculative edge cases. Fix only findings that meet "What blocks a PR" in AGENTS.md, with regression tests where applicable, and handle everything else as "Addressing review feedback" describes (one-line decline, scope guard, at most two review-and-fix rounds). Explain false positives with evidence; do not silently mark them addressed. A prior review remains useful only if its SHA is recorded and every subsequent delta is reviewed, or range-equivalence is demonstrated. A rebase alone is not proof of equivalence.
5. Validate the changed behavior. Run the smallest relevant existing tests, builds and user-path checks required by repository instructions. Update only affected documentation. Record exact commands and observed outcomes, including limitations. For contributor Markdown-only changes, check frontmatter, links/paths and Markdown plus applicable docs tooling; no full NativeAOT build is needed unless that tooling requires it.