Skip to main content
skill CX Codex

03-assert — Claude Code skill: what it does, how to install

03-assert runs a project's assertions and fixes code until they pass, with optional checks on architecture and a running UI. Useful as the last gate before you push.

MIT ★ 571 updated 2026-10-29

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add ai-driven-dev/framework
/plugin install aidd-dev@aidd-framework
Open on GitHub

What 03-assert does

The skill runs a project's own assertions and edits code until they pass. You get a pass or fail verdict on the work. Every applicable facet runs by default: assert (coding) always, assert-frontend when the work has a UI and a frontend is up (it resolves the URL itself), assert-architecture only when conformance is requested.

What each facet does with a failure differs. Coding and frontend fix and re-run until green. Architecture only names the places where code drifts from the documented architecture; it never patches anything, so don't wait for a fix from it. A facet whose precondition is missing gets skipped with a reason recorded. Before an action runs, the skill reads that action's file under actions/, not just the table.

The frontend facet keeps assets/task-template.md updated through its fix loop. Hand it failing CI checks and the fixing facets gather every failed check, repair each reproducible one locally, then repeat all applicable commands in the final sweep. Pushing stays with the caller, and only after green. Checks that live only in CI stay unverified.

What it helps with

  • drive failing project assertions back to green
  • find where code drifted from the documented architecture
  • check a running UI and fix the behaviour that is off
  • work through a batch of failed CI checks locally
  • get a clear pass or fail verdict on the work

Example prompts for the agent

  • Run 03-assert on the changes in src/api and keep going until the assertions pass.
  • Validate the work in src/components with the frontend facet; the UI is already running.
  • Run 03-assert with assert-architecture and tell me where the code breaks the documented design.

How to install 03-assert

1Plugin marketplace

/plugin marketplace add ai-driven-dev/framework
/plugin install aidd-dev@aidd-framework

This installs the whole aidd-dev plugin with all its skills

2Skills CLI (Vercel)

npx skills add ai-driven-dev/framework --skill 03-assert -a claude-code

3Manually: put the files in place

~/.claude/skills/03-assert/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/03-assert/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about 03-assert

How do I install 03-assert in Claude Code?

Use the marketplace: run /plugin marketplace add ai-driven-dev/framework, then /plugin install aidd-dev@aidd-framework.

What does 03-assert do?

It runs the project's assertions and fixes code until they pass, and on request checks architecture conformance or a running UI. The result is a pass or fail verdict.

Does 03-assert write tests?

No. It works with the assertions the project already has and repairs code against them. Writing or reviewing tests is out of scope.

Source text

SKILL.md · MIT
---
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.

© AI-Driven Dev · MIT · ai-driven-dev/framework

Similar skills

All skills for Testing and QA →
include-test-files-that-assert-on-behavior-being-changed-in-decl ZaxbyHub include-test-files-that-assert-on-behavior-being-changed-in-decl is a Claude Code skill that puts tests for changed behaviour in scope, so an agent fixes code alongside its checks. CX Codex +1 ★ 539repo stars update-or-delete-tests-that-assert-intentionally-removed-behavio ZaxbyHub update-or-delete-tests-that-assert-intentionally-removed-behavio is a Claude Code skill for revising or removing tests of deliberately removed behavior. It applies to code changes that retire a code path. CX Codex +1 ★ 539repo stars check-compiler-errors cursor The check-compiler-errors skill runs your project's compile and type-check commands, groups errors by file and category, then fixes the highest-confidence issues automatically. Useful when type errors are blocking local validation or CI. CX Codex +1 2,400installs gsd-validate-phase open-gsd gsd-validate-phase — a skill for Claude Code retroactively audits Nyquist validation coverage for a finished project phase. Runs when verifying completed milestones or when passed a phase number. CX Codex +1 572installs quality-validation qodex-ai quality-validation blocks AI agents from claiming a task is finished without running fresh verification commands and checking exit codes. CX Codex +1 142installs Skill Validator daffy0208 Skill Validator validates skill and MCP implementations against manifests using Codex. Detects feature drift, unchecked preconditions, and API mismatches. CX Codex +1 131installs

From the same set80

The whole set →
02-backlog The 02-backlog skill guides product backlog work, from sorting incoming requests to checking artifact relationships. Use it to review, order, or refine backlog items. CX Codex +1 ★ 571repo stars 01-usage 01-usage is a Claude Code skill that reports token use by period or task, split by day, model, agent or ticket, from a local aidd telemetry report. CX Codex +1 ★ 571repo stars 01-sdlc 01-sdlc orchestrates changes from contract framing to a draft pull request across Frame, Deliver, and Check zones. Use it for end-to-end tasks instead of single-step code edits. CX Codex +1 ★ 571repo stars 12-cook 12-cook is a Claude Code skill for finding and maintaining project recipes, researching techniques, and applying existing guides. It can also check recipe steps and investigate improvements. CX Codex +1 ★ 571repo stars 00-repo-init 00-repo-init prepares a fresh Git repository with a default branch, CONTRIBUTING.md, and a bootstrap commit, then pushes it to a remote host on request. CX Codex +1 ★ 571repo stars 09-for-sure The 09-for-sure skill runs an agent through repeated attempts until a runnable success check passes. Use it for work with a result that can be verified, such as a command. CX Codex +1 ★ 571repo stars 07-refactor 07-refactor rewrites code along one of four axes: performance, security, cleanup, architecture. It scans on its own or takes a finished audit report as the to-do list. CX Codex +1 ★ 571repo stars 00-init 00-init controls AIDD telemetry in projects: turns resource tracking on or off with consent, configures identity, or purges recorded metrics. CX Codex +1 ★ 571repo stars

Project sponsors

Companies that keep this analytics open