Plan and implement work described in a GitHub issue, including verification, documentation, and a PR that closes the issue.
日本語の概要は準備中です。原文の説明を表示しています。
NVIDIA/OpenShell1.6万2026年10月10日 更新
無料GitHub で公開
create-rfc
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.
インストール方法を見る含まれるファイル（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.
- Read
rfc/README.mdto confirm when an RFC is appropriate, how to choose the RFC number, and how the lifecycle works. - Read
rfc/0000-template/README.mdbefore drafting. Follow its section guidance, including scope, expected detail, and suggested section length. - Choose the next available
NNNNfrom the existingrfc/NNNN-*directories unless the user provided a specific number. - Create
rfc/NNNN-short-title/README.mdby copying the template and replacing placeholders. Use a short hyphenated folder title. - 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. - 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.
- Preserve uncertainty in Open questions instead of silently deciding unknowns. If a missing decision blocks a coherent RFC, ask the user for that decision.
- 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.
レビュー
まだレビューはありません。使ってみた感想をお寄せください。
同じリポジトリのスキル
概要と使いどころ
Maintain and validate OpenShell's build-only Windows MSVC lane for x64 and ARM64. Use when working on Windows compilation, `windows:*` mise tasks, unsupported Windows compute-driver contracts, or Windows build reports. This skill does not implement Docker, Kubernetes, Podman, VM, MXC driver, policy translation, MSI, service, or supervisor runtime support on Windows.
日本語の概要は準備中です。原文の説明を表示しています。
NVIDIA/OpenShell1.6万2026年10月10日 更新
Create GitHub issues using the gh CLI. Use when the user wants to create a new issue, report a bug, request a feature, or create a task in GitHub. Trigger keywords - create issue, new issue, file bug, report bug, feature request, github issue.
日本語の概要は準備中です。原文の説明を表示しています。
NVIDIA/OpenShell1.6万2026年10月10日 更新
Create GitHub pull requests using the gh CLI. Use when the user wants to create a new PR, submit code for review, or open a pull request. Trigger keywords - create PR, pull request, new PR, submit for review, code review.
日本語の概要は準備中です。原文の説明を表示しています。
NVIDIA/OpenShell1.6万2026年10月10日 更新
Investigate an OpenShell problem and create a structured issue with technical findings for human disposition.
日本語の概要は準備中です。原文の説明を表示しています。
NVIDIA/OpenShell1.6万2026年10月10日 更新
Debug inference clients that use an attached provider and its native endpoint, including hosted APIs and host-local Ollama, vLLM, SGLang, TRT-LLM, LM Studio, or NIM. Use for provider attachment, endpoint policy, credential substitution, topology, and migration from the removed managed inference endpoint. Trigger keywords - debug inference, managed inference endpoint, local inference, ollama, lm studio, vllm, sglang, trtllm, NIM, inference failing, model server unreachable, credential_endpoint_mismatch, host.openshell.internal.
日本語の概要は準備中です。原文の説明を表示しています。
NVIDIA/OpenShell1.6万2026年10月10日 更新