okisdev

Plugin okisdev in okisdev/ai-reference. Commands read from the repo's manifest — 6 days ago.

Skills (25)

• approve-pr

  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.

• clean-memory

  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.

• commit-changes

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

• create-branch

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

• create-pr

  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

• design-dashboard

  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-root

  Investigate why a command, test, build, deployment, or feature fails, reproduce it, trace it to its root cause, and fix the cause only when a fix was asked.

• distill-session

  Review how the skills are being used and how recent sessions went, and propose skill edits, rules, or memory for approval, including asks to optimize the skills or to turn a session's lessons into one.

• find-icon

  Find, add, or swap an icon or logo for a brand, product, vendor, file type, or UI concept.

• inspect-db

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

• mirror-reference

  Adapt a design, interaction, or API from a reference the user points at (a URL, repository, or sibling path) into this project's own components, following it without copying it.

• normalize-agents-md

  Rewrite a repository's instruction files, and the docs they point agents at such as a DESIGN.md or a README manual, into short normative files when markdown grows into a running log, changes with every change, or runs too long, retiring CLAUDE.md and routing as-built descriptions, incidents, and inv

• optimize-repo

  Extract, decouple, refactor, simplify, remove redundancy and dead code, and reuse existing helpers, then verify and leave the changes uncommitted.

• organize-commits

  Organize uncommitted changes or messy commits on the current branch into clean, categorized commits grouped by purpose, resetting and rewriting already-committed (even pushed) history when needed.

• plan-charts

  Decide what a page, screen, or dashboard shows and in which chart form when a view is text heavy or under-visualized.

• read-source

  Answer how a dependency behaves, or whether it supports something, from its source at the pinned version, including asks to read a library's or upstream's source.

• recap-activity

  Recap what I, my team, a project, or this computer did, or what failed and why, today, this week, or over any window, read-only, and say so when nothing covers it.

• ship-pr

  Ship a change to a merged PR end to end (ship it, run the flow, merge it), building or resuming the PR, looping over CI and review threads to address feedback, and merging once every check and review has settled on the head that merges.

• summarize-review

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

• upgrade-deps

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

• use-project-memory

  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; load it when a person starts work in a repository (a run another agent dispatched with a brief skips that load), and use it when work surfaces a u

• verify-issue

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

• verify-pr-comments

  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.

• verify-pr

  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.

• verify-ui

  Render and verify a web UI in a real browser, loaded before any browser tool is used (Chrome DevTools, Claude in Chrome, Gode, Playwright, or a built-in browser), when asked to look at a result, open the browser, take a screenshot, open localhost, check mobile or dark mode, or act on pasted-image fe