September 30, 2026
Unnecessary tests came under audit: GStack picked up the OpenClaw skill
On Sep 29, GStack received an OpenClaw test-audit skill version for analyzing tests. It finds low-value, duplicate, and implementation-coupled checks.
Garry Tan
@garrytan
Just merged an OpenClaw test-audit skill version into GStack. Bloated tests are a real problem. Fortunately, intelligence is now flowing from the tap!
· 1.5K views
Previously, the test folder grew with every task, even when a new test did not catch a new bug. Now test-audit works in three modes: it helps write a test, reviews existing ones, and runs a cleanup campaign.
Before adding a test, the skill asks 4 questions: what behavior the check protects, what regression is possible, why the current coverage does not catch it, and whether the code needs a separate seam. It accepts a deletion candidate only with 6 pieces of evidence: from the test's exact location to the command that will confirm the result.
Check after cleanup. OpenClaw instructs users to run owner and sibling tests through `node scripts/run-vitest.mjs <path-or-filter>`, then `git diff --check` and the repository's changed gate. test-audit itself is installed with `npx skills add 'https://github.com/openclaw/openclaw/tree/main/.agents/skills/test-audit'`.
For GStack, clone the repository into `~/.claude/skills/gstack`, run `./setup`, and add a rule to `AGENTS.md`. The `./setup --host openclaw` flag does not install the entire skill: it creates ACP pointers and guidance files, while the skill documentation is generated with `bun run gen:skill-docs --host openclaw`.
GStack ported the audit from OpenClaw, and the original skill already covers test writing, review, and campaigns.
Source
