agentleFS
Sign inStart free
cogine-aicogine-ai/cogine-dev-skillset/skills/run-smoke-tests/SKILL.md

run-smoke-tests

Skill4 starsChanged 4 months agoApache-2.0View on GitHub

Run Playwright smoke tests, debug failures, and verify fixes

We split this skill into the rules it gives an agent

3 rules. 3 are common, 0 are distinctive, and 0 are very specific to this project.

  • 3

    Common

    Most of the 3 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Run the relevant smoke suite or a focused test file.

    line 15
  2. Common:

    If failing, inspect traces/logs and isolate the root cause.

    line 16
  3. Common:

    Prefer deterministic waits and assertions over brittle timeouts.

    line 34

“Common” is measured: kept by at least 6 in 10 of the 3 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Run smoke tests

Trigger

Need end-to-end smoke verification before or after changes.

Workflow

  1. Build prerequisites for the target app.
  2. Run the relevant smoke suite or a focused test file.
  3. If failing, inspect traces/logs and isolate the root cause.
  4. Apply a minimal fix and rerun until stable.

Example Commands

# Run full smoke suite
npm run smoketest

# Run a specific smoke test file
npm run smoketest -- path/to/test.spec.ts

# Faster iteration when build artifacts are ready
npm run smoketest-no-compile -- path/to/test.spec.ts

Guardrails

  • Prefer deterministic waits and assertions over brittle timeouts.
  • Re-run passing fixes to reduce flaky false positives.
  • Quarantine tests only when explicitly requested and documented.

Output

  • Test results summary
  • Root cause and fix
  • Remaining flake risk (if any)

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free