/
/
Match open GitHub issues to what Ghost Inspector reports now
For development teams whose test-failure issues stay open after tests pass, who want the backlog reconciled by their AI assistant.
On this page
Connector
Connect Ghost Inspector, pick your AI tool and paste the prompt.
The problem
Issues stay open after tests pass again
GitHub issues about Ghost Inspector failures stay open long after the tests pass, while new failures go unfiled. Sorting it out means checking every issue against current results and every failing suite against the backlog.
Without PopdockAI
- Search GitHub for issues about test failures
- Check each suite and test in Ghost Inspector
- Look for failing suites with no issue
- Leave stale issues open
With PopdockAI
- Open issues with your title marker are read
- Each is sorted into now passing, still failing or not found
- Recently failing suites with no open issue are listed
- Closing and filing are recommended, never done
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** Reconcile open GitHub issues about Ghost Inspector failures (titles containing `{title-marker}`, default `[Ghost Inspector]`) against what Ghost Inspector reports now, looking back `{lookback-days}` days (default 7) for failures.
**Step 1: Collect the open issues (GitHub)**
Call `github-get-issue` with `title.contains` set to `{title-marker}` (or `[Ghost Inspector]` if blank) and `status` open. For each issue, pull out the suite name from the title and the test names and test ids from the body.
**Step 2: Check each against Ghost Inspector**
For each issue, call `ghost-inspector-get-suite` with `name.contains` set to the suite name, then `ghost-inspector-get-suite-result` with `suite-id` for its most recent result. Where the body names tests, call `ghost-inspector-get-test` with `id` (or `name.contains`) to read each test's current `passing`.
Sort each issue into one of:
* **Now passing**: the latest suite result and every named test pass. Candidate to close.
* **Still failing**: the latest result still fails.
* **Not found**: the suite or test no longer exists in Ghost Inspector.
**Step 3: Find unfiled failures (Ghost Inspector, then GitHub)**
Call `ghost-inspector-get-suite-result` with `passing` false and `date-created.from` set to `{lookback-days}` days ago. For each distinct suite name that is failing now and has no open issue from Step 1, record it as unfiled.
**Step 4: Report**
Four tables: Now passing (issue number, title, url, latest pass time), Still failing (issue, suite, failing count), Not found (issue, what is missing), Unfiled failures (suite name, suite id, latest failing result id and time).
**Rules & Guidelines:**
* `github-get-issue` is on the github server; the ghost-inspector tools are on the ghost-inspector server.
* This prompt is read-only. Do NOT call `github-update-issue`, `github-add-issue`, `github-add-issue-comment`, `ghost-inspector-execute-suite` or `ghost-inspector-execute-test`. Recommend closing or filing; do not do it.
**Validation:**
* Match suite names exactly once found; if `name.contains` returns several suites, prefer the exact name and list the others under Not found as ambiguous.
* If no issues carry the marker, say so, report only the unfiled failures, and mention that issues filed by hand may use a different title.Who it's for
One answer, three teams that use it
Developers
Close issues that are already fixed
Issues whose tests now pass are listed with the latest result time, ready to close.
Which open GitHub issues titled [E2E] are for Ghost Inspector tests that pass now?
QA leads
File the failures nobody reported
Suites failing recently with no open issue are listed so you can file them.
Which Ghost Inspector suites failed in the last 14 days with no open GitHub issue?
Engineering managers
Trust the test issue backlog
Four tables show exactly where the backlog and test results disagree.
Reconcile GitHub issues marked [Ghost Inspector] with the last 30 days of results.
How it works
What PopdockAI does when you ask
You give a title marker and a period, and your AI assistant matches the issue backlog to current test results. Ambiguous suite names are listed, not guessed.
01
Ask
You give the issue title marker and a lookback period.
02
Read
It reads open GitHub issues with that marker and checks each suite and test in Ghost Inspector.
03
Find
It lists suites failing recently with no open issue.
04
Report
You get one table per group, with closing and filing recommended, never done.
What PopdockAI provides
The tools behind the answer
Ready made tools for Ghost Inspector and one secure connection to your AI tool. No code, no exports.
github-get-issue
ghost-inspector-get-suite
ghost-inspector-get-suite-result
ghost-inspector-get-test
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
An issue backlog that matches reality
Related use cases
More ways to put this data to work
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.

.webp)
