good-first-issue-author
From the author
Draft one net-new *good first issue* on the configured `<upstream>` repo from one supplied gap or small maintainer-named task. Run suitability and readiness checks before showing the draft. File via `gh` only after explicit maintainer confirmation. Never curate or relabel the existing backlog.
Install
npx skills add apache/magpie --skill good-first-issue-author -a claude-code
Installs to .claude/skills/good-first-issue-author/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
- Contains hidden text (invisible characters, long comments or encoded blobs)Medium
Why 75
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- newcomer-issue-explainerapache/magpieGiven 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. First confirms the issue is open, non-security, and scope-clear, then drafts the explanation for maintainer review. Posts nothing without explicit maintainer confirmation.Security★ 126
- welcomeapache/magpieDraft 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.Other★ 126
- good-first-issue-sweepapache/magpieSweep the open `<issue-tracker>` backlog for 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 rubric. Applies labels only after explicit maintainer confirmation.Writing★ 126
- pr-triageapache/magpieSweep open PRs on the configured `<upstream>` repo, classify each against the project's quality criteria, and — on the maintainer's confirmation — act via `gh`. One disposition per PR: draft / comment / close / rebase / CI-rerun / workflow-approve / ping-stale-reviewer / request author confirmation of readiness / mark `ready for maintainer review` / promote bot-authored draft. Does **not** review code — that is `pr-management-code-review`.Engineering★ 126
- upstream-firstmgifford/accessibility-skillsLoad this skill before implementing a fix for a barrier that may originate in a shared component, design system, renderer, or external dependency rather than this project's own code. Decide whether the responsible fix is local, an existing installed capability, or an upstream contribution before writing a workaround. Absolutely always record any temporary local divergence with an owner and removal condition. Under no circumstances open, comment on, or submit anything in an external project without explicit human approval.Design★ 57
- prepareapache/magpieDraft release-preparation artefacts for `<upstream>`: the planning issue, the version-bump and changelog prep PR (with the first-release review of what the source archive ships), the post-release dev-version bump PR, and, for ASF projects, the one-time `automated-signing` setup. Every output is a draft the RM confirms; nothing is merged, filed or sent.Planning★ 126
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in