1. Reproduce the reported behavior
Gilfoyle reads the report, relevant logs you supply and repository guidance. The issue keeps an accountable owner. If the environment or reproduction input is missing, the handoff names exactly what is needed.
Turn bug reports into draft PRs
Hand Gilfoyle a bug report and get a reproduced problem, a scoped patch, focused checks and a draft GitHub PR ready for required review.
bug-fixes
Example brief · Hypothetical workflow
Your brief
The export button fails for an empty report. Reproduce it, make the smallest fix and open a draft PR with a regression test for our code owner.
GilfoyleAPP
I’ll establish the failing case, prepare the patch and report the checks with the draft PR.
See example output ↓How Gilfoyle handles it.
Starts: A report arrives in a connected bug channel or you hand over a specific issue.
2. Make the scoped change
With connected Claude Code or Codex and GitHub, Gilfoyle traces the failure, adds a regression test and changes the affected path. Focused checks cover the reported behavior and nearby cases without expanding into unrelated cleanup.
3. Prepare the draft and closure checklist
The draft PR includes the reproduction, patch summary, executed checks and remaining verification. Required reviewers own approval and merge. The bug stays linked to its owner until the agreed verification supports closure.
From a report to a reviewable change.
Use this for one reproducible defect. PR review and production-error diagnosis have separate workflows when those are the starting point.
Hypothetical finished result
Example output
Empty-export fix handoff
Hypothetical: exporting a report with no rows throws an exception.
- Reproduction
- An empty report reaches the CSV formatter without a header row. The draft includes the smallest input and the observed exception.
- Change and checks
- The patch returns a header-only export for the empty case. A focused test covers zero rows and a normal populated report; the handoff records actual commands and outcomes.
- Review and closure
- The draft requests the exports code owner. Closure awaits required review and owner verification in the agreed environment; a draft PR is not a deployed fix.
The apps this job needs.
Connect the accounts and actions for your workflow. Start in Artie or add your Artisan to Slack; access stays within your account permissions.
Explore apps- GitHub
- Connect the repository and allow branch creation and draft PRs. Provide repository instructions, a runnable environment and required reviewers.
- Claude Code or Codex
- Connect the coding tool available to your workspace and supply test dependencies and scoped access.
- Slack
- Connect the reporting channel if that is your intake. Permit updates to the report thread and link the issue owner.
Questions about this workflow
What if the bug cannot be reproduced?
Gilfoyle returns the attempted reproduction, observed behavior and missing input. It does not claim a fix without a supported failing case.
Will this deploy the fix?
This workflow ends in a draft PR and a verification handoff. Your review and release process determines what merges and deploys.
When is the report closed?
The owner checks the agreed closure evidence, such as a verified result in the target environment. The PR links back to that report.