build-test-verify
Skill0 starsChanged 7 months agoMITView on GitHub
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.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- bitwarden/iostheir own version, first seen Oct 8, 2026
- bitwarden/androidtheir own version, first seen Oct 8, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- bitwarden/android★ 9.6ksame name
- bitwarden/ios★ 731same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/tta-dev.mdcCursor rule
- build-test-verifySkill
- core-conventionsSkill
- create-atomic-noteSkill
- create-pull-requestSkill
- git-commitSkill
- sdd-workflowSkill
- self-review-checklistSkill
- session-startSkill
- core-conventionsSkill
- create-agentSkill
- create-atomic-noteSkill
- create-pull-requestSkill
- Feature DevelopmentSkill
- git-commitSkill
- Incident ResponseSkill
- Package ReleaseSkill
- sdd-workflowSkill
- self-review-checklistSkill
- session-startSkill
- ttadev-llmSkill
- ttadev-primitivesSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Use available code analysis tools if configured.
- Distinctive: line 23
Lint: Run Ruff linter with auto-fix.
- Distinctive: line 28
Type Check: Run Pyright in basic mode.
- Very specific: line 49
Type errors: Ensure all new functions have strict type annotations (str | None, not Optional[str]).
- Very specific: line 51
Import errors: All primitives imports must use from ttadev.primitives.X — never from primitives.X.
≈ “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.
Files
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, notOptional[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— neverfrom primitives.X. - Quarantined tests: Tests marked
@pytest.mark.quarantineare 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.
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
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.