CodeOns: Automated Codebase Onboarding Agent

Every developer has inherited a project with no README, cryptic variable names, no setup instructions, and hidden bugs. This is not an edge case — it happens constantly when developers leave, projects get handed off, or someone returns to old code. The cost is real: 2-3 hours minimum just to understand what an unfamiliar codebase does, more time lost to bugs nobody caught, and new team members blocked for days before they can contribute. CodeOns is a reusable IBM Bob 2.0 custom skill that automates the entire codebase onboarding workflow. A developer opens any project in Bob IDE and says: "I've inherited this codebase, help me understand it." Bob automatically activates the code-ons skill and runs a structured 9-step autonomous workflow — scanning the full repository, launching 4 parallel analysis tracks for flow mapping, dependency detection, input/output mapping, and bug detection, then generating a README, SETUP guide, inline comments on every file, automatic bug fixes with before/after documentation, a requirements.txt, and a final onboarding summary. CodeOns is built for any developer who works in a team — software engineers inheriting legacy code, new team members onboarding onto unfamiliar projects, and open source contributors trying to understand a repo before contributing. Users simply copy the code-ons skill file into their Bob workspace and describe their situation in natural language. Bob activates CodeOns automatically. No commands to memorize, no configuration needed. It works on any language, any repo, any team. What makes CodeOns unique is that it is not a one-time demo — it is a reusable, portable Bob skill that any team can adopt immediately. Unlike simply asking Bob to explain code, CodeOns runs a structured multi-step autonomous workflow using Agent mode, parallel tasks, and subagents, producing a complete set of deliverables in a single session. We demonstrated this on two projects: a synthetic messy repo (project_x) and a real public GitHub repository with 50+ undocumented scripts. Results from actual Bob sessions show time to understand a codebase dropped from 2-3 hours to under 2 minutes, documentation generation from 1-2 hours to 30 seconds, 8 bugs caught and fixed automatically, 22 files changed in one session, and 24 out of 24 tasks completed autonomously.