contributing
/contributing
Guides a change to GridSelect from issue to pull request so it meets the project's standards (tests first, browser tests, accessibility, README and CHANGELOG, size budget, no version bumps). Use when contributing to this repository, fixing a bug, adding a feature or theme, or preparing a pull request.
- Author
- emmgeede ↗
- Repository
- gridselect ↗
- Licence
- MIT
- Last repository change
- 10.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 10.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Guides a change to GridSelect from issue to pull request so it meets the project's standards (tests first, browser tests, accessibility, README and CHANGELOG, size budget, no version bumps). Use when contributing to this repository, fixing a bug, adding a feature or theme, or preparing a pull request.
Original author description
Guides a change to GridSelect from issue to pull request so it meets the project's standards (tests first, browser tests, accessibility, README and CHANGELOG, size budget, no version bumps). Use when contributing to this repository, fixing a bug, adding a feature or theme, or preparing a pull request.
How it works
- 1. Understand before changing
- 2. Plan the smallest change
- 3. Test first, in slices
- 4. Docs in the same change
- 5. Verify
- 6. Hand over
SKILL.md preview
--- name: contributing description: Guides a change to GridSelect from issue to pull request so it meets the project's standards (tests first, browser tests, accessibility, README and CHANGELOG, size budget, no version bumps). Use when contributing to this repository, fixing a bug, adding a feature or theme, or preparing a pull request. --- # Contributing to GridSelect Follow `AGENTS.md` in the repository root; it is the source of truth. Themes also follow `CONTRIBUTING.md`. This skill is the order of work. ## 1. Understand before changing - Read `AGENTS.md` and, for themes, `CONTRIBUTING.md`. - Find the issue this change belongs to. If there is none and the change is more than a typo, stop and help the user open one (problem, proposal, alternatives) and wait for a maintainer. Do not start building unagreed features. - Read the code the change touches and its tests. Reuse what is there before writing new code. ## 2. Plan the smallest change - State in one or two sentences what changes for users and which public seam shows it (an option, an attribute, the DOM, a key, an announcement). - Check the principles: native inputs, data attributes for structure, ARIA for state, WCAG 2.2 AA, no dependencies, size budget. If the change cannot meet one of them, tell the user and suggest raising it in the issue. ## 3. Test first, in slices For each behaviour: 1. Write one failing test through the public API (`test/*.test.js`). Run it and confirm it fails for the right reason. 2. Write the smallest code that passes. Comments in English. 3. Layout, visibility, focus or real keys: add the variant to `playground/index.html` and a Playwright test in `e2e/`, including axe where it is a visible state. ## 4. Docs in the same change - Documentation in `website/`: the feature's guide page (with a live `<Example>`) and the reference tables. README only when the overview changes; keep its Contents list in sync with the headings. - CHANGELOG: an entry under `## [Unreleased]` in the right section. - Never touch the version, tags, released CHANGELOG sections, `docs/` or `CLAUDE.md`. ## 5. Verify Run and fix until all pass: ```sh npm test npm run test:e2e node scripts/pr-check.js ``` If the size test fails, do not raise the limit; shrink the change or explain the need in the pull request. ## 6. Hand over - Commit with `feat: …`, `fix: …`, `docs: …`, `test: …` or `chore: …`. - Draft the pull request text from `.github/pull_request_template.md`: what and why, the issue (`Closes #…`), how it was tested, the checklist ticked honestly. Show it to the user before they open the pull request.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · emmgeede/gridselect | 100 | MIT |
| butterbase-ai/butterbase-skills | 100 | MIT |
| cloudflare/cloudflare-docs | 100 | CC-BY-4.0 |
| blaizzy/mlx-vlm | 100 | MIT |
| Jeff-Kazzee/github-skills | 100 | MIT |
| googlecloudplatform/race-condition | 100 | Apache-2.0 |
| Dqz00116/skill-lib | 100 | MIT |
| iowarp/clio-core | 84 | BSD-3-Clause |
Database snapshot: 13.11.2026 · package version 1e1a171187c9 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90readme-and-co:documentation-standards
This skill should be used when creating README files, CONTRIBUTING guides, SUPPORT documentation, or any core repository documentation. Triggers when user asks to "create a README", "write documentation", "generate CONTRIBUTING", "add support docs", or discusses repository… - 100docs
This skill should be used when the user asks about "documentation", "README", "CHANGELOG", "CONTRIBUTING", "ADR", "architecture decision record", "changelog format", "keep a changelog", "doc comments", "API documentation", or needs guidance on project documentation requirements. - 100pitchdocs-suite
One-command generation and audit of the full public repository documentation set — README, CHANGELOG, ROADMAP, CONTRIBUTING, CODE_OF_CONDUCT, SECURITY, issue templates, PR template, and discussion templates. Use when setting up a new repo or auditing an existing one. - 90contributing-changes
Use when preparing a change for the tycoon-cli repo: choosing which branch to target, opening a PR, updating the changelog, or when CI behaves differently than expected because workflow config differs between main and the release branch. - 100polestar-contributing
The rules for working on the Polestar repository (the WoW Forever leveling guide addon, fitzforge/polestar) for a contributor - checking that no one else is already fixing an issue, that every pull request goes to next, linking the issue, generated files, changelog fragments,… - 100documentation-guide
Guide documentation structure, content requirements, and project documentation best practices. Use when: creating README, documentation, docs folder, project setup, technical docs. Not for: generating docs mechanically from source — use /docgen; changelog entries — use…