magpie-contributor-to-committer

To assess contributor readiness for GitHub committer status, use a skill that evaluates merged pull requests, code reviews, issues, and comments against project-defined thresholds to generate a traffic-light status and gap analysis.

GitHub metrics for evaluating committer readiness include merged pull requests, code reviews, filed issues, comments, and area breadth. These contribution metrics are measured against project-specific configuration thresholds to determine readiness.

To check if a contributor meets project thresholds using GitHub CLI, run the assessment command with their GitHub handle. The tool requires the GitHub CLI and project-specific configuration files to analyze contribution data.

Yes, you can evaluate GitHub contributor readiness using project-specific thresholds. The assessment requires project-defined configuration files to measure a contributor's activity, such as merged PRs and code reviews, against your specific criteria.

To generate a gap analysis for a GitHub contributor approaching committer status, you need the GitHub CLI installed and project-specific configuration files. The assessment outputs a readiness brief with a traffic-light status and narrative summary.

No, the committer readiness assessment does not work without automated data collection. It relies on the GitHub CLI to automatically fetch contribution metrics like merged PRs and code reviews, requiring no manual data gathering.