← fstackCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to fstack
Snapshot Sep 30, 2026 · 23:16 UTC · version 1.1.2
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Find failing PR checks, inspect logs or external check links, and apply focused fixes",
"included_files": [],
"name": "fix-ci",
"skill_md_contents": "---\r\nname: fix-ci\r\ndescription: Find failing PR checks, inspect logs or external check links, and apply focused fixes\r\nmenu-description: find failing PR checks, inspect logs, apply focused fixes\r\n---\r\n\r\n# Fix CI\r\n\r\n## Trigger\r\n\r\nBranch or PR CI is failing and needs a fast, iterative path to green checks.\r\n\r\n## Workflow\r\n\r\n1. Resolve the active PR and inspect `gh pr checks --json name,bucket,state,workflow,link`.\r\n2. Inspect failed jobs and extract the first actionable error. Use GitHub Actions logs when available; otherwise use the check link to identify the failing command or service.\r\n3. Apply the smallest safe fix.\r\n4. Push, re-check the PR check set, and repeat until green.\r\n\r\n## Guardrails\r\n\r\n- Fix one actionable failure at a time.\r\n- Prefer minimal, low-risk changes before broader refactors.\r\n- Keep `gh pr checks` as the source of truth for overall PR CI state.\r\n\r\n## Output\r\n\r\n- Primary failing job and root error\r\n- Fixes applied in iteration order\r\n- Current CI status and next action\r\n"
}SHA-256 of public snapshot: 63b3e7fdbf180adf3fd8125cbc4cade29d963610cca4d434bb4178e1a24b13c0