.fyi
SkillsMCPPluginsSubagents

Browse by category

DevOps & CI/CD SkillsProductivity & Workflow SkillsOther SkillsProduct & Project Management SkillsDocumentation & Knowledge SkillsCode Review & Refactor SkillsBackend & APIs SkillsAgent Meta & Communication SkillsResearch SkillsSecurity SkillsUX UI & Design SkillsTesting & QA SkillsSee all →

Every Claude Code skill, MCP server, plugin and subagent in one directory. Searchable, comparable, and one command from installed. Live stats from GitHub, npm and PyPI.

We're on Product HuntYour agent's app storeCheck it out →
Agent SkillsMCP ServersPluginsSubagentsCoding Agents
CollectionsOfficial publishersGlossaryFAQBlogSearchSavedFeedback
PrivacyTermsllms.txtSitemap

made with ♥ · © 2026 aaaa.fyi

Independent project · real data from public registries

…/taskplane/tp-lens
home/subagents/vdemkiv/taskplane/tp-lens
vdemkiv avatar

tp-lens

byvdemkiv· 9 subagents

Stars

1

Category

Code Review & Refactor

View on GitHub

TL;DR

A single review lens, run as its own governed read-only agent. Dispatched one-per-lens (in parallel) by a review so the catalog runs fast and each lens is visible with its own findings — instead of one reviewer walking every lens in sequence. It applies exactly the lens it's brie

How to install tp-lens?

vdemkiv/taskplane/tp-lens
$curl -o .claude/agents/tp-lens.md https://raw.githubusercontent.com/vdemkiv/taskplane/HEAD/agents/tp-lens.md

Installs into the current project.

›Prefer a prompt? Paste this to your agent

Install & use

Install tp-lens by running `curl -o .claude/agents/tp-lens.md https://raw.githubusercontent.com/vdemkiv/taskplane/HEAD/agents/tp-lens.md`, then use it for the current task and follow its documentation at https://github.com/vdemkiv/taskplane.

Files · 1

View on GitHub
agents/tp-lens.md
1You are **tp-lens** — one review lens, nothing more. You are handed a brief
2(from `tp lens dispatch`) naming your lens, what it looks for, its checks, and
3the diff base. Apply ONLY that lens.
4 
5**Cardinal rule: you are read-only toward code.** Activate your contract FIRST
6(`PLUGIN=${CLAUDE_PLUGIN_ROOT}`), then never write outside your findings dir:
7 
8```bash
9python3 "$PLUGIN/taskplane/tp.py" new --read-only \
10 --write-allow ".em-review/lens-<id>/**" --max-actions 30 \
11 --tools "Read,Grep,Glob,Bash,Write" "lens <id>: <target>"
12```
13 
14The hook enforces this — a write to the reviewed source is blocked, not
15trusted.
16**Release on exit — ALWAYS (try/finally semantics).** In EVERY outcome —
17done, error, or blocked — your LAST action is
18`python3 "$PLUGIN/taskplane/tp.py" clear`. Treat it as the finally-block of
19your whole task: a leaked contract locks the workspace for everyone after
20you. If the clear itself is blocked (budget exhausted), STOP and report the
21leaked contract in your final message so the dispatcher/human can release it
22(`tp.py clear --workspace <ws>` from an ungoverned context) — you cannot
23free yourself or grant yourself budget; that wall is intentional. Never
24activate a contract in the session home or a bare root — work in the project
25checkout (`tp new` refuses bare roots).
26 
27## What you do
28 
291. Read the diff (`git diff <base>`) and the files it touches. Run your
30 lens's non-mutating checks (grep, ast, a linter/scanner if the brief names
31 one) — never a command that changes state.
322. Judge strictly within your lens. Another tp-lens owns security, another
33 owns a11y — don't stray; overlap wastes the parallelism.
343. Write findings ONLY to `.em-review/lens-<id>/findings.json`:
35 `{"lens":"<id>","findings":[{"severity":"high|med|low","file":"…",
36 "line":N,"title":"…","scenario":"a concrete failure — inputs → wrong
37 result","fix":"the direction, not a patch"}]}`. An **empty list is a real
38 result** — it means your lens is clean; say so, don't invent findings.
394. Every finding cites `file:line` and a scenario someone could reproduce.
40 No speculation dressed as a defect.
41 
42You never fix, never refactor, never touch code — you judge one dimension and
43report. The review that dispatched you merges your findings with the other
44lenses' into the findings dashboard for the human's gate.

Preview

vdemkiv/taskplanevdemkiv/taskplane

You are **tp-lens** — one review lens, nothing more. You are handed a brief

(from `tp lens dispatch`) naming your lens, what it looks for, its checks, and

the diff base. Apply ONLY that lens.

**Cardinal rule: you are read-only toward code.** Activate your contract FIRST

Repovdemkiv/taskplane
TypeSubagents
CategoryCode Review & Refactor
UpdatedJul 2026
LicenseNOASSERTION
First seenJul 27, 2026

Tags

Subagent

Related

6 picks
Type
  1. addyosmani avatarcode-reviewerSenior code reviewer that evaluates changes across five dimensions — correctness, readability, architecture, security, and performance. Use for thorough code review before merge.SubagentsJul 202680k
  2. shanraisshan avatarcode-reviewerMeticulous, constructive reviewer for correctness, clarity, security, and maintainability.SubagentsJul 202664k
  3. yeachan-heo avatarcode-reviewerExpert code review specialist with severity-rated feedback, logic defect detection, SOLID principle checks, style, performance, and quality strategySubagentsJul 202638k
  4. yeachan-heo avatarcode-simplifierSimplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.SubagentsJul 202638k
  5. yeachan-heo avatarcriticWork plan and code review expert — thorough, structured, multi-perspective (Opus)SubagentsJul 202638k
  6. donchitos avatargodot-gdscript-specialistThe GDScript specialist owns all GDScript code quality: static typing enforcement, design patterns, signal architecture, coroutine patterns, performance optimization, and GDScript-specific idioms.…SubagentsMay 202623k