Skip to content

Exclude workflow state from AUTO_FIX likelihood evaluation #92

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
adalton merged 1 commit into from
Aug 4, 2026
Merged

Exclude workflow state from AUTO_FIX likelihood evaluation #92

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion bugfix/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
name: bugfix
version: 0.4.0
version: 0.5.0
description: >-
Diagnostic and repair workflow that analyzes error logs, traces root causes,
implements fixes, and verifies with regression tests.
Expand Down
8 changes: 7 additions & 1 deletion bugfix/skills/assess.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -162,7 +162,13 @@ Provide a **reason** (1–2 sentences) and **confidence** (High / Medium / Low).

#### AUTO_FIX Likelihood

Only when recommendation is AUTO_FIX. Score 0–100 using these bands, then
Only when recommendation is AUTO_FIX. AUTO_FIX evaluates whether the bug is
technically amenable to automated fixing — clear root cause, bounded scope,
testable fix. Do not factor in workflow state such as existing PRs, prior fix
attempts, open branches, or previous bot assessments. Those are operational
concerns for the caller, not indicators of technical feasibility.

Score 0–100 using these bands, then
adjust based on source-code complexity from Step 4d:

| Band | Description-quality criteria | Code-level adjustments |
Expand Down
2 changes: 1 addition & 1 deletion triage/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
name: triage
version: 0.2.0
version: 0.3.0
description: >-
Bulk-triage unresolved Jira bugs with AI-driven recommendations and an
interactive HTML report. Scan also loads recently resolved bugs for regression
Expand Down
6 changes: 6 additions & 0 deletions triage/skills/analyze.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -151,6 +151,12 @@ Set `priorityMismatch` to `null` when the assigned priority reasonably matches t

#### AUTO_FIX Likelihood Criteria

AUTO_FIX evaluates whether the bug is technically amenable to automated
fixing — clear root cause, bounded scope, testable fix. Do not factor in
workflow state such as existing PRs, prior fix attempts, open branches, or
previous bot assessments. Those are operational concerns for the caller, not
indicators of technical feasibility.

When assigning `autoFixLikelihood`, consider:

- **80-100%**: Exact error message with stack trace, single file/method, clear fix pattern (e.g. null check, off-by-one, missing validation)
Expand Down
Loading