本文へ移動
cccskills
無料GitHub で公開

contributor-guide

Write a CONTRIBUTING guide that helps people contribute to an open-source project without friction. Use when asked to write a CONTRIBUTING.md, set up contribution guidelines, or make a repo welcoming to contributors. Produces a clear guide: how to set up, the contribution workflow, standards, PR expectations, and how to get help — lowering the barrier to a first PR.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md3.4 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Contributor Guide Skill

Most would-be contributors give up at setup friction or unclear expectations. A good CONTRIBUTING.md removes the guesswork: how to get the project running, how to propose a change, what a mergeable PR looks like, and where to ask. This skill writes that guide — welcoming, specific, and aimed at getting someone to a successful first PR.

Required Inputs

Ask for these only if they aren't already provided:

  • Project & stack — what it is, language/framework, repo layout basics.
  • Dev setup — how to clone, install, run locally, and run tests.
  • Workflow — branch model, commit/PR conventions, where issues live, who reviews.
  • Standards — linting/formatting, test requirements, the Code of Conduct (link).
  • Norms (optional) — how decisions are made, response times, good-first-issue process.

Output Format

A CONTRIBUTING.md:

Contributing to [Project]

A warm one-liner: contributions are welcome, here's how to make it smooth.

Ways to contribute — issues, docs, code, triage — not everyone writes code.

Development setup

# clone, install, run, test — the exact commands

…so a contributor can get the project running and tests passing locally.

Finding something to work on — point to good first issue / help wanted; ask people to comment before starting larger work.

Making a change (the workflow)

  1. Branch from … with naming convention …
  2. Make the change; follow the standards below.
  3. Add/update tests; run the linter/tests locally.
  4. Open a PR — what the PR description should include; link the issue.

Standards — formatting/linting, test expectations, commit/PR conventions, the Code of Conduct link.

What happens next — who reviews, rough turnaround, how feedback works.

Getting help — where to ask (Discussions, chat, issue) — make it explicitly OK to ask.

Quality Checks

  • Setup commands actually get the project running and tests passing
  • The contribution workflow is numbered and unambiguous (branch → change → test → PR)
  • Standards (lint, tests, commit/PR conventions, CoC) are stated and linked
  • It points to good-first-issues and welcomes non-code contributions
  • It's encouraging in tone and tells people exactly where to get help

Anti-Patterns

  • Do not assume the contributor knows the setup — spell out the exact commands
  • Do not leave PR expectations implicit — say what a mergeable PR includes
  • Do not be gatekeep-y or cold — friction and tone both lose contributors
  • Do not omit how to get help or who reviews — uncertainty stalls first PRs
  • Do not forget the Code of Conduct link — it sets the community standard

Based On

Open-source contribution best practices (clear setup, defined workflow, good-first-issues, welcoming tone, CoC).

Example Trigger Phrases

  • "Write a CONTRIBUTING.md."
  • "Set up contribution guidelines."
  • "Make a repo welcoming to contributors."

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Build or tailor an academic CV for faculty, postdoc, research or fellowship applications: publications, grants, teaching, supervision and service in the order the field expects, with consistent citations. Use when asked to write my academic CV, update my CV for a lectureship, tenure-track or postdoc application, format my publications list, or adapt my academic CV for an industry research role. Produces the full academic CV, a field-appropriate section order, a clean publications list in one citation style, and a two-page summary version when asked.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

mohitagw15856 のスキルをすべて見る

このスキルの問題を報告する