AI Agent Workflow Collection

Measures contributor-sentiment signals on over a configurable window: thread tone (first-response classification), time-to-first-reply (median hours), first-PR retention (second-PR rate), and reviewer load (Gini coefficient). Compares each signal against a pre-adoption baseline and produces a structured gate report used to decide whether a skill family is ready to advance from experimental to stable.

Read-only readiness tracker that maps a contributor's GitHub activity against the adopter's PMC-declared committer or PMC thresholds and surfaces a traffic-light brief (Not yet / Approaching / Ready to nominate) plus the specific evidence gaps that remain.

Read-only license audit of a project's direct and transitive dependency tree. Detects the dependency manager(s), resolves each dependency's declared license from ecosystem metadata, classifies each against a configured policy (ASF three-category A/B/X model or a custom allowlist), and surfaces incompatible, forbidden, and unknown-license dependencies for maintainer review. Never modifies manifests or lock files.

Read-only flaky-test detection from GitHub Actions CI run history for one repository. Parses workflow run outcomes over a configurable window, computes per-job failure rates, and distinguishes intermittent failures (flaky) from consistent failures (deterministically broken). Produces a prioritised triage list without modifying any test code, workflow file, or tracker state.

Sweep the open 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.

Read-only maintainer dashboard for the open general-issue backlog of . Surfaces a health rating, prioritised recommendations, age and staleness breakdowns, area pressure ranking, and a triage-funnel summary. Output is HTML by default; markdown fallback available.

Merge two open issues that describe the same root cause, preserving both reporters' context. Proposes a closing comment on the duplicate and a cross-reference comment on the kept issue. Waits for maintainer confirmation before posting anything or closing anything.

Read-only license compliance audit for one repository or a local checkout. Checks that a LICENSE file exists, that a NOTICE file is present and complete when required by the declared license, and that source files carry SPDX-License-Identifier headers consistent with the project's declared license. Produces a grouped compliance report and proposes remedies for maintainer review. Never modifies any file.

Given an open good-first-issue on the configured 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.

Answer a newcomer's "how do I contribute here" question by grounding the response in CONTRIBUTING.md and the project's own docs. Classifies the question (setup / workflow / first-issue / out-of-scope), retrieves the relevant guide excerpt, and drafts a concise answer in the Agentic Mentoring teaching register. Routes out-of-scope questions (design, security, deprecation, architectural taste) to a human maintainer. Read-only; produces a draft answer text — no files are written and no comments are posted without the maintainer's explicit action.

Sweep open pull requests on the configured repo for inactivity past a configurable threshold and propose either a conversion to draft (when the PR is open but has gone quiet) or a closure (when the PR has been abandoned long enough to presume the author has moved on). Waits for maintainer confirmation before converting or closing anything.

Run a newcomer-focused pre-flight checklist on a local branch before opening a pull request. Checks CONTRIBUTING conventions, SPDX headers on new files, commit-message shape (including the Generated-by: trailer for AI-assisted work), and the placeholder convention — then returns a structured checklist report. Read-only; no state changes, no PR, no external writes.

Scan dist/release/ / (or the configured distribution location), identify releases past the project's retention rule, and propose the backend-shaped command set to move them to the archive area. Read-only on the distribution surface; the RM executes every archival command as themselves.

Assemble a per-release audit record from the planning issue, vote thread, RC artefact list, promote revision, and announcement archive URL, then propose a PR that appends the record to the project's audit log. Read-only on every release surface; the only write is a PR the RM reviews and a committer merges.

Draft the diff that adds the Release Manager's public key to the project's KEYS file ( ), emit a paste-ready svn (or backend-equivalent) command sequence, remind the RM to upload to the configured keyserver, and validate the key meets the ASF strength floor. Never commits, never holds or reads the private key. Step 3 of the release-management lifecycle.

Draft the release planning issue (Step 1), the prep PR with version bump, changelog, NOTICE, and LICENSE updates (Step 2), or the post-release development-version bump PR (Step 14) for . Reads release metadata from /release-trains.md and /release-management-config.md. Every output is a draft confirmed by the Release Manager before filing; the agent never marks a PR ready, never merges, and never closes any artefact.

Emit the backend-shaped promotion command set for a release that has passed its vote. Reads the planning issue (must carry vote-passed), constructs the staging → release move for the configured distribution backend, checks PMC membership of the Release Manager, and proposes the promoted label. Never runs the promotion command itself and never publishes the release.

Emit the paste-ready command sequence to tag an RC, build artefacts, sign each artefact, generate checksums, and stage them to the adopter's distribution backend. Covers Steps 4–5 of the release-management lifecycle. Never runs any command locally — all sequences are emitted for the Release Manager to execute on their own machine with their own key and ASF credentials.

Read-only pre-flight verification of a staged release candidate (RC) for . Verifies GPG signatures, checksums, Apache RAT license headers, NOTICE/LICENSE presence, prohibited-binary absence, and version-string consistency across manifest files. Emits a structured PASS / PASS-WITH-WARNINGS / FAIL report. Makes no state change; a --post-to flag proposes a comment for explicit RM confirmation before any posting.

Draft the [VOTE] email body and planning-issue comment for an RC of . Reads RC metadata from the planning issue and /release-management-config.md; produces a ready-to-copy [VOTE] subject + body and a proposed planning-issue comment. Never sends mail and never posts without explicit RM confirmation.

After the approval window closes, fetch the approval signal for an RC of , classify each reply as +1 / 0 / -1 and binding or non-binding against the configured roster, produce the tally summary, and draft the [RESULT] [VOTE] email. Never sends mail and never applies a label without explicit RM confirmation.

Given an open issue or PR, scores the project's configured reviewer roster across three signals — touched-area eligibility, git-history familiarity with the changed paths, and current open-review load — and proposes a primary reviewer (plus an optional backup). Read-only and propose-then-confirm: nothing is assigned, labelled, or requested without the maintainer's explicit confirmation. An unresolved roster produces an explicit NO ELIGIBLE REVIEWER signal, never a fabricated handle.

Turn a framework bug or quirk the agent hit while running a Magpie skill or tool into a fix PR against apache/magpie — one PR per issue. First confirms the problem is a framework defect (not a local misconfiguration or a stale snapshot), then searches apache/magpie for an existing issue or PR that already covers it, and only proposes a new fix PR when none exists — otherwise it points the user at the pending one.

Compare two near-duplicate skills — typically an ASF variant and a non-ASF or multi-project variant — and classify every difference as ALLOWED, DRIFT, or SAFETY-BASELINE. Produces a structured diff and a reconciliation proposal. Read-only: it never rewrites either skill; convergence is a separate confirmed authoring step. A safety-baseline divergence is always a must-fix, never silently merged into allowed-divergence noise.