agentleFS
Sign inStart free
osocietyosociety/vernet/.github/skills/flutter-test-repair/SKILL.md

flutter-test-repair

Skill566 starsChanged 14 days agoApache-2.0View on GitHub

Fix Flutter or Dart unit, widget, and integration-test failures, including CI failures, emulator/device setup, plugin behavior, permissions, and platform-specific test issues.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    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
  1. Very specific:

    Use this when a Vernet test fails locally or in CI, or when configuring an existing unit, widget, or integration-test workflow.

    line 9
  2. Distinctive:

    If the failure is environmental, report the concrete blocker and the strongest test that did pass.

    line 18
  3. Distinctive:

    Keep networking in services and UI tests focused on visible behavior.

    line 22
  4. Distinctive:

    Treat database lifecycle and cleanup as concurrency concerns.

    line 24
  5. Distinctive:

    After Dart/Flutter code changes, hot reload or hot restart an attached app when one is available.

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Flutter Test Repair

Use this when a Vernet test fails locally or in CI, or when configuring an existing unit, widget, or integration-test workflow.

Procedure

  1. Identify the exact failing test, command, platform, and first project-owned stack frame. For CI failures, inspect the job log and workflow before assuming the test itself is defective. If a recent fix made a previously skipped path run, suspect a latent test bug rather than a regression, and compare against the last green run before changing production code.
  2. Classify the test as unit, widget, or integration. Read the nearest test and implementation; for app structure or ownership questions, use the repository graph when present and consult ARCHITECTURE.md for structural changes.
  3. Reproduce with the narrowest exact command. Check the available Flutter devices before running device-dependent tests. For plugin, notification, network, or permission failures, separate unsupported test-environment behavior from a production defect and use deterministic fakes where appropriate.
  4. Make one focused change and add or update a regression assertion for the failure. Preserve the existing test architecture and avoid weakening assertions, adding timing sleeps, or depending on live DNS/network state.
  5. Immediately rerun the exact failing test. Then run flutter analyze for affected Dart changes. Use the repository's established integration-test command and an available device; do not claim device or platform coverage that was not run.
  6. If the failure is environmental, report the concrete blocker and the strongest test that did pass; do not mask it with broad catches or unrelated code changes.

Vernet-specific checks

  • Keep networking in services and UI tests focused on visible behavior.
  • Guard native plugin calls in tests where the platform implementation is unavailable.
  • Treat database lifecycle and cleanup as concurrency concerns; avoid parallel tests that share the same SQLite database.
  • After Dart/Flutter code changes, hot reload or hot restart an attached app when one is available.

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