Back/Engineering/Claude
AdvancedEngineering

Build an Automated User Feedback to Pull Request Pipeline

Compress the path from live feedback to a testable code change by capturing the user’s words, structuring the issue, creating a Linear ticket, and invoking a context-rich coding agent from Slack.

Build an Automated User Feedback to Pull Request Pipeline

Chintan records live feedback, turns the audio into a structured issue and Linear ticket, then invokes an internal Slack bot that uses repository and observability context to prepare a pull request and preview.

Before you start

What you need

  • Consent to record the feedback
  • A lightweight audio capture app
  • An LLM with structured output
  • Linear, Slack, repository, and observability integrations

What you’ll make

A traceable Linear issue and draft pull request linked to the original feedback, with a preview that makes the proposed fix easy to test.

Tools used

Step by step

The workflow

Follow the sequence once, then adapt the prompts, checks, and handoffs to your own setup.

4 steps

Step01

Capture Live Audio Feedback

Use a mobile friendly recorder with one obvious control. Capture the user’s words during a consented dogfooding session and attach the session, product area, and timestamp.

The app only needs a simple record button to minimize friction and capture feedback in the moment.

Step02

Process Audio with an LLM

Transcribe the audio and return structured fields for observed behavior, expected behavior, product area, user journey, severity evidence, title, and concise summary. Keep diagnosis explicitly separate.

Example prompt
Process this consented user feedback recording. Return JSON with transcription, feedback_type, product_area, user_journey, observed_behavior, expected_behavior, impact, concise_title, ticket_summary, and open_questions. Preserve the user’s evidence. Do not invent a root cause.

The prompt should guide the model to extract the core problem and user journey, for example: 'On trade tab, typing into from field does not display numbers, user cannot initiate a trade.'

Step03

Automate Ticket Creation

Search Linear for a matching issue. Create a new ticket only when needed, attach or link the audio and transcript, and apply the relevant journey and feedback labels.

This step eliminates manual data entry and ensures that feedback is logged consistently and immediately.

Step04

Trigger a Pull Request from Slack

From the shared Slack thread, invoke the coding bot with the repository and ticket ID. Have it retrieve authorized code, error, and analytics context, create a draft PR, and return the PR plus preview to the same thread.

Example prompt
Claude bot create pr --repo wallet-mobile --ticket [TICKET_ID]. Read the ticket and attached feedback, inspect authorized Sentry, Datadog, analytics, and repository context, state the likely cause with evidence, implement the smallest fix, run relevant checks, and return a draft PR plus preview link to this thread.

For maximum effectiveness, this bot should be integrated with other services like Datadog and Sentry to pull in relevant context for debugging.

What good looks like

  • The ticket preserves the user journey and observable problem.
  • The original audio remains attached or linked for context.
  • The coding agent can retrieve relevant repository and telemetry evidence.
  • The draft PR and preview link return to the shared Slack thread.

Build your next product with ChatPRD

Turn an idea into a PRD, user stories, and a plan.

Try ChatPRD free

After the steps

Runbook notes

How to recover when the loop fails and where human judgment helps.

Recover

If it goes sideways

Feedback is recorded or retained without clear consent
Obtain consent, minimize captured data, define retention, and remove sensitive details before sending audio to a model.
The model turns an ambiguous report into a confident diagnosis
Separate observed behavior from suspected cause and keep the original audio attached for triage.
Every comment becomes a duplicate ticket or PR
Search existing Linear issues first and append evidence or frequency to the matching issue when appropriate.
The coding agent lacks enough product or production context
Attach the ticket, repository, affected journey, logs, Sentry events, and analytics links the agent is authorized to use before implementation.

Start shipping
better products.

Join 100,000+ product managers who use ChatPRD to write better docs, align teams faster, and build products users love.

Free to start
No credit card
SOC 2 certified
Enterprise ready