open-source-skills

Use when the user asks to design, create, review, improve, package, distribute, measure, or classify AI agent Skills, Claude Code Skills, Codex skills, or reusable agent workflows; convert recurring workflows, runbooks, verification steps, API usage, scaffolding, code review, CI/CD, infrastructure operations, data analysis, or team automation into a maintainable SKILL.md with gotchas, progressive disclosure, resources, evals, rollout guidance, and measurement.

Use when the user asks to write or improve CLI help output, usage text, option/flag documentation, subcommand docs, examples, terminal `--help` text, or a man-page style command reference from raw arguments or an existing CLI.

Use when the user asks to create, revise, or audit a CONTRIBUTING.md/contributor guide, onboarding instructions, local development setup, test/lint workflow, PR process, commit conventions, or open-source contribution guidance for a repository.

Use when the user asks to review, debug, harden, or optimize a Dockerfile or container build for smaller images, faster caching, multi-stage builds, non-root runtime users, dependency installation, .dockerignore, or Docker best practices.

Use when the user asks how to perform, explain, or recover from a Git operation: status/log inspection, branching, staging, commits, amend, reset, revert, rebase, merge conflicts, stash, reflog, submodules, remotes, force-push safety, or rewriting history.

Use when the user asks to triage an issue, bug report, feature request, crash report, reproduction steps, maintainer response, issue priority/severity, missing diagnostic information, or labels for GitHub/GitLab-style issue content.

Use when the user provides a GitHub repository URL/name or asks to analyze an open-source project, compare project health, inspect stars/forks/license/languages, summarize tech stack, evaluate activity/community/docs, or produce an OSS project report.

Use when the user asks about open-source license choice, compatibility, compliance, SPDX identifiers, LICENSE/NOTICE files, source headers, copyleft/permissive tradeoffs, MIT, Apache-2.0, GPL, LGPL, AGPL, BSD, MPL, 木兰宽松许可证, Mulan PSL v2, or OSS licensing terms.

Use when the user asks for OpenRank, OpenDigger metrics, repository/developer activity, community OpenRank, stars/attention trends, contributor metrics, issue/PR metrics, or month/quarter/year metric tables for a GitHub or Gitee project/user.

Use when the user asks to write, revise, or apply a Pull Request description/title/summary from a diff, branch, commit range, PR number, GitHub PR URL, `.diff` URL, or local changes. Also use for reviewer notes, testing summaries, and PR template completion.

Use when the user asks to review, debug, rewrite, strengthen, or optimize a prompt; identify ambiguity, missing context, weak constraints, output format issues, evaluation criteria gaps, prompt-injection risk, or hallucination risk; or produce a clearer ready-to-use prompt.

Use when the user asks to grade, audit, score, review, or improve a README; evaluate open-source project docs for clarity, installation, quick start, usage examples, contribution guidance, badges, license, formatting, missing sections, or actionable documentation improvements.

Use when the user asks to write, polish, or categorize release notes, changelog entries, GitHub Releases, version summaries, upgrade notes, breaking changes, highlights, fixes, acknowledgements, or user-facing summaries from commits, PR titles, tags, or existing release text.

Use when the user asks to draft, structure, review, or expand an RFC, technical proposal, architecture design, design doc, ADR-style decision, migration plan, system change, alternatives analysis, rollout plan, risks, tradeoffs, or unresolved questions.