Index of every page on this site: llms.txt
All skills
dominiktobureto avatar

/tdd-test-engineer

@9125e02
Run it yourself

Use for test-first development, regression tests, flaky test debugging, coverage gaps, test strategy, CI failures, or converting bugs into minimal reproducible tests.

Use this Skill: https://skilld.dev/gh/dominiktobureto/awesome-grok-build/tdd-test-engineer

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈46 tokens for metadata: the name and description. ≈359 when used: this file.

Description uses 2.3% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈186 characters, or 2.3%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

TDD Test Engineer

Make behavior executable before changing implementation.

Grok Build Mode

  • Use Plan Mode for new test strategy, broad CI changes, or uncertain behavior.
  • Use subagents for test work:
    • behavior: expected behavior and edge cases.
    • fixtures: setup/data/mocking strategy.
    • failure: reproduce current bug or CI failure.
    • coverage: missing test surfaces.
  • Arena-style test design: compare several test strategies and choose the smallest test that proves the behavior.
  • Human-in-the-loop: get approval before deleting or weakening tests.

Workflow

  1. Identify the behavior or bug.
  2. Find existing test style and commands.
  3. Write or propose a failing test first.
  4. Run the narrow test and capture failure.
  5. Implement the smallest fix.
  6. Re-run the narrow test, then broader checks if cheap.
  7. Summarize the regression protected.

Test Quality Rules

  • Prefer behavior assertions over implementation details.
  • Avoid sleeps; use deterministic waiting or mocks.
  • Keep fixtures small.
  • Do not snapshot volatile output without normalization.
  • Do not remove failing tests unless they are invalid and the user approves.

Example Prompts

Use tdd-test-engineer. Add a failing regression test for this bug before fixing it.
Use subagents to inspect flaky test causes: timing, shared state, network, fixture leakage. Propose the smallest deterministic fix.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts4mo3 checks · Risk SAFE
  • Gen Agent Trust Hub4mo

    This skill is a standard engineering assistant designed for Test-Driven Development (TDD). It provides instructions for creating regression tests and debugging flaky tests without any detected malicious patterns, unauthorized data access, or remote code execution.

  • Socket4mo

    No alerts

  • Snyk4mo

    Risk: LOW · No issues

Signed by skilld at 9125e02. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Steadyupdated 6 months ago
version
1.0.0
author
awesome-grok-build

README badge

README badge for dominiktobureto/awesome-grok-build/tdd-test-engineer