Forge

What This Skill Does

Forge is an autonomous quality engineering swarm designed to transform the software development lifecycle by integrating quality directly into the coding process rather than treating it as an afterthought. By unifying DDD (Domain-Driven Design), ADR (Architecture Decision Records), and TDD (Test-Driven Development), Forge ensures that every piece of code produced is verified against behavioral specifications written in Gherkin.

Forge acts as a self-healing agent that operates in a continuous loop: it runs tests, analyzes failures, applies fixes, commits the verified code, and learns from the outcome. Whether you are managing a complex microservices architecture, a modular monolith, or a standard monorepo, Forge automatically maps your project structure, detects language-specific dependencies, and enforces seven distinct quality gates to ensure the final output is production-ready and 'Done-Done.'

Installation

To integrate Forge into your environment, use the OpenClaw CLI:

clawhub install openclaw/skills/skills/ikennaokpala/forge

Once installed, Forge will perform a discovery pass on your project root to map your bounded contexts, API protocols, and build systems, creating a context map that ensures high-fidelity testing across your entire stack.

Use Cases

• Legacy Refactoring: Safely refactor complex monoliths by relying on Forge's behavioral verification to ensure no regressions occur.
• Rapid Feature Delivery: Accelerate the development of new microservices while maintaining high contract reliability and end-to-end integration standards.
• Automated Bug Resolution: Use the self-healing loop to automatically diagnose, fix, and verify production defects without manual intervention.
• Contract Testing: Ensure seamless communication between decoupled services by validating API contracts in real-time.

Example Prompts

1. "Forge, analyze the current project architecture and run an exhaustive end-to-end test suite on the 'checkout' bounded context to identify any breaking changes."
2. "I've added a new business requirement: Gherkin scenario for user registration. Forge, please implement the necessary code and verify it passes all seven quality gates."
3. "Forge, my microservices are failing integration tests after the latest deployment. Analyze the logs, determine the root cause in the service contract, and apply a self-healing fix."

Tips & Limitations

• Pre-requisites: Ensure your project has an existing test framework (e.g., Jest, Pytest, Go test) so Forge has a baseline to operate from.
• Context Awareness: Forge is most effective when Gherkin files are descriptive and modular; clear specifications lead to more accurate autonomous fixes.
• Limitations: While Forge handles most architectures, extremely non-standard build pipelines may require manual definition of build tasks in the initial context map.
• Safety: Always review Forge's generated commits in a feature branch before merging into production, despite its high level of behavioral verification.