Search guides, workflows, and reference pages.

Docs/Committer readiness and onboarding

Install & first runs

Install just this family — one plugin, 9 skills. The path-to-committer track.

Once you have added the marketplace:

/plugin install magpie-contributor-growth@apache-magpie

New to Magpie? The quick start walks the whole path in one place — install, the first /magpie-setup:setup run, and a recording of it happening — plus the other agents and the secure-isolation setup to run next.

The first contributor-growth skill you run opens with a one-minute welcome guide: the typical flow, what needs configuring, what to ask it, and how to make it yours. Dismiss it, or hide it for good, from its last line; “show the contributor-growth welcome again” or /magpie-setup:welcome-guide contributor-growth brings it back.

Before the first run

An animated /magpie-setup:setup config run for the contributor-growth family: the check failing, the values derived from the repository, one question for the rest, and personal files written

Illustrative — the real run derives more and asks better. What is true is the shape: it runs itself, it writes only your personal layer, and it stages nothing.

Every skill here resolves project-specific values from the adopter’s <project-config>/ directory — which is your personal layer first — .apache-magpie-local/ (gitignored) in a project that adopted Magpie, <git-common-dir>/apache-magpie/ in one that did not — then .apache-magpie-overrides/ (committed, the project’s).

For yourself: /magpie-setup:setup config scaffolds and fills these locally (/magpie-setup config on a pinned-snapshot install). Nothing is staged, nothing is committed, and it works on a repository that has never adopted Magpie.

This configuration stays personal. /magpie-setup:setup adopt never promotes or scaffolds it into .apache-magpie-overrides/: committed thresholds would tell every contributor how to game them.

Required. Without these a skill would act on a guess, so it stops and says which file is missing.

File What it carries Read by
committer-onboarding-config.md Capability-flag vocabulary for committer intake and governance models (icla/dco/no-cla; asf-pmc/github-codeowners/maintainer-roster). committer-onboarding
committer-readiness.md The project’s declared committer and PMC thresholds — what a contributor’s activity is measured against. calibrate, candidate-screen, contributor-to-committer
contributor-nomination-config.md Nomination-brief thresholds and assessment window. calibrate, candidate-screen, nomination
contributor-sentiment-config.md Signal thresholds for the sentiment gate. Every key has a default. sentiment
onboarding-concierge-config.md The path a new contributor is walked through, and who owns each step. onboarding-concierge
privacy-llm.md Which model tier may see which class of content, for projects routing foundation-private information away from third-party models. calibrate
project.md Project manifest. Identity, repositories, mailing lists, tools enabled, CVE tooling, GitHub project-board + issue-template field declarations. The single file every skill reads to resolve project-scoped references. activity-sweep, calibrate, candidate-screen, committer-onboarding, contributor-to-committer, identity-map, nomination, onboarding-concierge, sentiment

Optional. Each has a documented fallback; absent, the skill still runs.

File What it carries Read by
contributor-identities.md The project’s community channels, and confirmed mappings from each contributor’s GitHub handle to their Slack, Discord, mailing-list, and social-media handles. Written by contributor-identity-map after a maintainer confirms each one. committer-onboarding, identity-map, nomination
issue-tracker-config.md Tracker URL, project key, auth model, default query templates. activity-sweep, calibrate, contributor-to-committer, nomination, sentiment
pmc-roster.md Who is binding. Read wherever a vote is counted or a PMC-only action is gated. candidate-screen, nomination

Try these first

Illustrative shapes, not real transcripts — your output will differ. Nothing below sends, merges, or posts anything without you confirming it.

Sweep recent contributor activity.

/magpie-contributor-growth:activity-sweep

An activity-sweep run: ninety days of authored PRs, reviews, issues and comments for one contributor, with a note that mailing lists and release votes are not in the total

Draft a nomination brief.

/magpie-contributor-growth:nomination

A nomination run summarising a year of GitHub activity, naming the off-GitHub evidence it cannot see, and drafting the discussion thread without sending it

Onboard a new committer.

/magpie-contributor-growth:committer-onboarding

A committer-onboarding run: two steps done, two waiting on a PMC chair, and the welcome announcement drafted but not sent

Suggest a change