upstream-first

Solid

Load this skill before implementing a fix for a barrier that may originate in a shared component, design system, renderer, or external dependency rather than this project's own code. Decide whether the responsible fix is local, an existing installed capability, or an upstream contribution before writing a workaround. Absolutely always record any temporary local divergence with an owner and removal condition. Under no circumstances open, comment on, or submit anything in an external project without explicit human approval.

AI & Automation 44 stars 2 forks Updated 2 days ago AGPL-3.0

Install

View on GitHub

Quality Score: 81/100

Stars 20%
55
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Upstream First Skill This skill is a pointer to [mgifford/upstream-first](https://github.com/mgifford/upstream-first), a separate, standalone set of agent skills for deciding where an accessibility (or any other) fix belongs and preparing it for the receiving project. It does not restate that project's decision hierarchy, classification steps, or contribution workflow — those stay owned there so this skill does not drift out of sync with a project that is still a pre-release review draft. ## When to Use This Before implementing a fix for an accessibility barrier, check whether the affected code is actually owned by this project: - a shared component or design system used across multiple projects; - a renderer, framework, or platform dependency; - an npm/PyPI/Packagist/Composer package rather than first-party code; - a pattern that would benefit other consumers of the same dependency, not only this project. If the barrier may originate outside this project's own code, load [`upstream-first`](https://github.com/mgifford/upstream-first/blob/main/skills/upstream-first/SKILL.md) to decide whether the responsible fix is: 1. an existing installed capability; 2. an existing public API or extension point; 3. a suitable maintained open-source package; 4. a focused contribution to an existing project; 5. a new reusable open-source package with credible ownership; or 6. a local implementation, with a written justification for why every higher option is unsuitable. Do not de...

Details

Author
mgifford
Repository
mgifford/accessibility-skills
Created
5 months ago
Last Updated
2 days ago
Language
JavaScript
License
AGPL-3.0

Similar Skills

Semantically similar based on skill content — not just same category

Web & Frontend Listed

checking-upstream-first

Before writing a custom fix for a framework- or library-level problem, verifies that the current version does not already solve it. Covers the version actually resolved vs. the current one, reading the dependency's own code in node_modules, release notes and issue tracker, and whether an lt base repo already solved it. Activates whenever a workaround, shim, patch, wrapper, polyfill or guard is about to be built around a dependency's behaviour, and on "workaround", "patchen", "wir bauen uns das selbst", "eigene Lösung". NOT for feature work the dependency was never meant to cover. NOT for routine version bumps (use maintaining-npm-packages).

0 Updated 3 days ago
lenneTech
AI & Automation Listed

check-upstream-first

Use before debugging a framework or dependency bug from its source, and before writing any local patch. Establishes which install and version is actually running, then searches the project's issue tracker and release notes for an existing fix. Prevents the common waste of hand-patching a source tree that nothing executes, or shipping a fix for a bug that was resolved weeks ago.

0 Updated 2 days ago
TechNickAI
AI & Automation Solid

magpie-issue-fix-workflow

For a single triaged `<issue-tracker>` issue confirmed as a bug or feature, draft a fix against `<upstream>` on `<default-branch>`. Produces the failing test, the smallest production change, the targeted+module test runs, and the commit. The PR is NOT opened on autopilot; the human committer reviews, signs, and pushes. Hand-back artefact summarises branch, commits, test results, and scope.

91 Updated today
apache