Reviews completed changes through hands-on checks and one reviewer agent. It compares the implementation and recorded evidence with the original goal, constraints, code quality, and security requirements, then reports approval, specific blockers, or an inconclusive result.
Find unused TypeScript code, verify references with a language server, and assign removals to parallel agents. Group changes by file, create separate commits, and check types, tests, and the build after cleanup.
Manage Git changes and investigate repository history with evidence from commands. Group related edits into focused commits, reorganize branch history when requested, trace changes, and identify the first faulty commit when a repeatable check is available.
Get started with omo through a guided feature tour and workflow introduction. Optional setup migration and past-session analysis connect its features to existing work habits, while memory tools record useful preferences for future sessions.
Review changes since the last npm release through parallel change analysis, hands-on quality checks, and an overall release assessment. Receive a readiness verdict, blocking issues, version recommendations, and a draft changelog with compatibility concerns.
Guides code cleanup and restructuring by mapping dependencies, assessing test coverage, and planning small changes. Supports tasks such as extracting functions or renaming symbols, with checks after each step and recovery when verification fails.
Breaks long-running goals into small, verifiable steps, tracks progress, and records evidence from actual operation. Checkpoints preserve what has been proven so work can resume after interruptions and continue toward explicit completion criteria.
Have agents with different roles challenge a proposed approach, exposing weak assumptions, missed interactions, and unnecessary complexity. Surviving findings go to a dedicated planning agent, which produces sequenced tasks with explicit success criteria.
Execute a written work plan by assigning implementation and verification to subagents. Track progress, isolate work in Git worktrees, record test evidence, and require independent verification before marking tasks complete, with optional pull request delivery.
Check the appearance and interaction states of web pages, terminal interfaces, and paginated documents. Uses captured images, light and dark themes, viewport comparisons, and independent reviews to produce evidence-backed verdicts for each checklist item.
Coordinates a named team of Codex workers with concrete responsibilities and shared progress records. It selects available collaboration tools, manages communication and separate working copies when needed, and handles integration, team archival, and cleanup after the work ends.
Reproduce and fix LazyCodex or Codex defects in a temporary workspace. Verify the change with regression tests and real usage, then deliver an upstream Codex pull request or a LazyCodex issue containing the tested patch.
Automate website navigation, form filling, screenshots, data extraction, and web app testing while keeping page state between scripts. Works with a fresh Chromium session or an existing Chrome session through an extension.
Publishes oh-my-opencode through GitHub Actions, then checks package versions and release artifacts. Covers related packages, user-facing release summaries, and Discord announcements, reporting failures without starting code repairs during the release process.
Organize code changes into focused commits that follow the project's existing message style. Clean up branch history with rebase, resolve conflicts, and investigate when particular code changed or who last modified a line.
Turn a broad coding request into a concrete work plan grounded in the codebase. After user approval, it documents affected files, decisions, dependencies, and verification steps so a separate worker can carry out the implementation.
Search local session histories across Codex, Claude Code, OpenCode, and other coding agents. Find earlier requests, inspect transcripts and child sessions, and reconstruct past work using recorded evidence, with filters for dates, projects, platforms, and models.
Finds and rewrites code by its syntax structure across 25 languages. Use it to locate matching calls or declarations, preview bulk changes, and run reusable YAML rules that check code or apply fixes.
Compare current code with the latest published npm releases to identify unpublished changes. Read actual code differences, explain their impact across shared components and agent environments, and recommend version updates for each release layer.
Use language servers, tools that understand code structure, to check errors, locate definitions, and find references in Codex. Check whether a symbol can be renamed and apply the rename across the workspace.
Builds and improves web interfaces, covering layout, styling, motion, and usability. It records design rules before implementation, uses supplied references or design research, and checks the result in real browsers for visual consistency, accessibility, and performance.
Audit a codebase with three vulnerability hunters and two engineers who build small demonstrations of suspected flaws. Verify attack paths, assess severity from demonstrated impact, and report evidence, targeted fixes, and checks to prevent recurrence.
Test the Senpi adapter and task engine against the real senpi binary in an isolated environment. Check task and team behavior, record evidence in a consistent location, and verify that the existing agent directory remains untouched.
Display a preset introduction to Oh My OpenCode through an Easter egg command. The message outlines the plugin’s agent coordination, code navigation, structural search, built-in search integrations, and compatibility with Claude Code configuration.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)