/
/
Catch regressions from your latest deploy early
For developers who want every BugHerd report since the last GitHub deploy, matched to the commits it shipped, just by asking their AI assistant.
On this page
Connector
Connect BugHerd, pick your AI tool and paste the prompt.
The problem
New bug reports arrive and nobody knows which deploy caused them
After a release, new BugHerd reports arrive and someone has to work out which ones the deploy caused. That means finding the last workflow run, listing its commits and guessing which change broke what.
Without PopdockAI
- Find the last successful workflow run by hand
- List the commits that deploy shipped
- Read every new bug and feedback item since
- Guess which change caused which report
With PopdockAI
- The latest successful deploy and its commits are found
- Reports since that run are grouped by page
- Likely regressions are linked to a named commit
- Clean, watch or roll-back verdict, nothing changed
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** For the website tracked in the BugHerd project `{project-name}`, find the latest successful deploy from `{repository}` on `{branch}` (default main) and list what has been reported since, as possible regressions.
**Step 1: Find the deploy**
Call `github-get-workflow-run` with `company` set to `{repository}`, `branch`, `conclusion` success and `max-records` 10. Take the most recent run. If there is none, say so and stop. Call `github-get-commit` with `company` and `commit-date.from` set to the date of the previous successful run, to list what that deploy shipped.
**Step 2: Read what came in since**
Call `bugherd-get-projects` with `name.contains` set to `{project-name}`. If nothing matches, say so and stop. If several match, list their names and project-id values and ask which one; do not guess. Then call `bugherd-get-tasks` and `bugherd-get-feedback` with `project-id` and `created.from` set to the deploy run's created-date.
**Step 3: Judge**
* Group the new reports by page.
* A report is a likely regression when its page or wording relates to a commit message in the deploy; say which commit.
* Critical reports after a deploy always go at the top.
**Step 4: Report**
1. **Deploy:** run name, run-number, date, sha, and the commits it shipped (first line each).
2. **Reported since:** a table with task number, title, severity, page, created, and the related commit when there is one.
3. **Verdict:** clean, watch, or roll-back candidate, with one sentence why.
**Rules & Guidelines:**
* Tools named bugherd-... are on the bugherd MCP server; tools named github-... are on the github MCP server. Every GitHub tool takes the repository as its `company` parameter. If either set of tools is missing, say which server is not connected and stop.
* This prompt is read-only. Do not call any BugHerd write tool (`bugherd-add-task`, `bugherd-add-feedback`, `bugherd-update-task`, `bugherd-move-task`, `bugherd-add-comment`, `bugherd-add-attachment-from-url`, `bugherd-add-project`, `bugherd-update-project`, `bugherd-add-project-member`, `bugherd-add-guest-to-project`) or any GitHub write tool (`github-add-issue`, `github-update-issue`, `github-add-issue-comment`, `github-update-issue-comment`, `github-add-issue-assignee`, `github-add-issue-label`, `github-lock-issue`, `github-unlock-issue`, `github-add-milestone`, `github-update-milestone`, `github-enable-workflow`, `github-disable-workflow`, `github-rerun-workflow-run`, `github-cancel-workflow-run`).
**Validation:**
* If nothing has been reported since the deploy, the verdict is clean.Who it's for
One answer, three teams that use it
Release engineers
Decide fast whether to roll back
Get a clean, watch or roll-back verdict after a deploy, with the reports and commits that drive it.
Anything reported in BugHerd for Fabrikam Shop since the last deploy of fabrikam/shop from main? Should we roll back?
Developers
Find which commit broke the page
See new bug reports linked to the commits that touched the same pages, so you start in the right place.
Which BugHerd reports in Contoso Portal since the last main deploy look related to a commit?
QA leads
Triage post release reports by page
See everything reported since the release grouped by page, critical items first.
Group the BugHerd bugs and feedback reported for Northwind Traders since the last deploy of northwind/web by page.
How it works
What PopdockAI does when you ask
You name the project, repository and branch, and your AI assistant compares the latest deploy with new BugHerd reports. It reads both systems and changes nothing.
01
Ask
You name the BugHerd project, GitHub repository and branch.
02
Deploy
It finds the latest successful workflow run and the commits it shipped.
03
Compare
It reads BugHerd reports since that run and links likely regressions to commits.
04
Report
It gives the deploy, a table of new reports and a clean, watch or roll-back verdict.
What PopdockAI provides
The tools behind the answer
Ready made tools for BugHerd and one secure connection to your AI tool. No code, no exports.
github-get-workflow-run
github-get-commit
bugherd-get-projects
bugherd-get-tasks
bugherd-get-feedback
This report is built from Get data tools only. PopdockAI applies the row, field and parameter rules your admin sets, and every query is written to the audit trail.
The outcome
Regressions tied to the commits behind them
Related use cases
More ways to put this data to work
Check a BugHerd fix has shipped on GitHub
Ask your AI whether a BugHerd task is fixed and it traces the GitHub issue, fixing commits and deploy run to give a clear shipped or not yet verdict.
Learn More
Send a BugHerd task to a GitHub issue
Ask your AI to send a BugHerd task to GitHub and it opens one linked issue with the page, severity and reporter after you confirm, never a duplicate.
Learn More
Sync BugHerd task and GitHub issue status
Ask your AI to sync BugHerd and GitHub and it proposes status changes for drifted pairs, then applies only the rows you approve, with a comment on each.
Learn More
Reconcile BugHerd tasks and GitHub issues
Ask your AI to reconcile BugHerd and GitHub and it lists linked tasks and issues whose open or closed state has drifted, plus any broken links.
Learn More
Add an update to a BugHerd task
Ask your AI to add a note to a BugHerd task by its number, with an optional file from a link, and it posts the update only after you confirm.
Learn More
One prompt template with infinite possibilities.
Your AI assistant adapts its approach, tone, and capabilities to match each unique context while you maintain a single, manageable workflow.
Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.