okisdev

Approve a GitHub PR as a maintainer once verify-pr clears it, posting the GitHub approval or declining, with an optional hand-off to ship-pr for the merge.

Run a multi-round parallel verification sweep over recent work or a whole repository, tracking findings in a fix ledger and looping fix and re-verify rounds until a round comes back clean.

Verify a repository's project memory against the live tree and GitHub, then confirm, correct, compact, promote, archive, or disprove each topic so stale, derivable, or wrong memories stop steering agents and stop costing context.

Stage and commit only uncommitted file changes into clean, categorized commits; existing commits are left untouched.

Create a new branch off the default base (not the current HEAD, so unrelated commits stay behind) and move all uncommitted changes onto it. Use when you started work on the wrong branch or on main.

create or open a GitHub pull request (PR) from the current branch with a title and body that follow the repo's conventions and the user's writing style

Generate a project-local verify skill with a feature map so the repository gains a scripted, rerunnable way to prove its app's behavior, proven once end to end before handover.

Design or redesign an admin, ops, or customer dashboard in the repository's own design law, from a measured diagnosis to a verified build and a contract in AGENTS.md.

Diagnose a failure to its origin with a reproduction first, fix the cause rather than the symptom, and stop at the diagnosis when only an explanation was asked.

Mine recent session transcripts for durable lessons and turn them into proposed skill edits, rule candidates, or memory writes, applying nothing without approval.

Locate a verified icon for a brand, product, or UI concept and deliver it as a lucide-react import or a vendored SVG component when asked to find or add icons.

Inspect a live database with real SQL before reasoning from ORM schema files, resolving the connection from the project's own configuration and staying read-only unless explicitly asked to write.

Extract the load-bearing pattern from a reference URL, repository, or sibling path and re-express it in this codebase's own idiom with a deviation report, never cloning the reference.

Rewrite a repository's AGENTS.md and CLAUDE.md files into short normative instruction files, routing incidents, inventories, and module internals to where they belong, within the size caps every harness reads.

Build a structured understanding of a repository before any edit, producing a compact map of entry points, conventions, and prior art with every claim cited by file.

Run an optimization pass over a repository or recent changes that simplifies and deletes, reuses existing primitives, conforms to repo conventions, syncs docs, verifies, and ends uncommitted.

Organize uncommitted changes or messy commits on the current branch into clean, categorized commits grouped by purpose. Can reset and rewrite already-committed (even pushed) history.

Decide what a dashboard shows and in which chart form, including forms and data it does not have yet, from what the product holds and production says, then build it in verified batches.

Answer an API or behavior question about a dependency from authoritative source by reading installed code, the published npm artifact, or the upstream repository at the pinned version before ever trusting docs.

Drive a change to a merged PR end to end, building or resuming the PR, looping over CI and review threads to address feedback, and merging once every check and review has settled, skipping only a still-pending item that has gone quiet well past the 15-minute settle window.

Write a maintainer-style summary review of a GitHub PR for the original author, run after review fixes are applied.

Upgrade dependency versions and lockfiles across npm workspaces, Python uv projects, and GitHub Actions when asked to bump, upgrade, or update dependencies.

Read and write Claude project auto-memory so Claude, Grok, and Codex share one store that holds only durable facts the repository and GitHub cannot give. Use at the start of interactive repo work (not in a delegated run), when such a fact is learned, or when the user says remember / 记住 / 项目记忆.

Drive and verify a CLI or TUI change in a scripted terminal harness with captured transcripts as evidence, when asked to verify terminal behavior, check an interactive flow, or reproduce a terminal bug.

Fetch a GitHub issue and verify its claims against the codebase with concrete evidence.

Verify a GitHub PR against its stated goal and the surrounding codebase, judging whether it should exist at all before correctness, tests, conventions, and side effects.

Fetch review comments on a GitHub PR (bots + humans) and verify each claim against the actual code, reporting which to accept / reject / defer with concrete evidence and fix drafts.

Render and verify a web UI change in a real browser with a managed dev server, DOM assertions, and screenshots when asked to verify UI work or act on visual feedback.