본문으로 건너뛰기
cccskills
무료GitHub에 공개

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 when asked to create or update a PR. Do not use to review an unrelated PR or authorize relay.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(1)

  • SKILL.md2.6 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Prepare a Fabric pull request

Produce a reviewable PR whose release decision is explicit and whose public metadata contains no private identifiers.

Before pushing

  1. Read the root AGENTS.md sections on public repository hygiene and changesets, plus packages/fabric-app/README.md.
  2. Fetch the target branch and inspect the complete diff from its merge base. Preserve unrelated working-tree changes.
  3. 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.
  4. For an impacting change, run Changesets with --output against the target branch and inspect the JSON. Require .releases | length > 0; exit code zero with an empty release list is a failed release decision.
  5. For a skip-eligible change, do not create a meaningless changeset. Record the no-impact reason for the PR and plan to apply skip-changeset once the PR exists.
  6. 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.
  7. 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.
  8. 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-changeset immediately 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.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Build accessible web applications following WCAG 2.1/2.2 guidelines with proper semantic HTML, ARIA attributes, keyboard navigation, screen reader support, and inclusive design. Use when implementing ARIA labels and roles, ensuring keyboard navigation, supporting screen readers, providing text alternatives for images, managing focus, creating accessible forms, building inclusive UI components, testing with accessibility tools, meeting WCAG compliance levels, or designing for users with disabilities.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Fabric-Pro/fabric-oss32026년 10월 22일 업데이트

Guide for adding new OAuth-based integrations to Fabric. Use when implementing OAuth providers like Microsoft Teams, GitHub, Google Drive, Slack, or similar services that need OAuth 2.0 authentication for user data access.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Fabric-Pro/fabric-oss32026년 10월 22일 업데이트

Design clean, scalable, and maintainable REST and GraphQL APIs following industry best practices. Use when designing public or internal APIs, planning endpoint structures, defining request/response contracts, establishing versioning strategies, implementing authentication patterns, designing data models, creating API documentation, ensuring consistent error handling, optimizing for performance, or establishing service contracts between microservices.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Fabric-Pro/fabric-oss32026년 10월 22일 업데이트

Create professional, dark-themed architecture diagrams as standalone HTML files with SVG graphics. Use when the user asks for system architecture diagrams, infrastructure diagrams, cloud architecture visualizations, security diagrams, network topology diagrams, or any technical diagram showing system components and their relationships.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Fabric-Pro/fabric-oss32026년 10월 22일 업데이트

Create interactive, self-contained artifacts like mini-apps, visualizations, calculators, and tools that can be embedded or used standalone. Use when building interactive calculators, creating data visualizations, making mini web apps, building embeddable widgets, creating interactive demos, making tools for specific tasks, or generating standalone HTML/JS applications.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Fabric-Pro/fabric-oss32026년 10월 22일 업데이트

Set up something that runs on a schedule (a weekly report, a daily digest) as a scheduled workflow, change, pause or debug one, and build interactive pages (project artifacts and workspaces) that read live Fabric data. Use when the user asks for a recurring job, a status page, a dashboard or a page with buttons, or asks why one did not run.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Fabric-Pro/fabric-oss32026년 10월 22일 업데이트

Fabric-Pro의 스킬 모두 보기

이 스킬의 문제 신고