Generate project-tailored AI review skills by collecting system-specific knowledge. Complements pr-review-toolkit with project-specific review perspectives.
This skill should be used when the user asks to "backtest review skills", "test detection rate", "バックテスト", "レビュースキルをテスト", "検出率を測定", "過去のバグで検証", or wants to verify that generated review skills can detect known bugs by replaying historical states.
This skill should be used when the user asks to "build review skills", "generate review skills", "create review perspectives", "build review setup", "レビュースキルを生成", "レビュースキルをビルド", "レビューを作って", or after interview skill has populated the knowledge-base. This is the core of tailored-reviewer: it builds project-specific SKILL.md files that form a complete review system.
This skill should be used when the user asks to "debug review skills", "validate generated skills", "check skill quality", "スキルをデバッグ", "生成スキルを検証", or automatically after build-skills completes. Validates that generated review skills are structurally correct, comprehensive, project-specific, and behaviorally sound.
This skill should be used when the user asks to "check project health", "run health score", "health check", "プロジェクトの健康状態", "ヘルススコア", "健全性チェック", or on a schedule via cowork. Operates independently from review skills.
This skill should be used when the user asks to "set up tailored review", "interview for review", "collect project information", "initialize review project", "プロジェクト情報を収集", "レビュー用の情報を集めて", "インタビューして", or needs to collect project-specific knowledge for review skill generation. Also triggered when existing knowledge-base files have stale last_verified dates, or when tailored-reviewer version has changed since last interview.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
このリポジトリは、私個人が日常的に使っている Claude Code 用のエージェント/プラグインを公開しているものです。
主用途は 自分自身と自分の所属する環境で使うことですが、他の方が使うことを妨げる意図はありません。
自由に使ってください。
このリポジトリの内容は Apache License 2.0 のもとで公開されています。
詳細は LICENSE ファイルを参照してください。
このリポジトリは 個人利用を主目的としているため、
あらかじめご了承ください。
ただし、
ので、必要に応じて好きな形に育ててください。
理由はシンプルです。
そのため「共同開発前提」にはしていません。
一方で、
ことは歓迎しています。
Claude のモデルや公式エージェントは今後確実に進化していくと思っています。
このリポジトリのエージェントたちは、最終的には不要になる可能性が高いです。
それでも今これを作っている理由は、
現時点では、エージェントやプロジェクトが
「迷子にならないためのガードレール」がまだ足りない
と感じているからです。
そういったことを防ぐための 暫定的な補助輪として、このエージェント群を追加しています。
project-coordinator プラグインは Agent Teams に対応しています。
coordinator と investigator がチームメイトとして並行動作し、直接メッセージをやり取りできます。
Agent Teams は実験的機能のため、デフォルトでは無効です。
有効にするには settings.json に以下を追加してください:
{
"env": {
"CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1"
}
}
無効の場合は従来のサブエージェント方式にフォールバックします。
これは「完成されたフレームワーク」ではありません。
あくまで 今の自分にとって必要な道具です。
そのくらいの距離感で付き合ってもらえると嬉しいです。
This repository contains Claude Code agents and plugins that I primarily use for my own work.
While it is published publicly, its main purpose is personal use, not community-driven development.
Anyone is free to use it.
The contents of this repository are released under the Apache License, Version 2.0.
See the LICENSE file for full details.
This repository is not intended as a collaborative project.
Please understand this in advance.
However:
The reasons are simple:
That is why this is not run as a shared project.
At the same time, I welcome others who:
Claude models and official agents will almost certainly improve over time.
These agents may eventually become unnecessary.
They exist now because I believe:
At the moment, there are not enough guardrails to keep agents and projects from drifting.
Specifically:
These agents serve as temporary guardrails to prevent that.
The project-coordinator plugin supports Agent Teams.
The coordinator and investigator run as teammates, communicating directly via messages.
Agent Teams is experimental and disabled by default.
To enable, add the following to your settings.json:
{
"env": {
"CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1"
}
}
When disabled, the plugin falls back to the traditional subagent approach.
This is not a polished framework.
It is simply a set of tools that are useful to me right now.
That is the intended relationship.
npx claudepluginhub suzuki0keiichi/claude-plugins-suzuki0keiichi --plugin tailored-reviewerOperate remote machines via SSH
A Claude agent that coordinates multi-step projects by maintaining purpose, plans, and research logs, ensuring steady progress without owning scope, budget, or decisions.
Enforces alignment between all product decisions and the product’s declared concept, preventing vision erosion caused by convenience, politics, or technical shortcuts.
Code review plugin with a standalone reviewer agent and two skill strategies: disposable subagents for one-shot reviews and persistent team members for iterative reviews
Slash commands that launch Agent Teams for research, debugging, and feature implementation with code review gates
Complete project development toolkit: 23 agents, 23 slash commands, 29 lifecycle hooks, and 69 reusable skills for Claude Code workflows
Harness for Claude Code — skills, /harness:* slash commands, persona subagents, lifecycle hooks, and MCP tools without per-repo `harness setup`. Sibling plugins exist for Cursor, Gemini CLI, and Codex.
Automated code review for pull requests using multiple specialized agents with confidence-based scoring
Agent Teams orchestration, governance hooks, multi-AI review, memento skill intelligence, and project management skills for Claude Code