{"slug":"forge","title":"forge","description":"Description:\n\nAdversarial code hardening for Claude Code. Forge spawns two agents — a Builder and a Breaker — that iterate against each other until the code is unbreakable. The Builder implements a feature, the Breaker writes adversarial tests to prove bugs, and the Builder must fix the implementation without deleting or weakening the tests. The loop continues until the Breaker can't produce a failing test. The result is battle-tested code with a permanent adversarial test suite.\n\nKey features:\n\n  - Evidence-based, not opinion-based. Every issue the Breaker raises must have a failing test that proves the bug. No test, no break. This eliminates false positives and subjective feedback.\n  - Iterative adversarial loop. Builder and Breaker are separate agents that go back and forth for up to N rounds. The Builder cannot dismiss feedback; it must make the failing tests pass.\n  - Adversarial tests are permanent. The Breaker's tests stay in the repo under tests/adversarial/ as a regression suite. Future changes are protected by the same tests that originally caught the bugs.\n  - Automatic checkpoint. Creates a git tag before starting so the entire forge session can be rolled back with one command.\n  - Configurable rounds. Default 5 rounds, adjustable with --rounds N. Stops early if the Breaker can't find issues.\n  - Auto-detects project stack. Reads config files to determine language, test framework, and conventions. Works with Python, TypeScript, Rust, Go, Ruby, and anything with a test runner.","developer":null,"category":null,"reported_installs":null,"active":true,"first_seen_at":"2026-10-03T22:13:33.942Z","last_seen_at":"2026-10-09T18:02:35.368Z","last_changed_at":"2026-10-03T22:13:33.942Z","platform":"claude","sources":["Community"],"works_with":["Claude Code"],"marketplace_url":null,"repository_url":"https://github.com/UtkarshJain98/forge.git","web_data":{},"github_data":{},"catalog_sources":{"community":[{"name":"forge","source":{"sha":"95ef910b5528695bded466500f14515c4e14eeb1","url":"https://github.com/UtkarshJain98/forge.git","source":"url"},"homepage":"https://github.com/UtkarshJain98/forge","description":"Description:\n\nAdversarial code hardening for Claude Code. Forge spawns two agents — a Builder and a Breaker — that iterate against each other until the code is unbreakable. The Builder implements a feature, the Breaker writes adversarial tests to prove bugs, and the Builder must fix the implementation without deleting or weakening the tests. The loop continues until the Breaker can't produce a failing test. The result is battle-tested code with a permanent adversarial test suite.\n\nKey features:\n\n  - Evidence-based, not opinion-based. Every issue the Breaker raises must have a failing test that proves the bug. No test, no break. This eliminates false positives and subjective feedback.\n  - Iterative adversarial loop. Builder and Breaker are separate agents that go back and forth for up to N rounds. The Builder cannot dismiss feedback; it must make the failing tests pass.\n  - Adversarial tests are permanent. The Breaker's tests stay in the repo under tests/adversarial/ as a regression suite. Future changes are protected by the same tests that originally caught the bugs.\n  - Automatic checkpoint. Creates a git tag before starting so the entire forge session can be rolled back with one command.\n  - Configurable rounds. Default 5 rounds, adjustable with --rounds N. Stops early if the Breaker can't find issues.\n  - Auto-detects project stack. Reads config files to determine language, test framework, and conventions. Works with Python, TypeScript, Rust, Go, Ruby, and anything with a test runner."}]}}