skill-urmzd-dotfiles-fix-and-retry · by Install
$ agentstack add skill-urmzd-dotfiles-fix-and-retry ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README — it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-urmzd-dotfiles-fix-and-retry) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming — see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps — measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Fix and Retry
Diagnose CI failure, fix it, and re-ship.
Steps
- Diagnose: Follow the
diagnose-ciworkflow:
gh run list --status=failure --limit 1 --json databaseId,name,headBranchto find the latest failuregh run view --log-failedto get error logs- Identify root cause and affected files
- Fix: Apply the fix to the codebase. Read the affected file(s), make the edit, and verify the fix makes sense.
- Commit: Create a conventional commit for the fix (e.g.,
fix(ci): correct workflow syntax). Use a HEREDOC for the message.
- Push: Before pushing, capture the pre-push run id (
gh run list --branch $(git branch --show-current) --limit 1 --json databaseId -q '.[0].databaseId'). Thengit push.
- Watch: Poll for a NEWER run, not the previous failed one. Match the new run by the pushed commit's
headSha(git rev-parse HEAD) -- e.g.gh run list --branch $(git branch --show-current) --limit 5 --json databaseId,headSha,status,conclusionand pick the run whoseheadShaequals the new HEAD (and whose id differs from the captured pre-push id). Poll every 15s (max 5 minutes) until that run completes. This prevents the watcher from latching onto the previous failed run before the new run is registered.
- Report: Show whether the re-run passed or failed. If it failed again, show the new error.
Rules
- Only fix issues you can confidently diagnose from the logs. If the cause is unclear, report the diagnosis and ask the user rather than guessing.
- Never force push or amend the previous commit.
- If the fix requires secrets, env vars, or manual GitHub settings changes, explain what's needed instead of attempting it.
Gotchas
- A new CI run is not registered the instant you push. Capture the pre-push run id (step 4) and poll for a run whose
headShamatches the newly pushed HEAD before reading status. If you watch--limit 1blindly, the watcher can latch onto the previous failed run and report a false failure.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: urmzd
- Source: urmzd/dotfiles
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.