Kt Search Release
jillesvangurp/kt-search
A skill your agent uses when the user wants to cut, publish, tag, or create a GitHub release for kt-search, especially when the task includes version bumping, validating that commits are pushed…
A skill your agent uses when reviewing the Harmonica restart plan against reality — after a phase PR or milestone merges, before proposing the next phase, or when asked "are the specs up to date" /…
Install Plan Review
$ npx skills add KenjiOhtsuka/harmonica --skill plan-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install KenjiOhtsuka/harmonica plan-review --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/KenjiOhtsuka/harmonica.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.opencode/skills/plan-review .claude/skills/plan-review && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "plan-review" agent skill from https://github.com/KenjiOhtsuka/harmonica/tree/develop/.opencode/skills/plan-review into .claude/skills/plan-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-review", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/KenjiOhtsuka/harmonica/tree/develop/.opencode/skills/plan-reviewType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add KenjiOhtsuka/harmonica --skill plan-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install KenjiOhtsuka/harmonica plan-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/KenjiOhtsuka/harmonica.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.opencode/skills/plan-review .agents/skills/plan-review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "plan-review" agent skill from https://github.com/KenjiOhtsuka/harmonica/tree/develop/.opencode/skills/plan-review into .agents/skills/plan-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-review", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add KenjiOhtsuka/harmonica --skill plan-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install KenjiOhtsuka/harmonica plan-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/KenjiOhtsuka/harmonica.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.opencode/skills/plan-review .cursor/skills/plan-review && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "plan-review" agent skill from https://github.com/KenjiOhtsuka/harmonica/tree/develop/.opencode/skills/plan-review into .cursor/skills/plan-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-review", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/KenjiOhtsuka/harmonica.git --path .opencode/skills/plan-review--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add KenjiOhtsuka/harmonica --skill plan-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install KenjiOhtsuka/harmonica plan-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/KenjiOhtsuka/harmonica.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.opencode/skills/plan-review .gemini/skills/plan-review && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "plan-review" agent skill from https://github.com/KenjiOhtsuka/harmonica/tree/develop/.opencode/skills/plan-review into .gemini/skills/plan-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-review", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install KenjiOhtsuka/harmonica plan-reviewInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add KenjiOhtsuka/harmonica --skill plan-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/KenjiOhtsuka/harmonica.git skills-src && mkdir -p .github/skills && cp -r skills-src/.opencode/skills/plan-review .github/skills/plan-review && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "plan-review" agent skill from https://github.com/KenjiOhtsuka/harmonica/tree/develop/.opencode/skills/plan-review into .github/skills/plan-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-review", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add KenjiOhtsuka/harmonica --skill plan-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install KenjiOhtsuka/harmonica plan-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/KenjiOhtsuka/harmonica.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.opencode/skills/plan-review .opencode/skills/plan-review && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "plan-review" agent skill from https://github.com/KenjiOhtsuka/harmonica/tree/develop/.opencode/skills/plan-review into .opencode/skills/plan-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-review", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
plan-review- GitHub stars
- 131
- Token cost
- ~1k tokens
- SKILL.md length
- 516 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when reviewing the Harmonica restart plan against reality — after a phase PR or milestone merges, before proposing the next phase, or when asked "are the specs up to date" /…
- Works in 6 steps: Gather ground truth → Diff the docs against ground truth → Apply updates → …
- Reviewing the Harmonica restart plan against reality — after a phase PR
- SKILL.md covers When to run, Scope and Steps
- Calls gh and git
What it does
Plan Review is an agent skill from KenjiOhtsuka/harmonica. Use when reviewing the Harmonica restart plan against reality — after a phase PR or milestone merges, before proposing the next phase, or when asked "are the specs up to date" / "what should we do next". Reconciles spec/plan.md, spec/tech-notes.md, and spec/issues-triage.md with the actual repo (git log, GitHub issues/PRs, dependency versions, test counts), applies updates to spec/, then verifies with the spec-review agent.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Databases, covering Project management, Database migrations and Android development. It works with Git, Gradle, GitHub and Kotlin. The repository describes itself as: Kotlin Database Migration Tool. This tool makes it really easy to create table, index, add columns, and so on, with Kotlin DSL. The licence is MIT.
When your agent uses it
- Reviewing the Harmonica restart plan against reality — after a phase PR
- Milestone merges
- Before proposing the next phase
- Asked are the specs up to date / what should we do next
Example prompts
- “are the specs up to date”
- “what should we do next”
- “/plan-review”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 32e06c9. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
ghgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh and git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Plan Review loads about 1k tokens when it runs. Until then it costs about 110 tokens; SKILL.md has 516 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from KenjiOhtsuka/harmonica at commit 32e06c9, republished under its MIT licence (© KenjiOhtsuka). 516 words, ~1,004 tokens.
Download SKILL.mdSave it as
.claude/skills/plan-review/SKILL.md (or your agent's skills folder).- name
- plan-review
- description
- Use when reviewing the Harmonica restart plan against reality — after a phase PR or milestone merges, before proposing the next phase, or when asked "are the specs up to date" / "what should we do next". Reconciles spec/plan.md, spec/tech-notes.md, and spec/issues-triage.md with the actual repo (git log, GitHub issues/PRs, dependency versions, test counts), applies updates to spec/, then verifies with the spec-review agent.
Plan Review
The spec/ planning docs are the source of truth and go stale every time a
phase PR merges. This workflow reconciles them with reality: gather ground
truth, diff the docs, apply updates, verify. Edit spec/ only; every change
goes through a small PR against develop, never a direct push.
When to run
- After any phase PR or milestone merge.
- Before proposing the next phase of work.
- When the user asks "are the specs up to date?" / "what should we do next?".
Scope
Keep in sync: spec/plan.md, spec/tech-notes.md, spec/issues-triage.md.
Do not touch spec/ci.md, spec/testing.md, spec/exposed-integration.md,
or spec/README.md unless a finding specifically requires it.
Steps
1. Gather ground truth
Run these and record the results before touching any doc:
git fetch originthengit log --oneline origin/develop -15— recent merges.gh pr list --state openandgh pr list --state merged --limit 25— PR states.gh issue list --state open— note the exact open count.- Grep versions from the build:
gradle/wrapper/gradle-wrapper.properties,gradle.properties, root/core/gradle-pluginbuild.gradle.kts,settings.gradle.kts(wrapper, kotlin, junit, plugin-publish, dokka, test deps). ./gradlew test(JDK 25, this machine) for the authoritative test count and build health. Static@Testgrep counts drift from the real JUnit count — trust the Gradle output, not the source grep.
2. Diff the docs against ground truth
For each of the three docs, find every claim that disagrees with reality:
- plan.md: phase status blocks (
implemented/merged, PR numbers, dates, test counts); the phase checklists; §6 resolved/open decisions; §3 branch strategy notes. - tech-notes.md: dependency table rows still marked
pending/untouchedthat are nowDONE(add the PR ref); self-contradictions between a table row and a later note; test counts; repository/protocol notes. - issues-triage.md: the open-issue count in the header (re-snapshot); issues resolved by the work (move them out of the active table, note the closing PR); new issues created since the snapshot (add them); stale cross-references.
Cross-check the three docs against each other — no contradictions.
Show full SKILL.md (201 more words)Show less
3. Apply updates
- One logical change per edit; preserve the existing style and table format.
- Mark resolved issues as resolved in the docs with the PR reference, but do not close the GitHub issues — that is a separate user decision.
- Update the "Snapshot ...
<date>" header in issues-triage.md to the actual review date and the current open-issue count.
4. Verify
- Delegate a final pass to the
spec-reviewagent (read-only) against the updated docs. Fix any BLOCKER/WARNING findings it reports.
5. Open a PR
- Commit, push, and open the PR only when the user has explicitly asked for the reconcile to land as a PR; otherwise present the edits and ask first.
- Commit the spec changes on a
docs/...branch cut from the currentorigin/develop(fetch first; never cut from a sibling unmerged branch). - Push it and open a small PR against
developtitled around what the reconcile covers. - Do not close GitHub issues yourself — that remains a user decision; list in the PR body the issues this reconcile marks as resolved, with the PR that resolves each.
6. Report
Summarize: what changed in each doc, the PR URL, the authoritative test count, and a list of GitHub issues the user should close.
© KenjiOhtsuka, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .opencode/skills/plan-review of KenjiOhtsuka/harmonica.
Open the folder on GitHubat commit 32e06c9
Compare with similar skills
Plan Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Plan Review this skillKenjiOhtsuka/harmonica | 131 | — | ~1k | Automated safety check: Pass | MIT | |
| Kt Search Releasejillesvangurp/kt-search | 155 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Add API ReferenceJetBrains/kotlin-web-site | 1.6k | — | ~5.3k | Automated safety check: Pass | Apache-2.0 | |
| Releasesol4k/sol4k | 135 | — | ~949 | Automated safety check: Pass | Apache-2.0 | |
| Git GitHub Opsc5inco/compose-pokedexer | 143 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Kotlin Exposed Patternsaffaan-m/ECC | 277k | 2 repos | ~5.2k | Automated safety check: Pass | MIT |
Similar skills
- Official
Add API Reference
JetBrains/kotlin-web-site
Publish a new kotlinx library API reference on kotlinlang.org/api via the TeamCity Kotlin DSL, the way kotlinx.coroutines, kotlinx.serialization, kotlinx-datetime and kotlinx-io are published.
Release
sol4k/sol4k
Bump the sol4k library version everywhere, open a release PR, and draft GitHub release notes.
Git GitHub Ops
c5inco/compose-pokedexer
Handles Pokedexer Git and GitHub workflows: inspect changes, prepare commit messages, manage branches and pushes, and create or update issues and pull requests with safe file-based inputs.
Kotlin Exposed Patterns
affaan-m/ECC
JetBrains Exposed ORM 模式，包括 DSL 查询、DAO 模式、事务、HikariCP 连接池、Flyway 迁移和仓库模式。
Kotlin Exposed Patterns
affaan-m/ECC
JetBrains Exposed ORM パターン（DSL クエリ、DAO パターン、トランザクション、HikariCP 接続プーリング、Flyway マイグレーション、リポジトリパターンを含む）。
More from KenjiOhtsuka/harmonica
Harmonica Dev
KenjiOhtsuka/harmonica
A skill your agent uses when working on the Harmonica Kotlin DB migration tool — planning, phase work, PRs, or anything touching this repo.
Related
Categories
Questions about Plan Review
What does Plan Review do?
A skill your agent uses when reviewing the Harmonica restart plan against reality — after a phase PR or milestone merges, before proposing the next phase, or when asked "are the specs up to date" /…. Plan Review is an agent skill from KenjiOhtsuka/harmonica. Use when reviewing the Harmonica restart plan against reality — after a phase PR or milestone merges, before proposing the next phase, or when asked "are the specs up to date" / "what should we do next".
When should I use Plan Review?
Plan Review fits situations like: reviewing the Harmonica restart plan against reality — after a phase PR; milestone merges; before proposing the next phase; asked are the specs up to date / what should we do next.
How do I install Plan Review in Claude Code?
Run `npx skills add KenjiOhtsuka/harmonica --skill plan-review -a claude-code`. Or copy the skill folder (.opencode/skills/plan-review in KenjiOhtsuka/harmonica) into .claude/skills/plan-review in your project. Claude Code loads it when a task matches its description.
How do I install Plan Review in Codex?
Run `npx skills add KenjiOhtsuka/harmonica --skill plan-review -a codex`. Or copy the skill folder (.opencode/skills/plan-review in KenjiOhtsuka/harmonica) into .agents/skills/plan-review in your project. Codex loads it when a task matches its description.
Can I use Plan Review in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add KenjiOhtsuka/harmonica --skill plan-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/plan-review, .gemini/skills/plan-review, .github/skills/plan-review and .opencode/skills/plan-review in your project.
What does Plan Review need to run?
Going by SKILL.md and its folder, Plan Review needs the command-line tools its instructions call (gh and git).
Does Plan Review access the network?
SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Plan Review safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Plan Review use?
Plan Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Plan Review use?
About 1k tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Plan Review?
Skills that share tags, products or a category with Plan Review: Kt Search Release (jillesvangurp/kt-search, 155 stars), Add API Reference (JetBrains/kotlin-web-site, 1.6k stars), Release (sol4k/sol4k, 135 stars) and Git GitHub Ops (c5inco/compose-pokedexer, 143 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Plan Review?
KenjiOhtsuka (a GitHub user) maintains it in KenjiOhtsuka/harmonica, which has 131 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on September 22, 2026.
Source: KenjiOhtsuka/harmonica on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.