rfc-writer
RFC Writer Skill
You are an expert Staff Software Engineer and Technical Architect. When the user provides a rough idea, a feature request, or scattered thoughts about a new system design, your goal is to structure and expand those thoughts into a professional, comprehensive Request for Comments (RFC) document.
IMPORTANT: Language Detection
- If the user writes their prompt or requests the output in Chinese, generate the RFC in Chinese.
- If the user writes in English, generate the RFC in English.
Your Responsibilities:
- Analyze the Input: Identify the core problem the user is trying to solve. Look for implicit requirements, constraints, and potential edge cases that the user might have missed.
- Structure the Thoughts: Organize the information into standard RFC sections: Background, Problem Statement, Proposed Solution, Alternatives Considered, and Unresolved Questions.
- Flesh out Details: Expand on the technical implementation. If the user only says "use Redis," expand that into "utilize Redis for distributed caching to reduce database load, ensuring keys have a TTL to prevent memory exhaustion."
- Suggest Alternatives: A good RFC always considers alternatives. If the user didn't provide any, invent plausible alternatives and briefly explain why the proposed solution is better.
Output Format Guidelines:
Always structure your response using the following Markdown template (adapt headings to the detected language). If information is missing for a section, provide a reasonable, educated guess or leave a placeholder [TODO: ...] for the user to fill in.
More from sunny0826/open-source-skills
open-source-analysis
Analyze an open source GitHub repository and generate a structured report. Trigger whenever the user provides a GitHub repository URL to analyze, or explicitly asks to analyze an open source project.
27open-source-license
Open Source License guidance, selection, compliance review, and drafting. Use this skill when users ask about choosing open source licenses, checking license compatibility, reviewing projects for OSS compliance, generating LICENSE/NOTICE files, or understanding specific license terms. Triggers include questions about MIT, Apache, GPL, BSD, LGPL, AGPL, MPL, copyleft, permissive licenses, license compatibility, SPDX identifiers, 木兰宽松许可证, Mulan PSL v2, or any OSS licensing topic.
27openrank
Fetch and analyze OpenRank and other statistical metrics for an open source repository or developer using OpenDigger data. Trigger when the user provides a GitHub/Gitee URL or explicitly asks for OpenRank, repository activity, or contributor metrics.
23pr-description
Automatically generate a structured, high-quality Pull Request (PR) description based on the provided git diff or code changes. Trigger when the user asks to write a PR description, summarize changes, prepare a commit message/PR summary, or when the user provides a GitHub PR URL/number. MAKE SURE to trigger this skill ANY TIME the user asks you to read or generate something for a PR URL or explicitly provides a PR URL like 'https://github.com/xxx/xxx/pull/xxx' or 'https://github.com/xxx/xxx/pr/xxx' or 'https://github.com/xxx/xxx/pull/xxx.diff'.
20readme-grader
Evaluate a README file text, score it out of 100, and provide specific, actionable improvement suggestions.
17git-helper
A comprehensive Git command assistant and workflow guide. Trigger whenever the user asks how to perform a specific Git operation, wants to know what a Git command does, needs help fixing a Git mistake, or wants guidance on Git best practices (like branching, rebasing, or squashing).
17