iroha924
UserLocal-first Engineering Memory Graph for Claude Code and Codex — agents propose what they learned, you approve it, and it lives in Git as canonical Markdown.
Categories
Indexed Skills (10)
iroha-review
The self-review pipeline for this repository — the only one. Targets committed changes (default: everything since the merge-base with main), reviewing them through a multi-stage pipeline: deterministic checks (lint/typecheck/test/build/secret grep) → launch fresh-context reviewers (security-reviewer / spec-compliance-reviewer / adversarial-reviewer, plus security-diff-reviewer when the diff touches packages/git, packages/forge*, or packages/adapter-*) in parallel → reproduce-and-verify HIGH/CRITICAL findings with finding-validator. Can be invoked at any time, with or without a PR, and is what to run before pushing a fix to a security-sensitive package. If the working tree has uncommitted changes, use AskUserQuestion to confirm whether to include them. No commit, push, or PR creation — its only write is the PR-comment draft inside `.git/`, which is never committed. fail-open (this skill itself does not block the merge; it only reports findings). Invoked by "self-review this", "review this", or "/iroha-review".
pr-review-status
Find out what the AI reviewer said about a pull request, and respond to it. The hosted OpenAI Codex reviewer is invisible to CI — it appears in no status check — so `gh pr checks` being green says nothing about whether a review ran, is still running, or left findings. Use after pushing to a PR and before reporting the work as done, when deciding whether a re-review is worth its rate limit, and when replying to or resolving a review thread. Not for reviewing a diff yourself — that is `iroha-review`.
release
Cut an iroha npm release — bump the version, verify locally, dispatch the human-gated Release workflow, and confirm the publish. iroha ships to npm as `@irohalabs/iroha` via OIDC trusted publishing (no npm token). Use when preparing or cutting a release (a new `@irohalabs/iroha` version), or when asked "how do we release / publish iroha". Not for day-to-day development.
digest
Compose the editorial prose for the current iroha Digest period — the dashboard's front page. Use when the user asks to write, refresh, or regenerate the Digest (weekly or monthly). Do not use to look up knowledge or to report on a person; the Digest is aggregate and agent-and-rule-focused.
checkpoint
Save a structured Checkpoint of the current work as a local iroha candidate for later human approval. Use after a meaningful unit of work — a decision reached, a bug fixed, a reusable rule or pattern discovered. Do not use for trivial edits, and never treat a Checkpoint as approved knowledge (a human approves candidates in the dashboard).
init
Initialize iroha in the current Git repository so agents share approved engineering memory. Use when the user asks to set up, install, or initialize iroha in a repo. Do not use for unrelated project scaffolding or for repositories that are already initialized (rerunning is safe but unnecessary).
dashboard
Open the local iroha review dashboard, where a human approves or rejects candidate knowledge and browses the memory graph. Use when the user wants to review the iroha queue, approve or reject candidates, or open the dashboard. Do not use for unrelated local web servers or UIs.
doctor
Diagnose the iroha installation — platform integration, hook trust, MCP connectivity, database capabilities, and Git access. Use when iroha behaves unexpectedly, a hook or the MCP server seems inactive, or the user asks to check or verify the iroha setup. Do not use for unrelated environment diagnostics.
search
Search approved iroha engineering memory — decisions, rules, incidents, patterns, and session summaries — across Japanese, English, and code. Use when the user asks what iroha knows, why a past decision was made, or which rules apply here. Do not use for general web search or for searching source files directly.
sync
Rebuild the local iroha index from the Git-tracked .iroha/ canonical files. Use when the user asks to sync, refresh, or rebuild iroha memory — typically after pulling teammate changes or resolving a merge. Do not use for unrelated file synchronization or version control operations.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.