apache
- 417 skills
- 0 followers
- 145 repo stars
- yesterday last updated
- ▌ Bug Triage · apacheTriage open Comet issues marked `requires-triage` per the project bug triage guide. Classifies each issue as a bug or an enhancement, applies the recommended type (`bug`/`enhancement`), priority, and area labels, removes `requires-triage`, and files a dated summary issue listing what was done. A human reviews the summary issue and closes it when satisfied.
- ▌ Review Comet Pr · apacheUse when reviewing a DataFusion Comet pull request. Covers the workflow that applies to every PR and routes to the area-specific review skills for expressions, FFI, memory management, shuffle, Iceberg writes, and documentation. Provides guidance to a human reviewer rather than posting comments.
- ▌ Review Comet Docs · apacheUse when reviewing the documentation in a DataFusion Comet pull request or branch, or when auditing an existing page or directory under docs/source or README.md. Checks wording against the documentation style guide and checks that config keys, operator names, links, images and generated content match the code. Advisory only, it never edits files or posts comments. Load alongside review-comet-pr when a PR changes docs.
- ▌ Review Comet Ffi Pr · apacheUse when reviewing a DataFusion Comet pull request that crosses the JVM/native boundary, touching Arrow C Data or C Stream interface code, batch export and import, CometExecIterator, ScanExec, NativeUtil, CometVector subclasses, or jni_api. Load alongside review-comet-pr.
- ▌ Audit Comet Expression · apacheAudit an existing Comet expression for correctness and test coverage. Studies the Spark implementation across versions 3.4.3, 3.5.8, 4.0.1, and 4.1.1, reviews the Comet and DataFusion implementations, identifies missing test coverage, and offers to implement additional tests.
- ▌ Review Comet Memory Pr · apacheUse when reviewing a DataFusion Comet pull request that touches memory pools, memory reservations, spilling, the Spark TaskMemoryManager bridge, allocators, or memory-related configuration. Load alongside review-comet-pr.
- ▌ Review Comet Shuffle Pr · apacheUse when reviewing a DataFusion Comet pull request that touches native or JVM columnar shuffle, the shuffle writers and readers, partitioning, the Arrow IPC block format, shuffle compression, or the Celeborn integration. Load alongside review-comet-pr.
- ▌ Wire Datafusion Function · apacheUse when wiring an existing DataFusion or datafusion-spark function into Comet for a Spark expression. Identifies the right wiring pattern (one-line passthrough, datafusion-spark UDF registration, or custom serde with input massaging / restrictions), applies the Scala serde, registers the UDF in jni_api when needed, and adds SQL file tests. Assumes the function already exists upstream — if not, switch to `implement-comet-expression`.
- ▌ Optimize Comet Expression · apacheUse when optimizing the performance of an existing native scalar expression in the datafusion-comet-spark-expr crate (native/spark-expr/) — casts, string/JSON/array/math kernels that run per-row or per-batch. Covers benchmarking, keeping output bit-identical, and the no-regression gate. Not for adding new expressions (use implement-comet-expression) or wiring upstream functions (use wire-datafusion-function).
- ▌ Suggest Native Expression · apacheUse when picking the next Spark expression to implement natively in Comet, or when asked whether a specific codegen-dispatched expression is worth a native Rust implementation. Scores the candidate on how likely a native path can be 100% Spark-compatible and how much throughput or allocation it would save versus the JVM codegen dispatcher, records the verdict in the per-expression audit log so disqualified candidates are not re-litigated, and files a GitHub issue for the recommendation.
- ▌ Review Comet Expression Pr · apacheUse when reviewing a DataFusion Comet pull request that adds or changes a Spark expression, its Scala serde, its protobuf message, or its native Rust implementation. Load alongside review-comet-pr, which covers the parts of the review that apply to every PR.
- ▌ Review Comet Iceberg Write Pr · apacheUse when reviewing a DataFusion Comet pull request that touches Iceberg writes, the split-operator write plan (IcebergWriteStrategy, IcebergWriteExec, IcebergCommitExec), the native Iceberg writer (CometIcebergWriteExec, iceberg_write.rs, iceberg_partition_path.rs), its eligibility gate (CometIcebergNativeWrite), or the iceberg-rust pin. Load alongside review-comet-pr.
- ▌ Daily Inspection · apacheInspect HertzBeat monitor health and metrics storage, then produce a concise operations report. Use for daily checks, fleet health reviews, and monitoring summaries.
- ▌ Mysql Slow Query Diagnosis · apacheDiagnose slow queries, active sessions, locks, and query plans for a monitored MySQL or MariaDB instance. Use when database latency or query performance is under investigation.
- ▌ Reqsign Release · apache bundleRelease Apache Reqsign through the Apache RC, vote, dist, tag, crates.io, and announcement flow.
- ▌ Flink Agents Dev · apache bundleUse when building, scaffolding, modifying, debugging, converting, or verifying Apache Flink Agents applications, including Flink Agents YAML, Workflow Agent, ReAct Agent, Actions, Resources, MCP servers, vector stores, runtime skills, Python, or Java. Do not use for ordinary Flink jobs that do not use Flink Agents.
- ▌ Math Calculator · apacheCalculate simple mathematical expressions using shell commands. Use when the user asks to perform arithmetic calculations like addition, subtraction, multiplication, division, or more complex math expressions.
- ▌ Bydbql · apache bundleGenerate, validate, and optionally execute read-only BanyanDB BydbQL for STREAM, MEASURE, TRACE, and PROPERTY resources. Use when the user asks to query BanyanDB, translate natural language to BydbQL, inspect BanyanDB schema or data, validate BydbQL, or fetch raw BanyanDB records.
- ▌ Gh Issue · apache bundleSize-audit, write, and split BanyanDB issues that somebody else or an automated TDD workflow can implement. Use whenever the user asks to file or revise an issue, decide whether an issue is too large, make an issue TDD-ready, turn a design into tickets, or split an umbrella into executable leaves. Do not draft or file an implementation issue before classifying it as a mergeable leaf or a tracking parent.
- ▌ Compiling · apacheCompile and build the SkyWalking BanyanDB project. Use when the user asks to compile, build, or generate code for this project.
- ▌ Vendor Update · apacheUpgrade Go/Node.js vendor dependencies and sync tool versions. Use whenever the user says "upgrade dependencies", "update vendors", "vendor update", "run vendor-upgrade", "bump dependencies", "update packages", or asks to run the `vendor-update` Make target. This skill also checks `scripts/build/version.mk` after upgrading to see if any tracked tool versions need updating too, and removes stale binaries from `bin/` when versions change.
- ▌ Gh Pull Request 2 · apacheCreate a GitHub pull request for SkyWalking BanyanDB. Use when the user asks to create a PR, submit changes, or open a pull request.
- ▌ Seatunnel Test Suite · apache bundleWrite or review Apache SeaTunnel E2E (Testcontainers) and unit tests so they are stable, leak-free, and deterministic. Use when creating a new *IT/*Test class, reviewing a test diff, or refactoring a flaky or leaking test.
- ▌ Tsfile · apache bundleWork with the current Apache TsFile SDKs, tools, and file format. Use for Java, Python, C++, or C reads and writes; Python DataFrame and Arrow batches; Java CSV/Parquet/Arrow import; file properties; TAG filters; query-by-row and metadata APIs; C++ incomplete-writer recovery and append; static/shared C++ builds; parallel and TsBlock writes; encoding/compression factories; schema design; performance; and cross-language integration. Route operations specific to the C++ tsfile-cli binary to the sibling tsfile-cli skill.
- ▌ Tsfile CLI · apache bundleUse specifically for the project's C++ `tsfile-cli` in cpp/tools: inspect, preview, export, or create an Apache TsFile; report metadata or per-column counts; or use its explicit single-table CSV write command.
- ▌ Trino Test · apache bundleRun, debug, and manage Trino integration tests for the Gravitino project.
- ▌ Gravitino Release · apache bundleApache Gravitino release manager — guides through the full staged release pipeline stage by stage
- ▌ Pr Review 3 · apacheUse when reviewing a pull request in the datafusion-ballista repo, including a request to review PR
- ▌ Brpc Release · apache bundleDrive an Apache bRPC release end to end - confirm the release slot, draft Release Notes, bump version files, cut the tag, build/sign/checksum the source tarball, stage it to Apache SVN dist/dev, verify the candidate, and draft the VOTE/RESULT/ANNOUNCE mails. Use when cutting, resuming, or verifying a bRPC release ("发版 <version>", "release apache brpc", "准备 RC", "写投票邮件", "验证发布包", "check the release candidate").
- ▌ Hudi Table Layout · apache bundleAnalyzes the physical layout of an Apache Hudi table (partition and file size distribution, skew, micro-partitioning, small-file pile-up, hot partitions) by running the HoodieTableLayoutAnalyzer utility and interpreting its JSON report. Invoke when a user asks how big a Hudi table or its partitions are, whether a table has a small-file problem, whether it is over-partitioned, which partitions take most of the writes, or how skewed the partitions are.
- ▌ Hudi Config Consultant · apache bundleAnswers questions about Apache Hudi `hoodie.*` configuration properties from a catalog generated out of the Hudi source tree — what a config does, its default and valid values, where in the code it is actually read, what gates it so that setting it can silently do nothing, and what else must be set alongside it. Invoke when a user asks what a config does, what to set for a goal, why a config they set had no effect, how two configs differ, or which configs go together.
- ▌ Hudi Rca · apache bundleExplains why an Apache Hudi job failed. Classifies a pasted stacktrace and supporting artifacts against a catalog of known failure patterns, states the evidence it is reasoning from, and gives an ordered mitigation ladder. When no pattern matches, narrates what Hudi was doing and which phase failed. Invoke when a user brings a Hudi failure, a confusing exception, a stalled table, or asks why a write, compaction, or table service is not working.
- ▌ Hudi Architect · apache bundleInteractive Apache Hudi table design advisor. Turns workload requirements into architecture guidance and an Architecture Decision Record through a tiered conversational flow, with configuration bundles on implemented executable routes. Invoke when a user wants help designing a new Hudi table or evaluating an existing design.
- ▌ Hudi Optimizer · apache bundleFinds what an Apache Hudi deployment is leaving on the table. Reads writer properties, a Spark event log, and the table itself, corroborates observations across them, and recommends configuration and capability changes with risk tiers and verification steps. Invoke when a Hudi job works but is slow, expensive, or larger on storage than expected, or when a user asks whether a feature such as the record-level index or clustering would help their table.
- ▌ Hudi Mdt Health · apache bundleChecks whether an Apache Hudi table's metadata table is healthy -- caught up with the data table, consistent with the files on storage, compacting on schedule, and with a record-level index sized for the table -- by running the HoodieTableHealthChecker utility's metadata-table checks and interpreting its JSON report. Invoke when a user asks whether the metadata table is in sync or lagging, whether file listings from the metadata table can be trusted, why metadata-table compaction is not running, whether the record index has too few file groups, or whether the metadata table needs to be rebuilt.
- ▌ Hudi Table Health · apache bundleChecks whether an Apache Hudi table's table services (compaction, cleaning, archival, savepoints) are keeping up with ingestion, by running the HoodieTableHealthChecker utility and interpreting its JSON report. Invoke when a user asks whether a Hudi table is healthy, whether compaction or cleaning is falling behind, why the active timeline keeps growing, or what to do about a savepoint blocking archival.
- ▌ Merge Candidates 2 · apache bundleFind trivial, low-risk PRs in the `ready for maintainer review` queue of <upstream> that pass every quality gate and touch only supplementary areas (docs, changelog, translations, tests): the express lane. Ranks them with a diff summary, an all-gates-green attestation and the exact merge command; on per-PR confirmation it can APPROVE, as pr-management-code-review does. Never merges itself.
- ▌ Reviewer Routing 2 · apache bundleScore the configured reviewer roster for an open issue or PR on area eligibility, git-history familiarity with the changed paths, and open-review load; propose a primary reviewer plus an optional backup. Read-only, propose-then-confirm; an unresolved roster yields NO ELIGIBLE REVIEWER, never a made-up handle.
- ▌ Pre First Pr Check 2 · apache bundleNewcomer pre-flight checklist for a local branch before opening a PR: CONTRIBUTING conventions, SPDX headers on new files, commit-message shape (including the Generated-by: trailer for AI-assisted work), and the placeholder convention. Returns a checklist report; read-only, no PR, no external writes.
- ▌ Dependency Vulnerability Audit 2 · apacheRead-only dependency vulnerability audit for a repository or local checkout: detects the dependency manager(s), runs the matching audit tool, groups patchable findings by severity, and proposes upgrades for review. Never edits manifests or lock files, never opens update PRs.
- ▌ Stale Sweep 2 · apache bundleSweep open `<issue-tracker>` issues inactive past a configurable threshold and propose a closure (presumed abandoned) or an update request nudging the reporter. Posts or closes nothing without maintainer confirmation.
- ▌ Issue Sync 2 · apache bundleSynchronize a security issue in <tracker> with its GitHub discussion, the <security-list> thread, and any <upstream> fix PRs. Proposes label / milestone / assignee / field / draft-email updates and applies only what the user confirms; suggests the next step and prints the CVE allocation link when a CVE is needed.
- ▌ Thread Mentor 2 · apache bundleDraft one teaching-register comment on a GitHub issue or PR thread on `<upstream>` for a contributor missing context a maintainer would spell out. Decides whether to intervene, follows the tone guide and convention pointers, posts via `gh` only on explicit confirmation, and escalates on the four hand-off triggers.
- ▌ Nomination 2 · apache bundleRead-only nomination brief for named contributors on <upstream>: code-host and tracker activity across contribution tracks, off-forge signal and vendor-neutrality context, then one [DISCUSS] email with a personal note per candidate. Surfaces information only; never rates a contributor or says whether they are ready.
- ▌ Manage REST API · apache bundleDesign, expose, refactor, and verify OFBiz REST APIs using the framework REST support, service engine contracts, native OFBiz services, and contract-safe wrapper patterns. Use when working with `.rest.xml` files, REST-exposed services, PWA/API consumers, service export settings, or backend REST response contracts.
- ▌ Announce Draft · apache bundleDraft the `[ANNOUNCE]` email and open (never merge) the site-bump PR for a promoted release of `<upstream>`. Never sends mail.
- ▌ Workflow Optimization · apache bundleRead-only review of one repository's GitHub Actions workflows and recent run history against the ASF Infra workflow-optimization practices. Produces a prioritised plan to cut runner use; never edits workflows, opens PRs, or posts comments.
- ▌ Newcomer Issue Explainer · apacheGiven 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.
- ▌ Candidate Screen · apache bundleSurface activity data about recent contributors who pass a long-tail pre-filter — for committer and <governance-body> discussions — as an alphabetical list with details, in a verified-private repository. Data only: no scoring, ranking, floor comparison or readiness verdict.
- ▌ Workflow Security Audit · apacheRead-only GitHub Actions workflow security audit for one repository, a repository set, or a whole GitHub org. Runs `zizmor` to surface injection vulnerabilities, excessive permissions, unpinned external actions, and self-hosted-runner fork-secret leaks. Produces a grouped, prioritised report; never edits workflows, opens PRs, or posts comments.
- ▌ Issue Import Via Forwarder · apache bundleSub-skill for reports relayed onto `<security-list>` by a broker (the ASF security team, a disclosure platform, a SOC) rather than sent by the reporter. Detects the relay, extracts the credit and the reporter-addressing rules through the adapters in `forwarders.enabled`, and hands the routing back. Never mutates the tracker.
- ▌ Dependency License Audit · apache bundleRead-only license audit of a dependency tree. Detects the manager(s), resolves each dependency's license from ecosystem metadata, and classifies it against a configured policy (ASF A/B/X or allowlist), surfacing incompatible, forbidden, and unknown-license dependencies. Never modifies manifests or lock files.
- ▌ License Compliance Audit · apacheRead-only license compliance audit for one repository or checkout: LICENSE present, NOTICE complete when the declared license requires it, and source files carrying SPDX-License-Identifier headers consistent with that license. Produces a grouped report with proposed remedies for review; never modifies any file.
- ▌ Committer Onboarding · apache bundlePost-vote committer and PMC onboarding for Apache projects, podling or top-level: walks the nominator from ICLA check to welcome announcement, and maps the new committer's GitHub handle to their Slack, Discord, and social-media identities for the nominator to confirm.
- ▌ Onboarding Concierge · apacheAnswer newcomer contribution questions grounded in `CONTRIBUTING.md` and docs. Classifies questions into setup, workflow, first-issue, or maintainer hand-off. Drafts a concise response in the mentoring register. Read-only; never writes files or posts comments without maintainer confirmation.
- ▌ Dependency Vulnerability Audit · apacheRead-only dependency vulnerability audit for one repository or a local checkout. Detects the project's dependency manager(s), runs the appropriate audit tool, surfaces patchable findings grouped by severity, and proposes upgrades for maintainer review. Never modifies manifests or lock files and never opens update PRs.
- ▌ Contributor To Committer · apache bundleRead-only brief showing a contributor's activity next to the project's committer or PMC reference levels, as plain numbers. Surfaces information only: no ranking, no status, no readiness verdict — the PMC decides.
- ▌ Merge Candidates · apache bundleIdentify trivial, low-risk PRs in the `ready for maintainer review` queue of <upstream> that pass every quality gate and touch only supplementary areas (docs, changelog, translations, tests) — the "express lane". Surfaces and ranks candidates with per-PR diff summaries, an all-gates-green attestation, and the exact merge command. On explicit per-PR confirmation it can submit an APPROVE review, exactly as pr-management-code-review does. It never merges itself — automated merge is the deliberately-deferred Agentic Autonomous mode.
- ▌ Reviewer Routing · apache bundleGiven 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, propose-then-confirm: nothing is assigned, labelled, or requested without confirmation. An unresolved roster yields an explicit NO ELIGIBLE REVIEWER signal, never a fabricated handle.
- ▌ Identity Map · apache bundleMap a contributor's code-host or community handle to their Slack, Discord, Matrix, mailing-list, and social-media identities. Infers each mapping from the sources the session can reach, grades the evidence, and records only what the maintainer confirms, in a project-wide identity file shared by the contributor-growth skills.
- ▌ Audit Report · apache bundleAssemble a per-release audit record from lifecycle artefacts (planning issue, vote thread, artefact list, promote revision, and announcement URL) and propose a PR appending it 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.
- ▌ Issue Import From Scan · apache bundleTriage a security scanner's multi-finding output (via a scan-format adapter; ASVS is the reference), bucket each finding, and apply only the operator's confirmed decisions. Publishes the report as a gist and can open a report-back PR.
- ▌ Good First Issue Sweep · apache bundleSweep 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.
- ▌ Pre First Pr Check · apache bundleRun a newcomer-focused pre-flight checklist on a local branch before opening a PR. 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.
- ▌ Archive Sweep · apache bundleScan the release distribution area (`dist/release/<project>/` when `release_dist_backend = svnpubsub`, 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.
- ▌ Tracker Stats Dashboard · apache bundleGenerate a self-contained HTML dashboard of `<tracker>` repository statistics for security-team review.
- ▌ Report Framework Issue · apacheFile a clean, redacted GitHub issue against the Apache Magpie framework repo when a skill, tool, or doc misbehaves. Gathers the problem from the user — never the raw session transcript — runs a mandatory public-disclosure scrub, renders the report into the framework's issue template, and files via `gh issue create --web` only on explicit confirmation.
- ▌ Activity Sweep · apacheRead-only activity card for a named contributor on `<upstream>` across code-host and tracker surfaces. Code-host and tracker activity only; use `contributor-nomination` for a full brief.
- ▌ Good First Issue Author · apache bundleDraft 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.
- ▌ Pr Stale Sweep · apache bundleSweep open PRs on the configured `<upstream>` repo for inactivity past a configurable threshold and propose either a conversion to draft (open but quiet) or a closure (abandoned long enough to presume the author moved on). Waits for maintainer confirmation before converting or closing.
- ▌ Keys Sync · apache bundleAdd the Release Manager's public key to the project KEYS file: check it meets the ASF strength floor, draft the KEYS diff, and emit the `svn` (or backend) commands and keyserver reminder for the RM to run. Never holds the private key, never commits.
- ▌ Verify Rc · apache bundleRead-only verification of a staged RC of `<upstream>`: signatures and checksums, RAT headers, NOTICE/LICENSE, prohibited binaries, JVM artefacts, the Nexus staging repository behind them (ASF projects publishing Maven artefacts), source-tree integrity, version strings, and optionally reproducibility. Emits a PASS / PASS-WITH-WARNINGS / FAIL report; `--post-to` proposes a planning-issue comment for the RM to confirm.
- ▌ Isolated Setup Install · apache bundleWalk an adopter through the first-time install of the secure agent setup (sandbox, approval and clean-environment layers) for Claude Code, Codex, Antigravity, Pi or Goose. Interactive throughout; never runs sudo, edits a shell rc, or overwrites settings on its own.
- ▌ Nomination · apache bundleRead-only nomination brief for one or more named contributors on <upstream>. Aggregates code-host and tracker activity across contribution tracks, off-forge signal, and vendor-neutrality context, then drafts one [DISCUSS] email for all of them, with a personal note per candidate and the level of detail the nominator picks. Surfaces information only: never rates a contributor or says whether they are ready.
- ▌ Vote Draft · apache bundleDraft the `[VOTE]` email body and planning-issue comment for an RC of `<upstream>`. Reads RC metadata from the planning issue and `<project-config>/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.
- ▌ Vote Tally · apache bundleAfter the approval window closes, fetch the approval signal for an RC of `<upstream>`, 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.
- ▌ Audit Finding Fix · apache bundleFor a batch of findings from a non-security audit tool (`<audit-tool>` — ruff / flake8 / mypy / pylint / CodeQL / Apache Verum / Apache Caer / equivalent; full list in the body) against `<upstream>`, draft the smallest fix per finding, re-running the tool after each batch to confirm clearance. Produces a commit and a hand-back artefact; never opens a PR on autopilot or merges.
- ▌ Flaky Test Triage · apacheRead-only flaky-test detection from GitHub Actions run history for one repository: parses run outcomes over a configurable window, computes per-job failure rates, and separates intermittent failures from deterministically broken ones. Produces a prioritised triage list without modifying tests, workflows, or tracker state.
- ▌ Issue Import From Md · apache bundleOpen one or more `<tracker>` tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the `Needs triage` board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.
- ▌ Issue Import From Pr · apache bundleOpen a tracker for a security-relevant fix that already exists as a public `<upstream>` PR, with no `<security-list>` report. The tracker lands in `Assessed` with scope, PR-state and remediation fields filled from the PR; pairs with `security-cve-allocate`.
- ▌ Prepare · apache bundleDraft 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.
- ▌ Promote · apache bundleEmit 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.
- ▌ Issue Deduplicate · apache bundleMerge two <tracker> tracking issues that describe the same root-cause vulnerability, preserving every reporter's credit, every mailing-list thread reference, and every independent attack-vector description. Updates the kept issue's body in place, closes the duplicate with the `duplicate` label, and regenerates the CVE JSON attachment so both finders land in `credits[]`.
- ▌ Skill Reconciler · apache bundleCompare 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.
- ▌ Thread Mentor · apache bundleDraft a teaching-register comment on a GitHub issue or PR thread on the configured `<upstream>` repo, aimed at a contributor missing context the maintainer would spell out. Reads the thread, decides whether an intervention is warranted, drafts one comment per the tone guide and convention pointers, and waits for explicit confirmation before posting via `gh`. Escalates on the four hand-off triggers.
- ▌ CI Runner Audit · apache bundleRead-only audit of GitHub Actions runner compatibility for one repository, a repository set, one Apache project, or the full Apache org. Finds obsolete GitHub-hosted runner labels and macOS runner/tool architecture mismatches. Produces TSV evidence; never edits workflows, opens PRs, or posts comments.
- ▌ Submit To Oss Scan · apache bundlePrepare the enrolment (or update) PR that puts a project into Anthropic's OSS Scanner: `project.yaml`, an offline-capable `Dockerfile`, and a `threat_model.md` derived from the project's security model; guides the maintainer through testing it first.
- ▌ Isolated Setup Doctor · apache bundleProbe the secure-agent setup for restrictions that block legitimate work — SSH agent reachability, port binding, containers, the scratch directory, the signing key, `gh` outside the sandbox, `prek` and `uv` inside it, the global git hook dir. Names the troubleshooting entry and settings fix for each. Read-only.
- ▌ Isolated Setup Update · apache bundleReport drift between the installed secure setup and the framework's current one — checkout, pinned tools, user-scope script copies, denial commands, MCP checkouts. Read-only: it surfaces diffs and the user decides.
- ▌ Isolated Setup Verify · apache bundleCheck the secure agent setup against its checklist and report done, missing or partial for each item, with the evidence — paths, command output, versions. Covers Claude Code, Codex, Antigravity, Pi, Goose and Copilot CLI. Read-only.
- ▌ Calibrate · apache bundleDerive committer and <governance-body> reference levels from the project's own past nomination decisions on <private-list>, deliberately relaxed below what was elected, and propose them as a numbers-only config diff.
- ▌ Sentiment · apacheMeasure contributor-sentiment signals on `<upstream>` over a window: thread tone, time-to-first-reply, first-PR retention, and reviewer load. Compares signals against baseline to generate a mode promotion gate report.
- ▌ Override Upstream · apache bundlePromote a local `.apache-magpie-overrides/<skill>.md` into a PR against `apache/magpie`. Once it merges and the adopter upgrades, the override is redundant and the skill offers to remove it.
- ▌ Shared Config Sync · apacheCommit and push the user's shared Claude config to the `~/.claude-config` sync repo, rebasing first so a push never buries work from another machine. Bootstraps the repo when it is missing. Never force-pushes, never rewrites pushed history, never creates a public remote, and touches nothing outside `~/.claude-config/`.
- ▌ Optimize Skill · apache bundleMake an existing framework skill leaner without changing its behavior. Diagnose context-cost smells, propose the applicable optimization passes, and validate before and after every approved change.
- ▌ Code Review 2 · apache bundleWalk a maintainer through deep, sequential code review of open PRs on the configured `<upstream>` repo. Defaults to the **"my reviews"** queue (five maintainer signals — see the Inputs table); selectors narrow to one PR, an area label, or a collaborator subset. Drafts an `approve` / `request-changes` / `comment` review per PR and posts on confirmation.
- ▌ Rc Cut · apache bundleEmit the paste-ready commands to tag an RC, build the source archive reproducibly, sign, checksum and stage it to the distribution backend (or, with ASF automated signing, the tag push that triggers CI). Never runs them: the RM does, with their own key and credentials.
- ▌ Issue Invalidate · apache bundleClose a tracker as invalid: label, closing comment, board archive, and — for `<security-list>` imports — a polite-but-firm reply draft to the reporter with the team's reasoning. No reporter outreach for trackers imported from a public PR.
- ▌ Multi Agent Review · apacheFan a local diff through three independent, axis-focused review passes (correctness, security, conventions), then merge the findings into a single structured report. Each pass is isolated so one axis cannot bias another. The merged report uses the same format as pairing-self-review.
- ▌ Stack Review · apache bundleReview a GitHub stacked pull request as one unit on `<upstream>`: resolve the stack from any member PR or its stack number, check that the chain is linear and current, map every file to the layers that touch it, trace definitions removed in one layer and still used in another, and read code by tier with a coverage table instead of line by line. Drafts one rolling `COMMENT` on the lowest open layer and names the layers that deserve a `pr-management-code-review` pass. Never approves.