skills.rest
mastra-ai
mastra-aiOFFICIAL
Explore all skills by this author →
Website𝕏@mastraGitHub

label-core-bugs

Review open GitHub issues and apply the @mastra/core label to direct core bugs.

27.6k|2.7k|Updated Aug 6, 2024
Search Tags:#issue triage#gh CLI#gitHub#code ownership#bug classification#Mastra#Labeling
One-click install
npx skills add https://github.com/mastra-ai/mastra --skill label-core-bugs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: label-core-bugs
Source: https://github.com/mastra-ai/mastra/tree/main/.mastracode/skills/label-core-bugs
Command: npx skills add https://github.com/mastra-ai/mastra --skill label-core-bugs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintainers of the mastra-ai/mastra repository need a consistent, auditable way to identify which open issues are direct bugs in the @mastra/core package, so core ownership is tracked without mislabeling issues owned by other packages.

Core Features & Use Cases

  • Issue Classification: Fetches open issues via the GitHub CLI, traces reported behavior to concrete code in packages/core, and labels only confirmed direct core bugs.
  • Ownership Verification: Excludes issues owned by memory/storage adapters, client-js, server, deployers, CLI, integrations, docs, and other non-core areas, reporting uncertain cases instead of guessing.
  • Dry-Run and Sweep Modes: Supports --all sweeps, specific issue numbers or URLs, and --dry-run for read-only audits that never mutate GitHub state.
  • Use Case: Run a periodic reconciliation pass over all open issues to ensure the @mastra/core label accurately reflects current core bugs, grouping results by unclaimed, stale claim, active PR, or fixed-awaiting-closure.

Quick Start

Review all open mastra-ai/mastra issues in dry-run mode and report which ones are direct @mastra/core bugs.

Frequently Asked Questions about label-core-bugs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I label GitHub issues that are core package bugs?▼

Fetch each open issue with the GitHub CLI, trace the reported API or error to concrete code in packages/core, and add the @mastra/core label only when the primary fix belongs in core. Verify the label was applied after each edit.

How do I audit issue labels without changing anything on GitHub?▼

Run the review with the --dry-run flag, which performs the full classification and reports decisions without creating labels or editing issues. A dry run never mutates GitHub state.

What counts as a direct @mastra/core bug?▼

An issue qualifies only if it reports broken existing behavior and the primary fix belongs in packages/core, such as agent execution, workflows, tools, streaming, or core schemas. A core stack frame or mention of core alone is not sufficient evidence.

Which issues should not get the @mastra/core label?▼

Exclude issues owned by memory/storage adapters, client-js, server/auth, Studio, deployers, CLI tooling, integrations, docs, examples, and repository infrastructure. Mixed or uncertain ownership should be skipped and reported as uncertain.

What happens if an issue was already fixed by a merged PR?▼

The issue is reported as fixed-awaiting-closure with evidence linking the merged pull request. The skill never closes issues, removes labels, or comments on them.

Related Skills

Explore More Software Engineering Skills→
howellshowells
2

mastraudit

Audit JavaScript and TypeScript repositories for Mastra implementation correctness and structural boundaries.

Community
Advanced
FutureAtomsFutureAtoms
1

git-github-pr-triage

Prioritize GitHub pull requests with a priority matrix and triage labels.

Community
Advanced
jaminitachijaminitachi
1

dev-workflow

Gather data from GitHub, CI, error tracking, and local git to generate consolidated reports.

Community
Advanced
BluMintIncBluMintInc
2

repo-maintenance

Automate triaging, labeling, and maintenance workflows for the eslint-custom-rules repository.

Official
Advanced