triage-v3

Triage bugs and auto-create GitHub tickets by investigating codebase issues, reading files, tracing code paths, and running builds and tests. The workflow generates structured root-cause analysis and clear acceptance criteria without modifying any source code.

Yes, you can diagnose codebase issues safely without modifying source files by reading files, grepping, and inspecting logs. This non-destructive exploration traces code paths and runs builds or tests to identify root causes across open repositories.

The best way to trace code paths in large repos is using a structured diagnostic workflow that reads files, inspects logs, and runs tests. It then creates and updates GitHub tickets with project board integration, providing clear acceptance criteria.

Yes, triage-v3 works with GitHub project boards by creating and updating tickets as part of the investigation workflow. After tracing code paths and running builds, it updates project boards as needed to track the diagnosed issues.

To investigate and document root-cause analysis for GitHub tickets, describe the issue you want investigated to start triage mode. The workflow reads files, traces code paths, runs builds and tests, and drafts an initial ticket with structured analysis and acceptance criteria.

You should avoid using an automated codebase triage workflow when you need to actively modify source code to fix an issue. This workflow is strictly non-destructive, focusing on reading files, tracing paths, and generating tickets without changing source files.