Copy PR comments into clanker-ready prompts.

Stop re-explaining review feedback. Please Fix Clanker packages the comment, code, thread, and PR context your AI worker needs.

Add project creation flow #428

Awaiting approval

OpenMaya Chenwants to merge 1 commit intomainfromfeature/projects

Conversation 3Commits 1Checks 6Files changed 1+9

Jordan Lee reviewed this pull request

⌄apps/web/src/server/projects/createProject.ts

Comment on lines +8 to +15

8+export async function createProject(input) {

9+ const projectId = input.id ?? randomUUID();

10+

11+ await db.projects.doc(projectId).set({

12+ name: input.name,

13+ ownerId: input.ownerId,

14+ });

15+}

Jordan Lee left feedback

Check if this issue is valid. If so, understand the root cause and fix it. If not, explain why.

<comment>
Validate input.id before using it as a project document ID.
</comment>

<metadata>
Repository: acme-labs/customer-portal
PR title: Add project creation flow
File: apps/web/src/server/projects/createProject.ts
Line: 9
</metadata>

<file context>
+ const projectId = input.id ?? randomUUID();
+ await db.projects.doc(projectId).set({
</file context>

<thread context>
Jordan Lee left this review comment in an inline PR thread.
</thread context>

PR descriptionCommit SHAThread context

Validate input.id before using it as a project document ID.

Reply...

Built for the review loop you already have.

The extension does one narrow job: turn review feedback into a complete, precise worker handoff without leaving the PR.

Click the review comment

The extension stays beside the GitHub feedback you are already reading.

Choose the useful context

Include thread replies, nearby code, PR metadata, descriptions, or commit SHA when needed.

Paste into your worker

The copied prompt is portable across Codex, Claude Code, ChatGPT, or any task queue.

Copy the whole review conversation when one comment is not enough.

Clanker-ready prompts can include the exact thread, metadata, and code context so the worker understands what changed and why it matters.

MCEPJLPS

apps/web/src/server/checkout/applyCoupon.tsMaya Chen reviewed 6 minutes ago

12export async function applyCoupon(cart, code) {

13 const coupon = await db.coupons.findUnique({

14 where: { code },

15 });

17 const total = cart.items.reduce(

18 (sum, item) => sum + item.price,

19 0

20 );

22 return {

23 total: total - (coupon?.amountOff ?? 0),

24 couponId: coupon?.id,

25 };

26}

Maya Chenstarted a review thread on line 18

Maya Chenreviewed

This can apply an expired coupon. We should check expiresAt before using it in checkout totals.

Eli Parkreplied

Also worth checking merchantId. A coupon from another store should not discount this cart.

Jordan Leereplied

Confirmed. The API validates usage count, but this helper trusts the coupon lookup too much.

Priya Shahreplied

The worker should add tests for expired coupons and cross-merchant coupons. Both should keep the original total.

Maya Chenresolved direction

Yes. Reject the coupon before calculating the final total, then return the reason so the UI can show it.

Generated worker promptComment thread, metadata, and nearby code

Ready

Check if this issue is valid. If so, understand the root cause and fix it. If not, explain why.

<comment>
Maya Chen: This can apply an expired coupon. We should check expiresAt before using it in checkout totals.

Eli Park: Also worth checking merchantId. A coupon from another store should not discount this cart.

Jordan Lee: Confirmed. The API validates usage count, but this helper trusts the coupon lookup too much.

Priya Shah: The worker should add tests for expired coupons and cross-merchant coupons.
</comment>

<metadata>
PR: #428 Tighten checkout pricing
URL: https://github.com/acme/shop/pull/428
Repository: acme/shop
Author: Maya Chen
File: apps/web/src/server/checkout/applyCoupon.ts
Line: 18
Thread: 5 comments from 4 people
</metadata>

<file context>
export async function applyCoupon(cart, code) {
  const coupon = await db.coupons.findUnique({
    where: { code },
  });

  const total = cart.items.reduce(
    (sum, item) => sum + item.price,
    0
  );

  return {
    total: total - (coupon?.amountOff ?? 0),
    couponId: coupon?.id,
  };
}
</file context>

<thread context>
The thread asks for validation before totals are calculated, plus tests for expired and cross-merchant coupons.
</thread context>

PR descriptionCommit SHAThread context

Button styles

Make the copy action stand out as much as you want.

Keep the GitHub-native default, use a familiar action color, or make the prompt copier impossible to miss with a brighter style.

Default

GitHub native

GitHub

Merge green

Review

Action blue

Graphite

Quiet dark

Rainbow

High signal

Gold

Warm highlight

Aurora

Soft glow

The clipboard is the integration.

Please Fix Clanker does not try to become your AI dashboard. It gives you a clean prompt bundle and lets you decide where it goes.

Original review comment

Nearby file context

PR metadata

Thread replies

Optional PR description

Optional commit SHA

Narrow permissions

The extension targets GitHub PR pages, stores toggle preferences locally, and copies selected context when you ask.

No backendNo analyticsNo AI API callsNo dashboard