1. Read the change in context
Gilfoyle reads the diff, linked issue and repository instructions. You set the review scope, base branch and required checks so the review addresses the intended behavior.
Review every pull request
Give Gilfoyle a pull-request review queue and get evidence-backed findings, focused checks and a clear handoff to your reviewers.
code-review
Example brief · Hypothetical workflow
Your brief
Review this checkout PR against the linked issue. Reproduce likely defects and leave the merge decision with our reviewer.
GilfoyleAPP
I’ll trace the changed behavior, check likely failures and prepare findings for review.
See example output ↓How Gilfoyle handles it.
Starts: When a pull request opens or changes in a repository you have connected.
2. Prove the useful findings
Using connected Claude Code or Codex with GitHub, Gilfoyle traces affected paths and runs focused tests where the environment permits. Each finding names a trigger, code location and consequence; uncertain observations stay clearly qualified.
3. Hand back a review you can act on
You get prioritized findings, reproduction steps and check results. If you also authorize a fix, it goes into a separate draft PR with focused tests. Your required reviewers decide what merges.
A review with a reproducible reason.
Use this for a second look at an individual change. For implementation across a larger engineering project, explore software development.
Hypothetical finished result
Example output
Checkout review brief
Hypothetical: a PR adds a retry to checkout creation.
- Finding
- A timeout after the provider accepts the request can create a second checkout on retry. The finding points to the retry branch and a reproducible timeout sequence.
- Checks
- A focused regression test simulates an accepted request followed by a lost response. The brief records the test command and result, plus checks the environment could not run.
- Handoff
- Recommend an idempotency key and ask the code owner to review the finding. Any requested patch remains a draft PR pending required review.
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 intended repository with access to the PR, linked issues and the review actions you allow.
- Claude Code or Codex
- Connect an available coding tool and provide the repository environment and test dependencies. Grant comment or draft-PR actions only where needed.
- Linear (optional)
- Connect the relevant project if acceptance criteria live there. GitHub issue context can be enough.
Questions about this workflow
Does Gilfoyle approve or merge every PR?
You choose the review policy. This workflow returns evidence for your required reviewers; it does not replace their merge decision.
What if the tests cannot run?
The review names the missing dependency or environment and separates code inspection from executed checks. You can supply that environment before relying on the result.
Can a review include a fix?
Yes, when you authorize the coding work and connect the necessary tools. Gilfoyle prepares a draft PR with focused tests for required review.