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

request-apexyard-feature

File structured upstream feature requests for the apexyard framework.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structured governance for framework improvements by routing requests to the upstream ApexYard repository, ensuring visibility, consistency, and collaboration across projects.

Core Features & Use Cases

  • Upstream framing: propose enhancements to the apexyard framework itself (hooks, rules, or workflows) rather than changes to a single project.
  • Guided process: capture problem, proposed behavior, benefits, scope, and related items to provide complete context.
  • Upstream filing: always file the issue in the canonical me2resh/apexyard repository and track progress there.
  • Use Case: a team wants a new framework hook and drafts a structured upstream issue to request it upstream.

Quick Start

Submit a concise description of the desired upstream feature; file it against the me2resh/apexyard repository using the guided prompts.

Frequently Asked Questions about request-apexyard-feature

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

FAQPage Schema
How do I file an upstream feature request for the apexyard framework?▼

To file an apexyard feature request, you provide a concise description of the desired enhancement. The process guides you through defining the problem, proposed behavior, and benefits before submitting the issue to the canonical me2resh/apexyard repository.

What information do I need to include in an apexyard framework upstream issue?▼

An apexyard upstream issue requires the problem description, proposed behavior, benefits, scope, related items, and the current framework version. This structured context ensures visibility and consistency for collaborative framework governance.

Can I propose a new hook for the apexyard framework instead of changing my local project?▼

Yes, you can propose new apexyard framework hooks, rules, or workflows. The process focuses strictly on upstream framing, routing enhancement requests to the canonical repository rather than modifying a single local project.

How does the guided process for creating apexyard upstream issues work?▼

The guided process for apexyard upstream issues follows a one-question-at-a-time flow. It sequentially captures the problem, proposed behavior, and benefits, requiring explicit confirmation before filing the issue in the canonical repository.

Where are apexyard upstream feature requests tracked after submission?▼

Apexyard upstream feature requests are filed and tracked in the canonical me2resh/apexyard GitHub repository. This ensures structured governance, visibility, and collaboration across all projects using the framework.

Related Skills

Explore More Software Engineering Skills→
AAbdulghanyAAbdulghany

report-apexyard-bug

File structured upstream bug reports to the ApexYard repository.

Community
Advanced
gittowergittower
413

triage

Classify GitHub issues and discussions, find duplicates, and draft triage verdicts.

Official
Advanced
lluppesmslluppesms

create-github-issue-feature-from-specification

Create or update GitHub issues from specification files with duplicate checks.

Community
Intermediate
me2reshme2resh
489

release-sync

Create a main-to-dev PR with `-X ours` after a squash-merge release.

Community
Advanced