prepare-fabric-pr
Prepare or update a Fabric pull request by proving the changeset-or-skip decision, validation evidence, DCO sign-off, and public-safe PR metadata. Use before the first push, after later revisions, or
SKILL.md.agents/skills/prepare-fabric-pr/SKILL.md
GitHubPrepare a Fabric pull request
Produce a reviewable PR whose release decision is explicit and whose public metadata contains no private identifiers.
Before pushing
- Read the root
AGENTS.mdsections on public repository hygiene and changesets, pluspackages/fabric-app/README.md. - Fetch the target branch and inspect the complete diff from its merge base. Preserve unrelated working-tree changes.
- Classify the release impact:
- Production-shipping or user-visible behavior requires a changeset,
normally
"fabric-app": patch. - Docs-only, CI-only, Markdown-only, or pure changeset changes are normally
eligible for
skip-changeset. - A different change may skip only when it has no deployable or user-visible effect; state that reason explicitly.
- Production-shipping or user-visible behavior requires a changeset,
normally
- For an impacting change, run Changesets with
--outputagainst the target branch and inspect the JSON. Require.releases | length > 0; exit code zero with an empty release list is a failed release decision. - For a skip-eligible change, do not create a meaningless changeset. Record
the no-impact reason for the PR and plan to apply
skip-changesetonce the PR exists. - Run validation proportional to the diff and record exact commands and results. A skipped, unavailable, timed-out, or sandbox-blocked check is unverified, not passing.
- Inspect all public text—branch, commits, changeset headline/body, and PR draft—for real organizations, people, deployments, hostnames, internal URLs, or private ticket prose. Replace them with synthetic descriptions.
- Commit only when authorized. Use
git commit -s; never add AI attribution.
Create or update the PR
Creating or updating a PR is an external mutation. Do it only when the user's request authorizes it.
- Use the repository PR template.
- Explain behavior, release decision, and verification without claiming checks that did not run.
- After creating a skip-eligible PR, apply
skip-changesetimmediately and verify the stored label. - After every later push, repeat the diff review, release decision, and Changesets JSON check. A previous result belongs to the old head.
Stop after the PR is created or updated unless the user explicitly authorized landing. PR creation alone never authorizes relay, merge, or deployment.