docs(agents): add /rev and /fix-ci skills (#751)

## Summary

- Add `/rev` skill: rebase onto main, address unresolved PR review
feedback (GraphQL thread fetching with `databaseId` for REST replies,
auto-resolve when confident), and delegate CI fixes to `/fix-ci`
- Add `/fix-ci` skill: standalone skill to diagnose failing CI from
`link` URLs, fetch logs, fix, verify locally, and push
- Register both skill triggers in AGENTS.md

---------

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

Author: cpcloud

.claude/commands/fix-ci.md

@@ -0,0 +1,37 @@
+<!-- Copyright 2026 Phillip Cloud -->
+<!-- Licensed under the Apache License, Version 2.0 -->
+
+Diagnose and fix failing CI jobs on the current branch's PR.
+
+## 1. Identify failures
+
+1. List check runs: `gh pr checks --json name,state,link`
+2. If all checks pass, report that and stop.
+
+## 2. Diagnose each failure
+
+For each failing job:
+
+1. Extract the run ID from the `link` URL returned in step 1.
+2. Fetch failed logs: `gh run view <run_id> --log-failed`
+3. Read the relevant source files to understand the root cause.
+4. Common failure categories:
+   - **Compile errors**: Fix the Go code.
+   - **Test failures**: Read the failing test, understand the assertion,
+     fix the code (not the test) unless the test itself is wrong.
+   - **Lint/format**: Run the linter locally, apply fixes.
+   - **Nix build**: Hash mismatches need `/update-vendor-hash`. Eval
+     errors need Nix expression fixes.
+   - **OSV scanner**: Use `/fix-osv-finding`.
+   - **Cross-platform (Windows/PowerShell)**: No `&&` in commands, no
+     bash-isms, use `-bench .` not `-bench=.`.
+
+## 3. Verify locally
+
+Run `/pre-commit-check` to confirm the fixes work before pushing.
+
+## 4. Push and watch
+
+1. `git push` (or `git push --force-with-lease` if you rebased)
+2. Watch checks: `gh pr checks --watch --fail-fast`
+3. If new failures appear, loop back to step 2.

.claude/commands/rev.md

@@ -0,0 +1,71 @@
+<!-- Copyright 2026 Phillip Cloud -->
+<!-- Licensed under the Apache License, Version 2.0 -->
+
+Rebase onto the latest main, address PR review feedback, and fix failing CI.
+
+## 1. Rebase onto main
+
+1. `git fetch origin main`
+2. `git rebase origin/main`
+3. If there are conflicts, resolve them, `git add` the resolved files, and
+   `git rebase --continue`. Repeat until the rebase completes.
+
+## 2. Address PR review feedback and fix CI (parallel)
+
+These two steps are independent -- start both in parallel.
+
+### 2a. PR review feedback
+
+1. Fetch unresolved review threads (use the GraphQL API for threaded context):
+   ```
+   gh api graphql -f query='
+     query($owner:String!, $repo:String!, $pr:Int!) {
+       repository(owner:$owner, name:$repo) {
+         pullRequest(number:$pr) {
+           reviewThreads(first:100) {
+             nodes {
+               id
+               isResolved
+               comments(first:50) {
+                 nodes { id databaseId author{login} body path line }
+               }
+             }
+           }
+         }
+       }
+     }' -f owner=cpcloud -f repo=micasa \
+        -F pr="$(gh pr view --json number --jq '.number')"
+   ```
+2. For each **unresolved** thread:
+   - Read the referenced file and line to understand the context
+   - Make the requested change (or explain in a reply why not)
+   - After pushing the fix, reply to the review comment using its
+     `databaseId` from the query:
+     `gh api repos/cpcloud/micasa/pulls/<pr>/comments/<databaseId>/replies -f body='...'`
+     Explain how it was addressed (commit hash, what changed).
+   - **Resolve the thread** if you are extremely confident the feedback
+     has been fully addressed. Use the GraphQL mutation:
+     ```
+     gh api graphql -f query='
+       mutation($id:ID!) { resolveReviewThread(input:{threadId:$id}) {
+         thread { isResolved }
+       }}' -f id=<thread_node_id>
+     ```
+     If there is any doubt the comment hasn't been fully addressed, leave
+     the thread open for the reviewer.
+3. Skip resolved threads -- they need no action.
+
+### 2b. Fix failing CI
+
+Use `/fix-ci` to diagnose and fix each failing job.
+
+## 3. Push and verify
+
+1. `git push --force-with-lease` (safe force push since we rebased)
+2. Wait for CI to start: `gh pr checks --watch --fail-fast`
+3. If new failures appear, loop back to step 2b.
+
+## 4. Update PR description
+
+After all changes are pushed, re-read the PR title and body
+(`gh pr view`) and update them if they no longer match the actual changes.

AGENTS.md

@@ -170,6 +170,8 @@ details; do not duplicate that detail here.
 - `/pre-commit-check` -- before committing, to verify code compiles and tests pass
 - `/blog-post` -- when writing or updating Hugo blog content in `docs/`
 - `/debug-dump` -- when diagnosing rendering bugs (VHS or live TUI)
+- `/rev` -- rebase onto main, address PR review feedback, fix failing CI
+- `/fix-ci` -- diagnose and fix failing CI jobs on the current PR
 
 ### Shell and tools