Connect the context
Link an Asana project or ClickUp list to one or more GitHub repositories. Bring task descriptions, comments, and available attachments into the picture.
TaskPull request
MergewiseTASK-AWARE CODE REVIEW
Review the code.
Remember
the task.
The diff tells you what changed. The task tells you why. Mergewise brings both into your review, then helps your team take the next step.
For teams working in GitHub, Asana, and ClickUp.
ONE TASK. THE WHOLE PICTURE.
PULL REQUEST #128
OpenGuard checkout retries
LINKED TASK · ACCEPTANCE CRITERION
A retry must never create a second charge.
Task description + PR changesOne behavior worth checking
Retries can charge the customer twice.
The charge happens before its receipt is stored. If storage fails, a retry could repeat the charge instead of returning the original result.
checkout.ts · illustrative excerpt
68 const receipt = await charge(order);
69 await saveReceipt(receipt);Suggested directionUse a stable idempotency key for the payment request.
Illustrative workflow. Not a live review.
YOUR EXISTING TOOLS.
BETTER CONNECTED.
BETTER CONNECTED.
GitHub+AsanaorClickUp
No new place for your team to track work.
01 / THE WORKFLOW
From “what changed?”
to “what happens next?”
Keep the requirements, the review, and the handoff connected.
Ask for a review
Request a review from a PR comment. Mergewise checks the implementation against the task and reports findings with code locations and explanations.
@mergewise-ai reviewMake the handoff useful
Generate a QA plan in the task. Configure Asana merge notifications and status changes so the next person knows where to pick up.
/mergewise qa02 / BEYOND THE DIFF
The work around the code
is still part of the work.
Look past a green diff.
Review correctness, solution choices, and unnecessary complexity with the task’s intent in view. Findings are there for your team to evaluate, not accept blindly.
Turn context into test cases.
Request scenarios, expected results, and negative cases. No PR yet? Generate a plan from task context, including related parent and sibling tasks where available.
Estimate from the brief.
Use the task description, comments, and attachments to estimate effort. Add repository context when available, and request a fresh estimate when the scope changes.
Your project. Your rules.
Choose the Asana task status after a merge. Add exceptions based on the previous status, and configure each project independently.
03 / STAY IN CONTROL
Helpful automation.
Human judgment.
Decide which projects and repositories are connected, request the work you need, and keep your team in charge of the result.
Explore the setup guideA FEW THINGS THAT STAY YOURS
- 01Which projects and repositories to connect
- 02When to request a review or QA plan
- 03What status a merged PR should trigger
- 04The final call on every finding
A FEW PRACTICAL QUESTIONS
Before you connect.
Does Mergewise replace human review?
No. It provides findings and suggestions for your team to assess. A generated QA plan also isn’t proof that the tests have been executed.
Can one project use multiple repositories?
Yes. Select multiple GitHub repositories for a project, or leave the selection empty to detect repositories from PR links.
Do I need a PR to create a QA plan?
No. Use /mergewise qa in an Asana task to build a plan from its context. For subtasks, Mergewise can include the parent and sibling task context.
Can I choose what happens after a merge?
Yes. For each linked Asana project, configure a default status and optional overrides based on the task’s current status. These rules do not wait for every PR on a task to merge.
KEEP THE INTENT IN THE LOOP