profile-resolver — Claude Code subagent: what it does, how to install
profile-resolver — a subagent that reads a diff and the worktree, works out which project profiles are active, and reports which checklists load. Handy when detection has to run apart from the review.
Elastic-2.0 ★ 155 updated 2026-10-29
/plugin marketplace add serpro69/claude-toolbox
/plugin install kk@claude-toolboxWhat profile-resolver does
The agent takes three inputs: the diff text, the worktree root, and the absolute path to the plugin install. It reads the shared detection procedure, opens DETECTION.md for every known profile, then applies the three-part rule in order: path signals, filename signals, content signals. Its toolset is read-only (Read, Grep, Glob).
Output is a table with one row per diff file, the matching profile and the concrete triggered_by value, followed by two lists. One holds the checklists that load, the other the ones that stay out with the Load-if reason. Files where nothing matched still get a row marked none.
The plugin root arrives under a ## Plugin Root heading. There is no shell here, so ${TOOLBOX_PLUGIN_ROOT} cannot be expanded by the agent itself, and without that heading it halts with an error rather than guessing a path. It never reviews code or writes findings, that stays with kk:code-reviewer. Checklist lookup is wired for the /kk:review-code phase only.
What it helps with
- keep profile detection separate from the review step
- see which signal fired for each file in the diff
- list the checklists that were skipped and why
- grade the detection on its own, apart from review output
- keep procedure files out of the main session's context
Example prompts for the agent
- Resolve the active profiles for this diff and tell me which checklists loaded and which were skipped.
- Run
profile-resolveron the staged diff. Detection only, no code findings. - Build the detection report for
Chart.yamlandvalues.yaml; I'll pass the worktree root next.
How to install profile-resolver
1Plugin marketplace
/plugin marketplace add serpro69/claude-toolbox/plugin install kk@claude-toolbox2Manually: put the files in place
.claude/agents/profile-resolver.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/profile-resolver.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/profile-resolver.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about profile-resolver
How do I install profile-resolver in Claude Code?
Run /plugin marketplace add serpro69/claude-toolbox, then /plugin install kk@claude-toolbox. The agent file lands at .claude/agents/profile-resolver.md.
What does profile-resolver do?
It resolves the active profiles for a diff and decides which of their checklists load. You get a structured report: a per-file signal table plus both checklist lists with the reasoning behind each call.
What do I have to pass to the agent?
The diff, the worktree root, and the absolute plugin path under a ## Plugin Root heading. Skip the last one and it stops with an error, since it has no shell to resolve environment variables.