pr-checklist
Skill162 starsChanged 13 days agoApache-2.0View on GitHub
Run the BEEQ PR merge checklist on the current branch and report pass, fail or n/a per item: tests, stories, docs, consumer skill, PR title format. Use before marking a PR ready for review. To write the code or docs themselves use the component, test or doc skills.
9 other projects use a version of this.
Adopted by
Most recently taken up by
- guqiong96/Lvllmtheir own version, first seen Nov 9, 2026
- UMich-CURLY/claude-operating-principlestheir own version, first seen Nov 1, 2026
- ai-dynamo/dynamotheir own version, first seen Nov 1, 2026
- databricks/clitheir own version, first seen Oct 19, 2026
- SystemPanic/vllm-windowstheir own version, first seen Oct 17, 2026
- deepspeedai/DeepSpeedtheir own version, first seen Oct 17, 2026
Used with
Projects with it also use check-api-compat, ci-fails-buildkite and 6 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
vllm-projectSkillcheck-api-compat
Determine the correct behavior of vLLM's OpenAI-compatible or Anthropic-compatible API by checking the official upstream spec, instead of guessing from vLLM's own code. Use for any bug, issue, PR, review, or question touching /v1/chat/completions, /v1/completions, /v1/responses, /v1/embeddings, /v1/messages, or their request/response models — including "is this a bug or intended", "what should this field default to", "does upstream allow this", and any change that adds, removes, or renames a field on those models. Do not use for vLLM-internal APIs (engine, scheduler, LLM class) or for endpoints with no upstream counterpart.
Also in 3 projects that use this
- vllm-projectSkill
ci-fails-buildkite
Fetch and diagnose vLLM Buildkite CI failure logs. Use when investigating failing CI jobs on a PR or build, when the user pastes a buildkite.com URL, or asks to fetch/diagnose CI logs.
Also in 3 projects that use this
- +6 more from vllm-project
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- vllm-project/vllm★ 97ksame name
- deepspeedai/DeepSpeed★ 43ksame name
- open-metadata/OpenMetadata★ 16ksame name
- ai-dynamo/dynamo★ 8.5ksame name
- SystemPanic/vllm-windows★ 683same name
- guqiong96/Lvllm★ 475same name
- databricks/cli★ 427same name
- Swttch/swttch★ 302same name
- UMich-CURLY/claude-operating-principles★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- create-componentSkill
- doc-componentSkill
- fix-accessibilitySkill
- review-componentSkill
- review-docSkill
- write-e2e-testsSkill
- write-storiesSkill
- write-unit-testsSkill
- beeqSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
Check the PR title (use the argument, otherwise the latest commit message) against the PR rules and Breaking changes sections: Conventional …
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
BEEQ PR Checklist
Review the current branch against the merge checklist. The rules live in git workflow (PR merge checklist, PR rules, breaking changes). Do not restate them here.
Procedure
- List the files changed on the current branch (
git diff --name-only $(git merge-base HEAD main)). - Work through every item of the PR merge checklist in the git workflow instructions. Mark each pass, fail (with a specific reason) or n/a (with a brief justification). Typical mappings:
packages/beeq/src/shared/changed: a.spec.tsexists and was updated.- Component TSX or SCSS changed:
packages/beeq/src/components/<name>/__tests__/bq-<name>.e2e.tsxcovers the change. - Component added or
@Prop/@Eventchanged: a story exists under__storybook__/, andapps/beeq-docs/components/<name>.mdxis updated. - Public API, pattern or design rule changed:
packages/beeq-skills/src/beeq/is updated, andskills/was regenerated withpnpm skills:sync.
- Check the PR title (use the argument, otherwise the latest commit message) against the PR rules and Breaking changes sections: Conventional Commits format, type allowed by
.commitlintrc.ts, lowercase subject of at most 72 characters,!andBREAKING CHANGE:footer when breaking,[ci skip]when docs-only. - Remind the contributor to run the verification commands listed in the checklist. Do not run them yourself.
- Finish only when every checklist item and every title rule has a verdict. Output the per-item results, then a prioritised list of action points that must be fixed before merge.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.