-
Notifications
You must be signed in to change notification settings - Fork 0
Notes
Baiju Muthukadan edited this page Jun 9, 2026
·
1 revision
Analyze the source code for critical issues (concurrency bugs, resource leaks,
data corruption, logic errors in core algorithms). Ignore minor style/consistency
issues. For each confirmed issue, create a GitHub issue with the bug label,
including: exact file paths and line numbers, code snippets showing the problem,
a concrete scenario demonstrating the failure, and a suggested fix.
You can tune it by adding/removing concern areas (e.g., "focus on the audio pipeline" or "include security vulnerabilities") or adjusting the severity threshold ("include medium-severity
issues too").