agentleFS
theinternetitheinterneti/TTA.dev/.claude/skills/build-test-verify/SKILL.md

build-test-verify

Skill0 starsChanged 7 months agoMITView on GitHub

Use this skill when asked to build the project, run tests, lint the code, or verify that the TTA.dev platform is stable before committing.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 4 are distinctive, and 3 are 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.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If CGC is unavailable, note it and proceed.

    line 20
  2. Distinctive:

    Lint: Run Ruff linter with auto-fix.

    line 27
  3. Distinctive:

    Type Check: Run Pyright in basic mode.

    line 32
  4. Distinctive:

    If E2B is unavailable, fall back to local pytest and note the deviation.

    line 59
  5. Very specific:

    Retain: after a successful commit, call mcp__hindsight__retain with bank_id tta-dev documenting any decision, pattern, or failure from this …

    line 61
  6. Very specific:

    Type errors: Ensure all new functions have strict type annotations (str | None, not Optional[str]).

    line 66
  7. Very specific:

    Import errors: All primitives imports must use from ttadev.primitives.X — never from primitives.X.

    line 68

≈ “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

Build, Test, and Verify (TTA.dev)

Validate code changes to ensure they meet quality standards before committing.

Process

Execute the following steps in order. Do not skip steps.

  1. Orient (before writing any code): query CGC for the target.
    mcp__codegraphcontext__find_code — search for the target function/class
    mcp__codegraphcontext__analyze_code_relationships — callers, dependencies
    mcp__codegraphcontext__calculate_cyclomatic_complexity — risk level
    If CGC is unavailable, note it and proceed. Do not block on CGC absence.
  2. Format: Apply Ruff formatting (100-char line length).
    uv run ruff format .
  3. Lint: Run Ruff linter with auto-fix.
    uv run ruff check . --fix
  4. Type Check: Run Pyright in basic mode.
    uvx pyright ttadev/
  5. Run Tests: Execute the pytest suite (100% coverage required for new code).
    uv run pytest -v --tb=short -m "not integration and not slow and not external"
  6. Full coverage (when adding new code):
    uv run pytest --cov=ttadev --cov-report=html
  7. Validate in E2B (when adding or changing Python code): run the tests identified in the Orient step inside a clean E2B sandbox.
    from ttadev.primitives.integrations.e2b_primitive import CodeExecutionPrimitive
    from ttadev.primitives.core.base import WorkflowContext
    
    async with CodeExecutionPrimitive() as executor:
        result = await executor.execute({
            "code": "import subprocess; r = subprocess.run(['python', '-m', 'pytest', '<test_file>', '-v', '--tb=short'], capture_output=True, text=True); print(r.stdout); print(r.stderr)"
        }, WorkflowContext(workflow_id="validate"))
        # Check result["success"] and result["output"] for PASSED/FAILED
    If E2B is unavailable, fall back to local pytest and note the deviation.
  8. Retain: after a successful commit, call mcp__hindsight__retain with bank_id tta-dev documenting any decision, pattern, or failure from this task.

Common Issues

  • Type errors: Ensure all new functions have strict type annotations (str | None, not Optional[str]).
  • Test failures: Fix the implementation, never comment out tests. Follow the AAA pattern (Arrange-Act-Assert).
  • Import errors: All primitives imports must use from ttadev.primitives.X — never from primitives.X.
  • Quarantined tests: Tests marked @pytest.mark.quarantine are auto-skipped unless selected with -m quarantine.

Deep Reference

For full testing patterns, markers, CI pipeline details, and MockPrimitive API, see docs/agent-guides/testing-architecture.md.

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.