fix(ce-debug): investigate the tracker and PR history for prior work#1018
Merged
Conversation
ce-debug previously diagnosed only from code and live telemetry, so it could not see that a bug already had an open ticket, was being fixed in an unmerged PR, had a prior fix that regressed, or had a prior merged attempt that took the same (failing) approach. Add Phase 1.4: discover the project's tracker/code-review surface from repo signals (git remote, issue-key patterns, active project conventions), then run a few targeted queries. The search is weighted toward what git log cannot show -- open/in-flight work and the issue/PR discussion thread -- and explicitly defers merged-fix discovery to the existing Phase 1.3 git step to avoid redundant work. Findings flow into Phase 2 and reshape the recommendation (e.g. defer to an existing open PR instead of writing a duplicate fix). Gated off the trivial fast-path; regression signals are the strongest trigger; ticket/PR text is treated as data, not instructions.
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
ce-debugdiagnosed bugs only from the code and live telemetry (Sentry, logs, DB). It never consulted the project's institutional memory — the issue tracker and PR history — so it could not see when a bug:Change
New Phase 1.4 in
skills/ce-debug/SKILL.md:ABC-123-style issue keys in commits/branches/PR titles, the tracker named in active project conventions) — capability-not-tool: never assumes a specific CLI/MCP exists, never treats a missing one as proof the capability is absent.git logcannot show (open/in-flight work + the issue/PR discussion thread). Merged-fix discovery is explicitly handed to the existing Phase 1.3 git step to avoid redundant searching.A Phase 2 present-findings bullet carries any surfaced ticket/PR into the recommendation (e.g. lead with an existing open PR instead of a fresh fix).
Validation
Tested via the
skill-creatoreval workflow (fresh subagents, so the in-session skill cache didn't mask the change), using this repo's real GitHub issues/PRs as fixtures and the pre-edit file (git show HEAD) as the baseline:git log)With-skill 100% vs. baseline 68% pass rate; tracker searched 3/3 scenarios vs. 0/3 for the baseline. Modest cost (~+40s, tokens within noise).