run-tests
Skill682 starsChanged 6 days agoMITView on GitHub
Use when writing/running tests, interpreting coverage, or checking documented behavior against Make targets, quality gates and validation claims in personal-os-setup.
50 other projects use a version of this.
Adopted by
Most recently taken up by
- tatsoft-llc/FrameworX-Projectstheir own version, first seen Nov 15, 2026
- wisterx-spec/agent-railstheir own version, first seen Nov 15, 2026
- 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
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
SentrySkillcommit
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 4 projects that use this
Other versions50 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 50
- 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.3ksame name
- ComplianceAsCode/content★ 2.8ksame name
- idaholab/moose★ 2.4ksame name
- CliMA/Oceananigans.jl★ 1.5ksame name
- serenedb/serenedb★ 1.1ksame name
- microsoft/testfx★ 1.1ksame name
40 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 repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- add-system-actionSkill
- chezmoi-scriptsSkill
- docs-siteSkill
- fork-and-customizeSkill
- ship-featureSkill
- vm-labSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 45 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Read docs/developer/4.testing.md for the test suites and current targets.
- Very specific: line 36
Use tmp_path and monkeypatch.
- Distinctive: line 48
Never run either without explicit authorization.
“Common” is measured: kept by at least 6 in 10 of the 45 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
Testing in personal-os-setup
Read docs/developer/4.testing.md for the test suites and current targets.
Safe local checks
make test-localrunstests/unitandtests/skillswith xdist (N=4, orN=1for debugging). Plainpytesthas the same safe testpaths. Empty collection fails.make test-alladds real wheel/sdist identity/resource checks and isolated wheel installation. The console callable loads without starting the app (startup can self-update and prepare sudo).make test-coveragereusestest-allwith separate Python coverage inreports/coverage.xml. Coverage does not establish OS integration completeness; no threshold is imposed yet.make checkrunspre-commit-status(hook warning), static/docs hooks,test-allanddocs-build.make install-devprepares the environment and the Git hooks; checks never install them.
Full validation targets reject ARGS and PYTEST_ADDOPTS. Use
make test-local ARGS="-k release" for focused debugging, including collection-only runs.
Isolation conventions
- Patch at the import site: frontend chezmoi functions at
personal_os_setup.frontend.app.chezmoi_*, managers atpersonal_os_setup.tasks.managers.<backend>.run/sudo_non_interactive_ok.shutil.whichis patched globally because managers access it through that module. - Frontend tests live in
tests/unit/frontend; its shared autouse fixture supplies a synthetic catalog, sections and managed paths, and fails on unexpected real manager/chezmoi actions. Override only the calls a test intentionally exercises. Never wire tests to real system actions. - Fake results with
TaskResult,InstallResultorMagicMock(returncode=..., stdout=..., stderr=...). Usetmp_pathandmonkeypatch; xdist workers must share no mutable state. - Textual async tests need
pytest.mark.asyncioin strict mode. Pollapp.is_busywith Pilot pauses for thread workers, and find dynamic TabPanes through a known child rather than fixed generated IDs. - Settings tests set environment values and reload the settings module; values are read at import.
- Release regressions use explicit Git/uv/Make/GitHub stubs. Docs generators use temporary source/output trees; integration-report tests launch pytest only against synthetic modules.
tests/skillsdeploys into temporary roots with a fake installer. POSIX Bash/jq are required; its chezmoi case skips when absent, and native Windows skips the POSIX harness.
OS validation boundary
make test-integration and tests/archlinux can run real host-mutating commands on Linux/macOS.
Never run either without explicit authorization; a generic request to test means safe local suites.
Windows integration is deliberately read-only.
Hosted CI requires self-contained tests and executed integration on Ubuntu/macOS/Windows.
Other operating systems' skips are expected, but zero passing integration tests, deselection and
collection-only runs fail through scripts/integration_results.py.
CachyOS integration is not exercised by hosted CI; the Arch container is an interactive sandbox.
A local make check pass does not establish that required CI passed.
Tooling boundaries and gate gotchas
- Bare
makeshows help.make install-uvinstalls only when missing;make update-uvupdates.make install-prod= runtime deps only;make install-dev= tools + Git hooks (pre-commit-installrepeats,pre-commit-statuschecks). make pre-commitruns prepared tools without sync or hook install. New untracked files needmake pre-commit FILES="<paths>";--all-filessees only tracked files.- The strict docs hook calls
make docs-build. Installation smoke checks a real isolated wheel and loads thepersonal-os-setupcallable without starting the app; artifact checks also need matching sdist metadata/resources. - actionlint and zizmor are enabled; pip-audit, bandit and markdown-link-check remain commented out in
.pre-commit-config.yaml. - commitizen runs only at the
commit-msgstage — a green pre-commit says nothing about message format. - detect-secrets is stateless: allowlist false positives inline, never whole-file. Existing exclusions cover only generated payload/lock content and binary artifacts.
- Formatting hooks can rewrite files and fail the first run — recheck final content.
properdocs.ymlusesdocs_dir: .— new top-level output dirs need an exclude entry (see [[docs-site]]).packages.yamlmanager registrations are checked bytests/unit/test_detect_os.py::TestPackagesYaml.- CI releases from
main(stable) anddev(rc) bind to the tested revision; localmake releaseusesHEAD; interrupted tag/version publication can resume verified asset uploads (see the release guide). make actmay mutate its execution environment — not atest-localreplacement.tests/archlinuxis a manual interactive sandbox, not CachyOS validation.
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.

