How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

error-report-summary - Prompt

Name: error-report-summary
Author: damoneward38

Prompt file imported from damoneward38/cli (.cursor/commands/error-report-summary.md). Copyright stays with the author.

Error Report Summary (last 5 days)

Fetch the last 5 days of error-report issues from the Base44 CLI GitHub repo, produce a summary report with Mermaid graphs, action items, and evaluation. Output is written to error-reports/ (gitignored).

Instructions

1. Compute the date range

"Last 5 days" = from today backward (e.g. today 2026-03-08 → created:>=2026-03-03).
On macOS: date -v-5d +%Y-%m-%d. On Linux: date -d '5 days ago' +%Y-%m-%d.

2. Fetch issues with GitHub CLI only

List issues:

gh issue list --repo base44/cli --label "error-report" --state all --search "created:>=YYYY-MM-DD" --limit 20

For each issue number in the list, fetch the full body:

gh issue view <number> --repo base44/cli --json title,number,state,createdAt,body

Use only the gh CLI; no direct GitHub API calls.

3. Read and understand each issue

For each issue: command, error message, stack trace, environment (OS, command), and whether it is a CLI bug, backend issue, or user error (working as designed).

4. Ensure report directory is gitignored

If error-reports/ is not in .gitignore, add:

# Error report summaries (generated, do not commit)
error-reports/

Create the directory if needed: mkdir -p error-reports.

5. Write the report

Write to error-reports/last-5-days-summary.md (or error-reports/YYYY-MM-DD-summary.md for a date-stamped name) with:

Meta — Run date, "last 5 days" window, total issue count, table of issues (title, link, created date, state).
Graphs (Mermaid) — Embed in the same file:
- Total errors over time: Bar or xychart with X = date (by day), Y = number of errors. Use each report’s "Total errors" and the report date from the issue title.
- Errors by type: Pie or bar of count per type. Derive type from issue body (e.g. auth, deploy, backend 428, config not found, timeout, user validation).
- Top N per-error: Bar chart of the top 5–10 recurring error patterns (normalize issue titles or first error line; group and count).
Per-issue summary — Short description of what failed, root cause if evident, 1–2 bullets per issue.
Main action items — Grouped by theme (auth, deploy, entities, config, telemetry, UX). Concrete next steps with file/line references where applicable.
What else to evaluate — Trends (same error across reports), gaps (missing context, unclear reproduction), suggestions (telemetry, docs, CLI UX).

6. Reply to the user

Give a short summary (e.g. how many issues, main themes) and the path to the report file.

Output

Report path: error-reports/last-5-days-summary.md (or date-stamped equivalent).
All charts are Mermaid code blocks so they render in GitHub and Cursor.

Install error-report-summary and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

# Error Report Summary (last 5 days) Fetch the last 5 days of error-report issues from the Base44 CLI GitHub repo, produce a summary report with Mermaid graphs, action items, and evaluation. Output is written to `error-reports/` (gitignored). ## Instructions ### 1. Compute the date range - "Last 5 days" = from today backward (e.g. today 2026-03-08 → `created:>=2026-03-03`). - On macOS: `date -v-5d +%Y-%m-%d`. On Linux: `date -d '5 days ago' +%Y-%m-%d`. ### 2. Fetch issues with GitHub CLI only - List issues: ```bash gh issue list --repo base44/cli --label "error-report" --state all --search "created:>=YYYY-MM-DD" --limit 20 ``` - For each issue number in the list, fetch the full body: ```bash gh issue view <number> --repo base44/cli --json title,number,state,createdAt,body ``` - Use only the `gh` CLI; no direct GitHub API calls. ### 3. Read and understand each issue - For each issue: command, error message, stack trace, environment (OS, command), and whether it is a CLI bug, backend issue, or user error (working as designed). ### 4. Ensure report directory is gitignored - If `error-reports/` is not in `.gitignore`, add: ```text # Error report summaries (generated, do not commit) error-reports/ ``` - Create the directory if needed: `mkdir -p error-reports`. ### 5. Write the report Write to `error-reports/last-5-days-summary.md` (or `error-reports/YYYY-MM-DD-summary.md` for a date-stamped name) with: 1. **Meta** — Run date, "last 5 days" window, total issue count, table of issues (title, link, created date, state). 2. **Graphs (Mermaid)** — Embed in the same file: - **Total errors over time:** Bar or xychart with X = date (by day), Y = number of errors. Use each report’s "Total errors" and the report date from the issue title. - **Errors by type:** Pie or bar of count per type. Derive type from issue body (e.g. auth, deploy, backend 428, config not found, timeout, user validation). - **Top N per-error:** Bar chart of the top 5–10 recurring error patterns (normalize issue titles or first error line; group and count). 3. **Per-issue summary** — Short description of what failed, root cause if evident, 1–2 bullets per issue. 4. **Main action items** — Grouped by theme (auth, deploy, entities, config, telemetry, UX). Concrete next steps with file/line references where applicable. 5. **What else to evaluate** — Trends (same error across reports), gaps (missing context, unclear reproduction), suggestions (telemetry, docs, CLI UX). ### 6. Reply to the user - Give a short summary (e.g. how many issues, main themes) and the path to the report file. ## Output - Report path: `error-reports/last-5-days-summary.md` (or date-stamped equivalent). - All charts are Mermaid code blocks so they render in GitHub and Cursor.

