Code Breaking Changes
- 251 installs
- 104k repo stars
- Updated August 4, 2026
- openai/codex
Guide for testing Codex TUI interactively.
About
Guide for testing Codex TUI interactively. You can start and use Codex TUI to verify changes. The test-tui skill documents workflows, constraints, and examples from SKILL.md for agent-assisted execution.
- You can start and use Codex TUI to verify changes.
- Always set RUST_LOG="trace" when starting the process.
- Pass `-c log_dir=<some_temp_dir>` argument to have logs written to a specific directory to help with debugging.
- When sending a test message programmatically, send text first, then send Enter in a separate write (do not send text + E
- Use `just codex` target to run - `just codex -c ...`
Code Breaking Changes by the numbers
- 251 all-time installs (skills.sh)
- +15 installs in the week ending Jul 26, 2026 (Skillselion tracking)
- Ranked #749 of 2,154 Testing & QA skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 4, 2026 (Skillselion catalog sync)
code-breaking-changes capabilities & compatibility
- Capabilities
- you can start and use codex tui to verify change · always set rust_log="trace" when starting the pr · pass ` c log_dir=<some_temp_dir>` argument to ha · when sending a test message programmatically, se
- Use cases
- documentation
What code-breaking-changes says it does
Guide for testing Codex TUI interactively
npx skills add https://github.com/openai/codex --skill code-breaking-changesAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 251 |
|---|---|
| repo stars | ★ 104k |
| Security audit | 3 / 3 scanners passed |
| Last updated | August 4, 2026 |
| Repository | openai/codex ↗ |
How do I apply code-breaking-changes using the workflow in its SKILL.md?
Guide for testing Codex TUI interactively
Who is it for?
Developers following the code-breaking-changes skill for the tasks it documents.
Skip if: Tasks outside the code-breaking-changes scope described in SKILL.md.
When should I use this skill?
User mentions code-breaking-changes or related triggers from the skill description.
What you get
Working code-breaking-changes setup aligned with the documented patterns and constraints.
Files
You can start and use Codex TUI to verify changes.
Important notes:
Start interactively. Always set RUST_LOG="trace" when starting the process. Pass -c log_dir=<some_temp_dir> argument to have logs written to a specific directory to help with debugging. When sending a test message programmatically, send text first, then send Enter in a separate write (do not send text + Enter in one burst). Use just codex target to run - just codex -c ...
Related skills
TddFollow test-driven development with a strict red-green-refactor loop when creating reliable features or fixing bugs.544k196k
Test Driven DevelopmentEnforce writing failing tests before any production implementation code.181k264kQaRun conversational QA sessions that turn user-reported bugs into well-written, domain-aware GitHub issues without manual ticket writing.179k196kMigrate To ShoehornAutomatically update TypeScript test files that rely on unsafe `as` type assertions by replacing them with type-safe partial objects from @total-typescript/shoehorn.164k196k
Webapp TestingVerify frontend behavior, debug UI issues, capture screenshots, and inspect logs of a running local web application using Playwright.123k165k
Playwright CliRun browser automation, generate element snapshots, inspect DOM attributes, and execute Playwright tests from the terminal.102k12.3kFAQ
What does code-breaking-changes do?
Guide for testing Codex TUI interactively
When should I use code-breaking-changes?
Invoke when Guide for testing Codex TUI interactively.
Is code-breaking-changes safe to install?
Review the Security Audits panel on this page before installing in production.