artilens

Visualize subagent, Agent tool, and delegated task activity from the current Claude Code session. Use when work was delegated or the user asks what agents/subagents did, what ran in the background, or how tasks were coordinated.

List, find, inspect, diff, resume, or update this project's locally registered artifacts. Use when the user references a previous artifact, asks what artifacts exist, wants artifact history, or wants to continue from an artifact.

Create a draggable planning, kanban, roadmap, or backlog board artifact with copy-as-prompt feedback. Use for task ordering, project boards, sprint planning, prioritization, or moving cards between columns.

Catalog available slash commands, ArtiLens skills, plugins, and contextual recommendations. Use when the user asks what commands/tools/skills are available, what ArtiLens can do, or what to run next.

Create an option comparison artifact with tradeoffs and a recommendation. Use when the user wants to compare approaches, architectures, libraries, plans, implementation choices, pros/cons, or decision options.

Inventory project context files — CLAUDE.md, AGENTS.md, rules, SKILL.md files, plans, and docs — with read-frequency from the current transcript. Use when the user asks what context is loaded, which files shaped the session, or before auditing stale or unused context files.

Create a dependency review artifact from real package metadata. Use when checking dependencies, package.json, outdated or deprecated packages, license risk, upgrade order, dependency health, or version cleanup.

Analyze CLAUDE.md, AGENTS.md, rules, skills, plans, and docs for stale, broken, or conflicting context guidance. Use when docs may be outdated, contradictory, stale, misleading, or need a health check.

Visualize real git status, changed files, a commit, or a remote diff as an artifact. Use when the user asks what changed, wants a repo/change overview, needs git status explained, or asks to inspect a commit or diff.

Create an incident, regression, bug investigation, or debugging artifact with timeline, metrics, and hypothesis table. Use for outages, postmortems, root-cause analysis, production issues, flaky failures, or debugging narratives.

Visualize the current Claude Code session's context health, token pressure, hot files, and compact/clear/handoff recommendation. Use when the user asks to see session context, context window, context usage, session health, handoff readiness, or whether to compact.

Build an annotated pull-request or branch walkthrough artifact from real git data. Use before review, when explaining a branch, preparing a PR, summarizing commits, or showing changed files and risks.

Create a release checklist, changelog, or ship-readiness artifact from real git history. Use before tagging, cutting a release, shipping a version, preparing release notes, or reviewing recent commits.

Visualize todos, plan checklists, progress, blockers, and next actions from the current transcript and project plan files. Use when the user asks for progress, task status, blockers, roadmap state, or the next safe task.

Visualize the current Claude Code session's real usage: cost, model token usage, cache tokens, line-change estimate, and MCP/skill share. Use when the user asks for usage, cost, spend, tokens, model usage, session stats, or "/usage"-style data.