skills.rest
AAbdulghany
AAbdulghanyCOMMUNITY
Explore all skills by this author →
𝕏@AAbdulghanyyGitHub

report-apexyard-bug

File structured upstream bug reports to the ApexYard repository.

Updated Apr 15, 2026
Search Tags:#versioning#framework#issue-tracking#bug-reporting#upstream#apexyard
One-click install
npx skills add https://github.com/AAbdulghany/fms --skill report-apexyard-bug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: report-apexyard-bug
Source: https://github.com/AAbdulghany/fms/tree/main/.claude/skills/report-apexyard-bug
Command: npx skills add https://github.com/AAbdulghany/fms --skill report-apexyard-bug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

File upstream framework bugs to the canonical ApexYard repository to improve framework quality and consistency of upstream feedback.

Core Features & Use Cases

  • Reports a framework bug to the upstream repository me2resh/apexyard.
  • Guides version capture, reproducibility, and contextual details to ensure issues are actionable.
  • Provides a safe, scrubbed workflow that avoids leaking private project information.

Quick Start

Create an upstream bug report by answering the prompts to collect a title, reproduction steps, framework context, and target upstream repository, then file it to me2resh/apexyard.

Frequently Asked Questions about report-apexyard-bug

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

FAQPage Schema
How do I report an upstream framework bug to the ApexYard repository?▼

To report an upstream framework bug, you file a structured issue to the canonical ApexYard repository, capturing version details and reproduction steps to ensure the report is actionable and auditable.

What kind of framework issues can I file using ApexYard bug reporting?▼

ApexYard bug reporting covers hook misfires, rule bugs, and documentation gaps within the apexyard framework, ensuring upstream feedback is consistently formatted and scoped to framework quality.

How do I prevent leaking private project information when filing upstream bugs?▼

To prevent leaking private project information when filing upstream bugs, the reporting workflow provides a safe, scrubbed process that strips sensitive contextual details before submitting the issue upstream.

What details do I need to capture for an actionable ApexYard framework bug report?▼

You need to capture the framework version, clear reproduction steps, and relevant contextual details to build a structured issue body that makes the ApexYard framework bug actionable.

Does the ApexYard bug reporting workflow format issues for upstream tracking?▼

Yes, the ApexYard bug reporting workflow generates a consistently formatted issue body with version capture and leak protection, designed specifically for upstream issue tracking in the canonical repository.

Related Skills

Explore More Software Engineering Skills→
salavendersalavender
47

debug

Diagnose software bugs through structured reproduction and root-cause analysis.

Community
Intermediate
AAbdulghanyAAbdulghany

request-apexyard-feature

File structured upstream feature requests for the apexyard framework.

Community
Intermediate
BrennonTWilliamsBrennonTWilliams
7

ll-verify-issues

Verify issue documentation claims against current source code.

Community
Intermediate
antondelafuenteantondelafuente

file-feedback

Submit and track feedback on automated-researcher scaffold tooling and operations.

Community
Basic