magpie-newcomer-issue-explainer

Solid

Given an open good-first-issue on the configured `<upstream>` repo, explain it in beginner terms and sketch a concrete approach: which files to read first, what "done" looks like, and where to ask follow-up questions — without writing any code or fix. First runs an issue assessment to confirm the issue is open, non-security, and scope-clear. Then drafts the explanation for maintainer review. Read-only; nothing is posted without explicit maintainer confirmation.

AI & Automation 83 stars 78 forks Updated yesterday Apache-2.0

Install

View on GitHub

Quality Score: 84/100

Stars 20%
64
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

<!-- SPDX-License-Identifier: Apache-2.0 https://www.apache.org/licenses/LICENSE-2.0 --> <!-- Placeholder convention: <upstream> → upstream codebase repo in `owner/name` form (default: read from `<project-config>/project.md → upstream_repo`) <project-config> → the adopting project's config directory (see /AGENTS.md § Placeholder convention) Substitute these with concrete values before running any `gh` command below. --> # newcomer-issue-explainer **Status: experimental.** An Agentic Mentoring ([conversational mentoring](../../docs/mentoring/spec.md)) skill that explains an existing good-first-issue to a newcomer contributor in plain language. Where [`good-first-issue-author`](../good-first-issue-author/SKILL.md) *authors* issues and [`good-first-issue-sweep`](../good-first-issue-sweep/SKILL.md) *curates* the backlog, this skill *explains* what has already been filed — it is the teaching bridge between "I found an issue" and "I know where to start". This skill acts on **one issue** per invocation. Its job is to answer, for the supplied issue number, two questions in order: > *Is this issue suitable to explain to a first-time contributor — and > if so, what does a concrete, beginner-friendly explanation say?* If the issue is unsuitable (closed, security-sensitive, or too vague), the skill says so and exits without drafting. A missing explanation is better than a misleading one. The Agentic Mentoring spec (scope, register, hand-off rules, adopt...

Details

Author
apache
Repository
apache/magpie
Created
3 months ago
Last Updated
yesterday
Language
Python
License
Apache-2.0

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

magpie-good-first-issue-author

Draft a single net-new *good first issue* on the configured `<upstream>` repo from one supplied candidate such as a known gap or a small maintainer-named task. The skill first runs a suitability gate to confirm the candidate is small and newcomer-safe. If it passes the skill drafts one issue. The draft carries scope, code pointers, contributing-doc links, acceptance criteria, and an effort estimate. A readiness checklist gates the draft before it is shown. Nothing is filed via `gh` until the maintainer explicitly confirms. The skill never curates or relabels the existing backlog.

83 Updated yesterday
apache
AI & Automation Solid

magpie-good-first-issue-sweep

Sweep the open `<issue-tracker>` backlog for existing issues that could be labelled as good first issues. Classifies each candidate as READY (propose the GFI label), NEAR-MISS (surface edits to make it GFI-ready), or SKIP using the G1–G7 suitability rubric. Applies labels only after explicit maintainer confirmation; never edits issue bodies without the maintainer's direction.

83 Updated yesterday
apache
AI & Automation Solid

magpie-mentoring-welcome

Draft a first-contact orientation comment for a first-time contributor on a newly opened issue or PR on the configured `<upstream>` repo. Detects first-time authorship via the GitHub `author_association` field and drafts a welcome with contributing-guide link, community-norm pointers, and expected next steps. Waits for explicit maintainer confirmation before posting. Does not post for repeat contributors.

83 Updated yesterday
apache