Build test verify

Skill theinterneti/TTA.dev/.github/skills/build-test-verify

AI devops for vibe coders

Install

npx -y skills add theinterneti/TTA.dev --skill build-test-verify

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use this skill when asked to build the project, run tests, lint the code, check types, or verify that the TTA.dev platform is stable before committing. Invoke when the user says "run tests", "check quality", "lint", "format", "verify", or before any commit or PR.

SKILL.md

2.2 KB, as published. Nobody here has run it

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.

Orient (before writing any code): search the codebase for the target function/class, analyze its callers and dependencies, and assess complexity/risk level. Use available code analysis tools if configured; otherwise proceed with manual review.
Format: Apply Ruff formatting (100-char line length).
```
uv run ruff format .
```
Lint: Run Ruff linter with auto-fix.
```
uv run ruff check . --fix
```
Type Check: Run Pyright in basic mode.
```
uvx pyright ttadev/
```

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"

Full coverage (when adding new code):

uv run pytest --cov=ttadev --cov-report=html

Validate in sandbox (when adding or changing Python code): run the identified tests inside a clean sandbox environment if available (e.g. E2B). If unavailable, fall back to local pytest and note the deviation.

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.

Gives 0 of the 12 instructions most quality gates skills give

Counted across 1,195 of the 2,094 authors here whose files we hold, read 2026-08-06

read the output and check the exit codein 55 of 1195, across 14 files
verify requirements using a line-by-line checklistin 53 of 1195, across 12 files
identify the verification command proving the claimin 53 of 1195, across 12 files
run the full verification commandin 51 of 1195, across 11 files
verify output confirms the claimin 49 of 1195, across 10 files
check version control diff after agent delegationin 45 of 1195, across 5 files
state claim with evidencein 43 of 1195, across 3 files
run the test suitein 32 of 1195, across 24 files
keep state in memory by defaultin 27 of 1195, across 6 files
make prototype runnable with one commandin 26 of 1195, across 5 files
detect the package manager from lockfilesin 24 of 1195, across 5 files
produce a verification reportin 23 of 1195, across 12 files

Said here and by no other author read

orient before writing any code
apply formatting with 100-character line length
run the test suite excluding integration tests
generate full coverage report for new code
validate new code in a sandbox environment
add strict type annotations to all new functions

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.