What is task-view?
task-view turns a coding agent’s account of a code change into an interactive review page, helping developers understand how modified files, functions, tests, and endpoints relate. It presents the change as a graph, step-by-step flows, a diff map, and claims with supporting evidence, alongside the relevant code and the agent’s explanation. The tool works across programming languages and repositories, and creates an offline HTML review that can be kept or shared.
task-view Features:
Change Graph: View changed functions, components, endpoints, and tests as connected nodes, grouped by repository, with controls for showing additional context.
Stepwise Flows: Follow paths through a change from affected entry points to boundaries, with branches and tests attached to the steps they cover.
Code Inspector: Open a node, edge, hunk, or finding to see relevant code, its diff or after-change version, agent explanations, relations, and findings.
Git Checks: Check whether referenced files, lines, and commits resolve against Git, and see whether a reference matches the code and diff.
Diff Coverage: Use a per-file map to see which changed hunks are described by review nodes, including changes that are only partly covered or not mentioned.
Offline Reports: Build a standalone HTML review for each task; generating it reads files and uses read-only Git without running tests or builds.
task-view Benefits:
Less Reconstruction: Reviewers can spend less effort piecing together call paths and file relationships from separate diffs, and more effort judging the code.
Clearer Coverage: The diff map makes omissions easier to spot, so reviewers can check whether the account addresses all changed hunks.
Grounded Review: Visible verification states help distinguish references that match the repository from unresolved or contradicted details and agent statements.
Portable Sharing: A self-contained HTML file can be retained or shared without requiring reviewers to use a hosted review service.
Language Flexibility: Teams can use the same review approach for changes spanning different languages and repositories, without relying on language-specific parsing.
Use Cases:
Agent Code Review: Ask a coding agent to describe a completed task, then inspect the resulting map before deciding whether its code change is ready.
Cross-Repository Changes: Trace a change that spans a web client and API, following related code and endpoints across repository boundaries.
Test Coverage Review: Follow a changed feature from its entry point through the affected code and check which tests the review associates with each step.
Large Diff Triage: Start with flows or grouped graph nodes to understand a broad change, then use the diff map to locate hunks the account does not explain.
Committed Change Review: Have an agent create a review account for an already committed change without asking it to modify the code.

