Programming · Testing
03-assert
/03-assert
Assert the work behaves by iterating the project's coding assertions until they pass, plus optional architecture and frontend facets. Use to validate an implementation. Not for reviewing or writing tests.
For whom
- Author
- ai-driven-dev ↗
- Repository
- framework ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
- Files in this package
- 5
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
Deprecation
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
Licence
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Assert the work behaves by iterating the project's coding assertions until they pass, plus optional architecture and frontend facets. Use to validate an implementation. Not for reviewing or writing tests.
Arguments
/03-assert work | scope
Original author description
Assert the work behaves by iterating the project's coding assertions until they pass, plus optional architecture and frontend facets. Use to validate an implementation. Not for reviewing or writing tests.
How it works
- Actions
- Transversal rules
- Assets
Original SKILL.md headings · 27 lines, 257 words
SKILL.md preview
--- name: 03-assert description: Assert the work behaves by iterating the project's coding assertions until they pass, plus optional architecture and frontend facets. Use to validate an implementation. Not for reviewing or writing tests. argument-hint: work | scope --- # Skill: assert Validate that the work behaves as intended: run the project's assertions, iterating and fixing until they pass. ## Actions | # | Action | Facet | | --- | --------------------- | ----------------------------------------------------------- | | 01 | `assert` | Run the project's coding assertions, fixing until they pass | | 02 | `assert-architecture` | Report where the code breaks the documented architecture | | 03 | `assert-frontend` | Inspect the running UI, fixing until the behavior is right | Run every applicable facet by default, or one when named. Coding (`01`) always applies; add `03` when the work has a UI and a frontend is running, the facet resolving the URL itself; run `02` only when architecture conformance is asked for. Skip a facet whose precondition is absent, with a noted reason. Ask only when the intent is genuinely ambiguous. Before running an action, read its file in `actions/`, not only the table or assets. ## Transversal rules - Gate: it returns a pass or fail verdict on the work. - Fix loop: the coding and frontend facets fix and re-run until they pass. The architecture facet only reports, never fixes. - Stop only when every selected assertion passes a final clean sweep. - On supplied CI failures, fixing facets collect all failed checks, repair each reproducible failure locally, and rerun every applicable command in the final sweep; the caller pushes once after green if authorized, with CI-only checks unverified. ## Assets - `assets/task-template.md`: the tracking file the frontend facet fills across its fix loop.
Files in this package (5)
- SKILL.md 2 KB
- actions/01-assert.md 1 KB
- actions/02-assert-architecture.md 1 KB
- actions/03-assert-frontend.md 2 KB
- assets/task-template.md 1 KB
Versions
The database has no other skills named 03-assert.
Database snapshot: 13.11.2026 · package version 2236b9ccc5dd (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100skill-testing
AL test development patterns for Business Central. Use when creating test codeunits, writing Given/When/Then test procedures, using Library Assert, configuring test projects, or implementing TDD workflows. - 100chai
Expert Chai assertion library assistance covering Should, Expect, and Assert styles. Use when writing BDD/TDD assertions, testing JavaScript/TypeScript applications, or validating API responses. - 100assertion-strength
Use when writing or editing test assertions, and when any test diff adds skip, xfail, a try/except, a snapshot, or a looser assertion to get green. Catches assert result, assert x is not None, assertTrue(x), toBeTruthy, toBeDefined, type-only checks, assertion-free tests,… - 100mocha-assertions
Use when assertion libraries for Mocha including Chai with expect, should, and assert styles. - 100overfit-assertion-quality
Analyzes the variety and depth of assertions across test suites in any language. Use when the user asks to evaluate assertion quality, find shallow testing, identify assertion-free tests (no assertions or only trivial ones like Assert.IsNotNull / expect(x).toBeTruthy() / assert… - 95nunit-skill
Generates NUnit 3 tests in C#. Covers Assert.That constraint model, parameterized tests, setup/teardown, and Moq mocking. Use when user mentions "NUnit", "[TestFixture]", "[Test]", "Assert.That", "C# unit test". Triggers on: "NUnit", "[Test]", "Assert.That", "C# test", "NUnit3".