run-tests
Skill0 starsChanged 6 months agoMITView on GitHub
Validate the current project and build a fresh place file. Use when the user wants to run /run-tests from a Bloxkit repo or project.
48 other projects use a version of this.
Adopted by
Most recently taken up by
- utopia-rise/fmod-gdextensiontheir own version, first seen Nov 9, 2026
- Pubx-ai/skillstheir own version, first seen Nov 8, 2026
- coralogix/cx-clitheir own version, first seen Nov 8, 2026
- DataDog/dd-trace-pytheir own version, first seen Nov 1, 2026
- busycaesar/Harnesstheir own version, first seen Nov 1, 2026
- NumericalEarth/Breeze.jltheir own version, first seen Oct 17, 2026
Used with
Projects with it also use prepare-release, create-pr and 3 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.
ShopifySkillprepare-release
Prepare the changeset-release/main branch for release by syncing version.ts files and running pnpm install
Also in 3 projects that use this
SentrySkillcreate-pr
Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.
Also in 4 projects that use this
- SentrySkill
commit
Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.
Also in 4 projects that use this
MicrosoftSkillrelease
Use ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version. Performs an outward action — bumps the version in apps/desktop/package.json, commits + annotated-tags vX.Y.Z, and pushes the branch + tag. That tag push auto-builds the macOS/Windows installers and publishes a GitHub Release. Provides `status`, `bump`, `tag-push`, and a one-command `run` (bump → tag-push).
Also in 5 projects that use this
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 5 projects that use this
Other versions48 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 48
- netbox-community/netbox★ 22ksame name
- yagop/node-telegram-bot-api★ 9.2ksame name
- gitextensions/gitextensions★ 8.6ksame name
- ethereum/consensus-specs★ 4ksame name
- dotnet/sdk★ 3.2ksame name
- ComplianceAsCode/content★ 2.8ksame name
- idaholab/moose★ 2.4ksame name
- CliMA/Oceananigans.jl★ 1.4ksame name
- microsoft/testfx★ 1.1ksame name
- serenedb/serenedb★ 965same name
38 more not listed
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 repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- add-placeSkill
- adopt-projectSkill
- buildSkill
- doctorSkill
- fix-myselfSkill
- new-featureSkill
- new-gameSkill
- new-placeSkill
- persistence-proofSkill
- runtimeSkill
- serveSkill
- setup-new-gameSkill
- setupSkill
- testSkill
- travel-proofSkill
- ui-add-daily-rewardsSkill
- ui-add-hudSkill
- ui-add-inventorySkill
- ui-add-leaderboardSkill
- ui-add-popupSkill
- ui-add-quest-logSkill
- ui-add-settingsSkill
- ui-add-shopSkill
- ui-add-upgrade-menuSkill
- ui-previewSkill
- uiSkill
- upgrade-projectSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 44 edited versions we read keep these.
2
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
- Distinctive: line 8
Use the shared Bloxkit workflow runner instead of rebuilding this flow manually.
- Very specific: line 13
Run node toolkit-v2/scripts/command-runner.mjs /run-tests with any user arguments filled in.
- Distinctive: line 14
Do not substitute lower-level scripts unless you are debugging the shared workflow.
“Common” is measured: kept by at least 6 in 10 of the 44 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
/run-tests
Use the shared Bloxkit workflow runner instead of rebuilding this flow manually.
Workflow:
- Confirm you are in the current Bloxkit project root.
- Run
node toolkit-v2/scripts/command-runner.mjs /run-testswith any user arguments filled in. - Do not substitute lower-level scripts unless you are debugging the shared workflow.
- Return the command summary, changed artifacts, and any remaining manual Studio or MCP steps.
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.