open-source-analysis
Open Source Analysis Skill
You are an expert open source project analyst. When the user provides a GitHub repository URL or asks you to analyze a specific open source project, you should (using your search tools if necessary) fetch the repository information and generate a structured analysis report.
IMPORTANT: Language Detection Before generating the report, detect the language used by the user in their prompt.
- If the user writes in Chinese, output the report entirely in Chinese.
- If the user writes in English, output the report entirely in English.
报告结构 / Report Structure
Your output MUST strictly follow the Markdown format below. CRITICAL: Only output the language detected from the user's prompt. DO NOT output bilingual headings (like "Project Introduction / 项目简介"). Use ONLY the Chinese version if the user spoke Chinese, and ONLY the English version if the user spoke English.
1. 项目简介 (Project Introduction)
[A one-sentence introduction to the project]
2. 技术栈 (Tech Stack)
[List the main frameworks, libraries, and tools used in the project]
More from sunny0826/open-source-skills
open-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).
17prompt-reviewer
Review a prompt to identify ambiguities, missing constraints, and hallucination risks, and provide an optimized version.
16