ReleasePilot – From Code to Release Confidence

Releasing software is not just about checking whether the application runs. Before a release, developers may need to inspect code quality, security risks, tests, documentation, dependencies, and configuration. These checks are often spread across different files and tools, making the process time-consuming and easy to overlook. ReleasePilot is a release-readiness analysis tool built to bring these checks into one structured workflow. A developer selects a project and branch in ReleasePilot and starts an analysis. The application creates an analysis session and generates an orchestration task for IBM Bob. Bob then coordinates three specialized analysis agents in parallel: a Code Risk Analyst, a Test Analyst, and a Docs & Config Analyst. Each agent examines a different part of the repository and produces findings with a severity, affected file, evidence, impact, and recommendation. The results are then passed through a critic/review stage before being sent back to ReleasePilot. The application presents the reviewed findings in a single report and classifies the release state as READY, READY WITH WARNINGS, or BLOCKED. For our demonstration, ReleasePilot analyzed a DocuRAG project and identified 18 evidence-backed findings. These included a hardcoded API credential in the source code, ineffective tests with no assertions, a missing test file dependency, and documentation/configuration issues. The target users are developers and teams who want a more structured way to validate a project before release. Instead of manually checking different areas one by one, they can use one workflow to organize the investigation and understand the most important issues. What makes ReleasePilot different is the way IBM Bob is used as the orchestration layer. Rather than treating the AI as a single general-purpose reviewer, Bob coordinates specialized agents and a critic pass, while ReleasePilot provides the interface, analysis session, persistence, and final report. The goal is not to automatically make the release decision for the developer. It is to make release validation more systematic, evidence-backed, and easier to verify.