{ "prompt": "# Error Report Summary (last 5 days)\n\nFetch the last 5 days of error-report issues from the Base44 CLI GitHub repo, produce a summary report with Mermaid graphs, action items, and evaluation. Output is written to `error-reports/` (gitignored).\n\n## Instructions\n\n### 1. Compute the date range\n\n- \"Last 5 days\" = from today backward (e.g. today 2026-03-08 → `created:>=2026-03-03`).\n- On macOS: `date -v-5d +%Y-%m-%d`. On Linux: `date -d '5 days ago' +%Y-%m-%d`.\n\n### 2. Fetch issues with GitHub CLI only\n\n- List issues:\n ```bash\n gh issue list --repo base44/cli --label \"error-report\" --state all --search \"created:>=YYYY-MM-DD\" --limit 20\n ```\n- For each issue number in the list, fetch the full body:\n ```bash\n gh issue view <number> --repo base44/cli --json title,number,state,createdAt,body\n ```\n- Use only the `gh` CLI; no direct GitHub API calls.\n\n### 3. Read and understand each issue\n\n- For each issue: command, error message, stack trace, environment (OS, command), and whether it is a CLI bug, backend issue, or user error (working as designed).\n\n### 4. Ensure report directory is gitignored\n\n- If `error-reports/` is not in `.gitignore`, add:\n ```text\n # Error report summaries (generated, do not commit)\n error-reports/\n ```\n- Create the directory if needed: `mkdir -p error-reports`.\n\n### 5. Write the report\n\nWrite to `error-reports/last-5-days-summary.md` (or `error-reports/YYYY-MM-DD-summary.md` for a date-stamped name) with:\n\n1. **Meta** — Run date, \"last 5 days\" window, total issue count, table of issues (title, link, created date, state).\n2. **Graphs (Mermaid)** — Embed in the same file:\n - **Total errors over time:** Bar or xychart with X = date (by day), Y = number of errors. Use each report’s \"Total errors\" and the report date from the issue title.\n - **Errors by type:** Pie or bar of count per type. Derive type from issue body (e.g. auth, deploy, backend 428, config not found, timeout, user validation).\n - **Top N per-error:** Bar chart of the top 5–10 recurring error patterns (normalize issue titles or first error line; group and count).\n3. **Per-issue summary** — Short description of what failed, root cause if evident, 1–2 bullets per issue.\n4. **Main action items** — Grouped by theme (auth, deploy, entities, config, telemetry, UX). Concrete next steps with file/line references where applicable.\n5. **What else to evaluate** — Trends (same error across reports), gaps (missing context, unclear reproduction), suggestions (telemetry, docs, CLI UX).\n\n### 6. Reply to the user\n\n- Give a short summary (e.g. how many issues, main themes) and the path to the report file.\n\n## Output\n\n- Report path: `error-reports/last-5-days-summary.md` (or date-stamped equivalent).\n- All charts are Mermaid code blocks so they render in GitHub and Cursor.", "variables": [], "notes": "Fetch the last 5 days of error-report issues from the Base44 CLI GitHub repo, produce a summary report with Mermaid graphs, action items, and evaluation. Output is written to `error-reports/` (gitignored).", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/damoneward38/cli", "path": ".cursor/commands/error-report-summary.md", "ref": "0ef4c490049767f8f7c5b2b0d20b085ffc5aa1ba", "url": "https://github.com/damoneward38/cli/blob/0ef4c490049767f8f7c5b2b0d20b085ffc5aa1ba/.cursor/commands/error-report-summary.md", "key": "damoneward38/cli/.cursor/commands/error-report-summary.md" } } }

error-report-summary

About

Error Report Summary (last 5 days)

Instructions

1. Compute the date range

2. Fetch issues with GitHub CLI only

3. Read and understand each issue

4. Ensure report directory is gitignored

5. Write the report

6. Reply to the user

Output

Install error-report-summary and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews