contributor-nomination

<!-- SPDX-License-Identifier: Apache-2.0 https://www.apache.org/licenses/LICENSE-2.0 --> <!-- Placeholder convention (see ../../../AGENTS.md#placeholder-convention-used-in-skill-files): <upstream> → value of `upstream_repo:` in <project-config>/project.md <project-config> → adopter's project-config directory <viewer> → the authenticated GitHub login of the maintainer running the skill --> # contributor-nomination > **GitHub projects only.** This skill assumes the project's primary > development activity is on GitHub and uses the GitHub CLI (`gh`) for > all data collection. Most ASF projects use GitHub, but some remain on > Apache GitBox (Gitea) or use other forges. If your project is not > on GitHub, the automated fetch steps will not work — you can still use > the off-GitHub signal sections and the nomination brief template, but > you will need to supply all contribution counts manually. Read-only skill that answers *"is this contributor ready to be nominated, and what is the evidence?"* for a single GitHub handle on `<upstream>`. Primary output is a **nomination brief** with four sections: | Section | What it shows | Maintainer use | |---|---|---| | **Contributions** | All tracks in one table — GitHub-derived counts (code, review, issues) and nominator-supplied signal (mailing list, docs, community, testing, mentoring) | Full picture; no track privileged over another | | **Activity timeline** | Month-by-month activity bar across the...