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

create-rfc

Turn a design request into an OpenShell RFC, a proposal for review and discussion. The skill follows the project template, assigns an available number, and organizes motivation, alternatives, and open questions into a draft.

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

원문원문 설명 보기

Create OpenShell RFC proposals in rfc/ from a design request. Use when the user asks to write, draft, start, create, or update an RFC, Request for Comments, architecture proposal, API proposal, process proposal, or cross-cutting design proposal that should follow the OpenShell RFC process and template.

설치 방법 보기

이럴 때 유용합니다

  • Drafting an architecture proposal
  • Organizing an API change proposal
  • Documenting a process change
  • Updating an existing RFC

포함된 파일(2)

  • SKILL.md2.6 KB
  • agents/openai.yaml174 B

SKILL.md(원문)

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

Create RFC

Workflow

Create RFCs by following rfc/README.md and rfc/0000-template/README.md. Keep the template as the source of truth for section guidance.

  1. Read rfc/README.md to confirm when an RFC is appropriate, how to choose the RFC number, and how the lifecycle works.
  2. Read rfc/0000-template/README.md before drafting. Follow its section guidance, including scope, expected detail, and suggested section length.
  3. Choose the next available NNNN from the existing rfc/NNNN-* directories unless the user provided a specific number.
  4. Create rfc/NNNN-short-title/README.md by copying the template and replacing placeholders. Use a short hyphenated folder title.
  5. Fill in front matter with the RFC author, state: draft, and any related links the user provided. If the author is unknown, use the requesting user's GitHub handle when available or leave the template placeholder.
  6. Draft each section from the user's design context. Keep Summary concise, Motivation readable by anyone, Non-goals explicit, Proposal focused on what is being proposed, and Alternatives focused on credible competing approaches.
  7. Preserve uncertainty in Open questions instead of silently deciding unknowns. If a missing decision blocks a coherent RFC, ask the user for that decision.
  8. Check the completed RFC against the template once more before finishing.

Writing Standards

  • Prefer concrete design statements over placeholder language.
  • Link to relevant issues, prior RFCs, and published docs when they provide needed context.
  • Keep rejected or left-out designs in Alternatives, not Proposal.
  • Use Mermaid diagrams for architecture or data flow when a diagram would make the proposal easier to review.
  • Do not update published docs just because an RFC was drafted. Those updates belong with implementation or with an accepted RFC when the user asks for them.

Validation

Before handing the RFC back to the user:

  • Verify the folder name and RFC number match the process in rfc/README.md.
  • Verify every template section is present or intentionally marked as not applicable.
  • Run a Markdown formatting or lint check only if the repo already provides one for Markdown-only changes.

리뷰

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

댓글

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

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

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

0 / 1,000자

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

같은 저장소의 스킬

Process one recommendation selected by ID from a local issue or CI triage report. Apply, reject, or defer it, record the outcome, and obtain separate confirmation before each change made on GitHub.

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

  • Apply one recommendation selected by its item ID
  • Reject a recommendation and record the reason
  • Defer a decision for the next queue review
NVIDIA/OpenShell1.7만2026년 10월 19일 업데이트

Turn a GitHub issue into a scoped implementation plan and, when authorized, code changes, tests, documentation, and a pull request that closes it. Check existing ownership and feedback to keep work aligned with acceptance criteria.

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

  • Creating an implementation plan from a GitHub issue
  • Implementing an authorized issue with focused tests
  • Updating documentation alongside behavior changes
NVIDIA/OpenShell1.7만2026년 10월 19일 업데이트

Maintain and validate OpenShell builds for Windows on x64 and ARM64 using MSVC, Microsoft's C++ toolchain. Check compilation, build executables, run tests on native hosts, and report artifacts and unsupported driver behavior.

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

  • Investigating Windows compilation failures
  • Building x64 and ARM64 release executables
  • Checking errors for unsupported drivers
NVIDIA/OpenShell1.7만2026년 10월 19일 업데이트

Create GitHub issues for OpenShell bugs, feature requests, and tasks using the gh command-line tool. Organize firsthand use cases, impact, and completion criteria into the project's templates, then return the created issue link.

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

  • Report an OpenShell bug you directly encountered
  • Request a feature for a specific OpenShell use case
  • Register an internal task with completion criteria
NVIDIA/OpenShell1.7만2026년 10월 19일 업데이트

Create GitHub pull requests with the gh command-line tool. Check linked issues, contributor permissions, branch conventions, and relevant tests, then prepare a title and description that follow the project's contribution rules.

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

  • Submit code changes for review
  • Open a draft pull request
  • Link a pull request to its issue
NVIDIA/OpenShell1.7만2026년 10월 19일 업데이트

Investigate a specific OpenShell problem or feature need and create a structured GitHub issue. Record observed behavior, technical findings, alternatives, and missing evidence so a human can decide what to accept and pursue.

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

  • Investigate an OpenShell bug and document reproduction steps
  • Compare alternatives for a specific feature need
  • Prepare a structured issue for human review
NVIDIA/OpenShell1.7만2026년 10월 19일 업데이트

NVIDIA의 스킬 모두 보기

이 스킬의 문제 신고