ompsure
  • Reviews
  • Pro
  • Pricing
  • Template
Sign InSign Up
ompsure

Code quality that happens automatically.
Free for personal use.

Audience

  • Who's It For?
  • For Creators
  • For Developers

Features

  • Code Graph
  • Security
  • Code Review
  • Testing
  • Deployment
  • Memory

Product

  • Plugins
  • Control Panel
  • Proof
  • Catalog
  • How It Works

Plans

  • Pricing
  • Pro Patterns
  • Commercial License
  • Starter Template

Resources

  • Getting Started
  • Documentation
  • Reviews
  • Affiliate Program

© 2026 Et'al Software Solutions. All rights reserved.

  • Template License
  • Plugin License
  • Refund Policy
  • GitHub
Enforcement catches
Viewing as
Enforcement catches

Non-null assertion (!)

2026-06-09

enforcement hook — composure-pro · 2026-06-09
[composure:enforcement] The write you just attempted to MobileNav.tsx matches a pattern this codebase doesn't want shipped. What the rule caught (1 item): - Non-null assertion (!) detected. Use optional chaining (?.) with a null guard.

The agent conceded immediately: “The enforcement rule rightly flags my `tab.children!` non-null assertion. I'll use optional chaining instead (`tab.children?.map`) — safe since `hasChildren` already guards it.” Fixed in one pass.

Why this matters: Bugs that wait for a customerThe failure mode this catch prevents — in App architecture, in practice.

Composure enforcement hook, firing mid-session in the composure-pro repo. Catch message reproduced verbatim.

You can stop reading and start checking.

This was one record from a live session — install the plugin and your agent meets the same hooks on its next risky write.

Install itNext: Lazy Function / Object type