What is error-autofix?

An error-investigation and code-fix workflow for production exceptions reported through PostHog, an error-tracking service, or found by a scheduled scan. Depending on its mode, it reports the problem or opens a pull request with a possible fix.

It is for checking the real production error, deciding whether it is a genuine code bug, and, when permitted, creating a fix pull request or marking a candidate for automatic merging.

It separates investigation from implementation and keeps a human responsible for merging code, while allowing recurring production errors to be examined again.

How KeepSoftwareSimple/compass-calendar configures GitHub Copilot

Reuse

Borrowing it

Nothing to install: this file belongs to KeepSoftwareSimple/compass-calendar. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/KeepSoftwareSimple/compass-calendar/main/.github/prompts/error-autofix.md

Clone the repo

git clone --depth 1 https://github.com/KeepSoftwareSimple/compass-calendar

Made for: GitHub Copilot.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/keepsoftwaresimple/compass-calendar/error-autofix/github.svg)](https://agentmods.dev/commands/keepsoftwaresimple/compass-calendar/error-autofix)

Your own site

<a href="https://agentmods.dev/commands/keepsoftwaresimple/compass-calendar/error-autofix"><img src="https://agentmods.dev/badge/commands/keepsoftwaresimple/compass-calendar/error-autofix/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/keepsoftwaresimple/compass-calendar/error-autofix"><img src="https://agentmods.dev/badge/commands/keepsoftwaresimple/compass-calendar/error-autofix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,767 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.01767
Opus 5.5	$0.00000	$0.00707
Sonnet 5.5	$0.00000	$0.00353
Haiku 4.5	$0.00000	$0.00177

Measured yesterday against content hash d7b55ee639f4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

error-autofix scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.github/prompts/error-autofix.md · 150 lines

How it starts

The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Error autofix agent instructions

You are triaging a GitHub issue that reached the error-autofix workflow. That issue may have been opened by PostHog's error-tracking integration (posthog[bot]), reopened after a later spike, or created by the hourly sweep when production exceptions had no GitHub ticket. Your job depends on the Mode you were given:

triage — investigate and report. Never open a PR.
pr — investigate, and for genuine code bugs open a fix PR. Never merge it; a human merges.
merge — same as pr, plus: label the PR automerge-candidate if (and only if) it meets every criterion in "Confidence rubric" below. A separate deterministic script re-checks your work before anything actually merges — you are not the last line of defense, so err toward leaving the label off when uncertain.

In every mode, do the investigation and triage classification below first.

Recurrence on an already-seen fingerprint is in scope. A closed GitHub issue, a prior autofix comment, or an earlier "wait for the next burst" close is not a reason to no-op. Treat the latest production events as a new wave.

Step 1 — get the real error, not just the issue body

The issue body is thin (a short description plus a PostHog fingerprint URL like .../error_tracking/fingerprint/<hash>?timestamp=...). Use the PostHog MCP tools to pull the actual signal before doing anything else:

Stack trace and exception type/message
Occurrence count, affected users, first/last seen
Event properties listed in packages/core/src/constants/posthog-error-tracking.properties.ts (POSTHOG_ERROR_TRACKING_PROPERTY: environment, service, version, namespace, result, errorType, $exception_fingerprint). Some historical issues predate these and will be generic.
Whether this is staging or production (staging and prod currently share one PostHog project — a staging-only error is not urgent and should never justify an automerge-candidate label)

The backend and sync services set those keys as custom event properties (see POSTHOG_ERROR_TRACKING_PROPERTY in packages/core/src/constants/posthog-error-tracking.properties.ts), so PostHog's environment and release context groups do not return them — query-error-tracking-issue-events will look like the event carries nothing but $exception_* and $lib. Read them with SQL instead, substituting the issue's UUID and using the exact property names from that constants file:

Read the full file on GitHub · 150 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

yesterday First seen · 150 lines · 0 tokens per session scan A d7b55ee639f4

Subscribe to this mod's changes

error-autofix is a command published in the GitHub repository KeepSoftwareSimple/compass-calendar (226 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,767 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-11-07.

Debugging React TypeScript calendar google google-calendar nodejs

error-autofix next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
error-autofixKeepSoftwareSimple/compass-calendar	Command	226	today	MIT	A	0	GitHub Copilot
validate-auth-schemakriasoft/react-starter-kit	Command	24k	6d ago	MIT	A	0	Claude Code
COMMANDS.generatedPostHog/posthog	Command	41k	today	none	A	0	Claude Code
e2e-testingJNTMTMTM/eIsland	Command	335	yesterday	GPL-3.0	A	0	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code

compass-calendar: Command for GitHub Copilot