Fix Prs
Use only in the Anarlog repository when the active checkout branch is exactly...
Install
npx skills add fastrepl/anarlog --skill fix-prs -g -a claude-code -y- Repository
- fastrepl/anarlog9.7k
- Category
- Git and review
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 2,663 tokens
- Runs scripts
- No, instructions only
What it does
Use only in the Anarlog repository when the active checkout branch is exactly gitbutler/workspace. Resolve conflicts in the current GitButler workspace and fix actionable code review findings and CI failures on its active PRs, including drafts. Validate and publish repairs on their owning branches, resolve addressed review threads, and leave PRs open.
Fix workspace conflicts, PR reviews and CI
Applicability
Use only in the Anarlog repository or its checkouts/worktrees when the active
checkout branch is exactly gitbutler/workspace. Before running this workflow,
check with git symbolic-ref --quiet --short HEAD (a read-only branch check).
On any other branch or detached HEAD, skip this skill and use the normal Git
workflow. Do not initialize GitButler or switch branches to activate the skill.
Use this checkout's skills, not a global copy or another checkout's skills.
Use this skill when asked to repair workspace conflicts, PR review findings, or CI failures in the Anarlog GitButler repository.
Read the repository-local but skill and the active repository's AGENTS.md, workflow,
and testing skills when present. Use but for version control and the
repository's preferred authenticated forge tools for PR operations. Derive the
repository and configured target from the current workspace.
Invoking this workflow authorizes workspace updates, conflict resolutions and their necessary history rewrites, in-scope fixes, local commits, protected pushes, necessary CI reruns, and evidence-backed review replies/thread resolutions. Creating the skill alone does not execute it. Do not merge, enable auto-merge, create missing PRs, change draft state, or bypass branch protection. Other pushed/shared history rewrites need existing authorization; a new focused commit on the owning branch can avoid that dependency.
