mrkeyoor.comAsk

Qiuner/birdviewtested 02 Oct 2026commit acddbf0

birdview review

Try Birdview 0.3.1 when reviewing an agent's architectural assumptions before a substantial edit would help you decide whether to approve its plan.

  • Install 15 s
  • Build 10 s
92/92tests passed
  • 22 packages
Dev Toolsevaluationupdated 01 Nov 2026
+12stars / 7d

Use Birdview to inspect a coding agent's architecture assumptions and proposed file scope before approving a substantial edit. Birdview 0.3.1 displays agent-declared snapshots without independently observing edits or enforcing filesystem restrictions. Its standalone HTML map brings architecture, reviewed constraints and proposed changes into one reviewable artifact. Our run tested repository commands, not the accuracy of a map or an agent's compliance with an approved plan.

Verdict

Try Birdview 0.3.1 when reviewing an agent's architectural assumptions before a substantial edit would help you decide whether to approve its plan. Our run on 2026-10-02 at commit acddbf0 recorded installation at 15 seconds, build at 10 seconds and the test command at 28 seconds, each with exit code 0. The stored parser summary reports 92 passed and 0 failed, without establishing exhaustive coverage. Verify activation and map accuracy yourself, and inspect the conflicting audit records before relying on the installation.

We ran it

Lab card: what happened when we ran birdview
Lab card from our sandbox run
Screenshot of birdview (qiuner.github.io/birdview)
qiuner.github.io/birdview
Install✓ · 15s22 packages · 120 MB
Build✓ · 10s
Tests✓ · 28s92 passed · 0 failed of 92 (node:test)
Known vulns00 critical · 0 high · 0 moderate · 0 low (npm audit)
Repo197 files~5,037 lines of source · 2.6 MB · 2 CI workflows · tests dir

Answers from our run

Does birdview build from source?

Dependencies installed in 15 seconds (22 packages), and the build succeeded in 10 seconds. We cloned commit acddbf0 into a clean Debian container with 3 CPUs and no project-specific setup.

Do birdview's tests pass?

Yes. The project's own test command finished in 28 seconds and reported 92 passed, 0 failed (node:test).

Does birdview have known vulnerabilities in its dependencies?

npm audit found none in the dependency tree at the time of our run.

Who should not use birdview?

Teams requiring enforced file restrictions or independently observed agent activity.

What are the alternatives to birdview?

Code Review Graph, Superpowers. Try Birdview 0.

Setup3/5The documented bundle setup includes dependencies, doctor, project configuration and a fresh-task activation check. Our run did not establish activation.
Docs5/5The supplied documentation explains installation, invocation, data contracts and limitations, with English and Chinese guidance.
Community4/5GitHub feedback and a QQ group provide multiple documented contact routes. This rating does not establish participation, adoption or response quality.
Maturity3/5Recorded repository commands succeeded, but live agent behavior remains untested and the dependency and audit records are not reconciled.

Who it’s for

Codex and Claude Code users who want to inspect affected modules and source evidence before approving changes.
Maintainers who will compare the agent's architectural claims with the repository.
Teams that want a browser-readable review artifact with English and Chinese controls.

Who it’s NOT for

Teams requiring enforced file restrictions or independently observed agent activity.
Reviewers who need automatic updates rather than regenerated HTML snapshots.
Developers expecting schema validation to establish architectural accuracy or rule compliance.
Small fixes where a separate map would add more review work than it saves.

Setup reality

Our run on 2026-10-02 tested commit acddbf0 in our sandbox. The stored harness records a 15-second installation, a 10-second build and a 28-second test command. Each command returned exit code 0 without a recorded timeout. The stored parser summary reports 92 passed and 0 failed; it does not establish exhaustive unique test coverage.

The stored dependency summary lists 22 packages and 120 MB. The raw installation output reports 14 packages added, which does not reconcile the stored dependency count. The stored audit summary records zero advisories, while the installation tail reports one moderate severity vulnerability. Scan coverage is unknown because scannedPackages is absent. Neither advisory record establishes security.

Skill installation requires the complete GitHub bundle, dependencies, a doctor check and verification in a fresh agent task. Manual installation requires Node.js 18 or newer. Our run did not establish live agent activation.

Should you use Birdview?

Use Birdview when you want to question an agent's proposed scope before authorizing a change across several modules. Its map makes the agent explain ownership, relationships, applicable rules and planned checks in a form you can inspect. That review still depends on someone checking the explanation against source.

Birdview 0.3.1 displays agent-declared snapshots without independently observing edits or enforcing filesystem restrictions. Keep Git diffs, tests and code review in the workflow. The HTML page cannot establish that the agent changed only the approved files.

What our sandbox recorded

Our run on 2026-10-02 tested commit acddbf0 in our sandbox. The full revision is acddbf0f9496f50685ed916f8be8cad7b70f32d3, and the build output identifies Birdview 0.3.1. The attached sandbox configuration records lab-node:22, 3 CPUs and 8 GB of memory.

The stored harness records installation at 15 seconds, build at 10 seconds and the test command at 28 seconds. For each command, it stores a success flag, exit code, elapsed time and timeout flag. All three recorded exit codes are zero, with no recorded timeout. Test counts are stored separately as parsed summaries.

The attached stored parser summary reports 92 passed and 0 failed. The supplied raw test footer also reports 92 passed, 0 failed and 0 skipped. Those matching figures do not establish exhaustive unique test coverage. No new execution or complete-log reconciliation was performed. The footer's runner duration and the harness's command duration describe different timing scopes.

This run did not establish successful activation in a live coding-agent session, a completed browser test run, the accuracy of a map of another repository or compliance with an approved scope. Successful repository commands do not answer those questions.

The MrKeyoor testing methodology explains how the publisher records command outcomes and parsed counts. The supplied methodology page was fetched on 2026-10-31; it does not establish which methodology version governed this older run.

Installation succeeded, but the records disagree

The stored dependency summary records 22 packages and 120 MB on disk. The raw installation output reports 14 packages added. The supplied evidence does not reconcile those figures or establish that they count the same thing.

The stored npm audit summary records zero advisories at every listed severity. Separately, the raw installation tail reports "1 moderate severity vulnerability". Both records remain relevant; the successful installation does not resolve the discrepancy. Scan coverage is unknown because the supplied record has no scannedPackages field. Recheck the dependency tree and audit report for the revision you intend to install. Advisory totals are not a security assessment.

Validation checks the artifact's consistency

At the measured revision, validation checks structure and cross-record consistency, including sequence order, valid scope, targets and ownership references. It does not prove that architectural claims are true or that referenced source files exist.

The architecture file describes modules, ownership, relationships and evidence. The constraint catalog records reviewed rules and coverage. The activity file holds the task scope, progress and check results declared by the agent. Displaying a rule does not prove compliance, and confirmation does not mean tests passed.

Under the documented workflow, confirmation happens in the conversation and material scope changes require another confirmation. Version 0.3.1 requires regenerating the HTML and refreshing the browser when the artifact changes; live transport and automatic refresh are not implemented.

Verify activation after installing the bundle

Birdview needs its complete skill bundle, including scripts, schemas, assets, references and package files. Copying only SKILL.md is insufficient. The npm package is private, so a global npm installation is not the documented distribution route.

The installation guide separates dependency installation from the doctor check and agent activation. Doctor invokes an installed validation CLI and renders an example in memory. It does not exercise every worker CLI or prove that the host loaded the skill.

Start a fresh task with a map-only request. Check that the agent reads the skill, reports any existing map, delivers a browser-readable artifact and discloses missing constraint coverage. Inspect a module's ownership and cited evidence before approving a code-changing task.

On-demand invocation is the default; auto mode is optional. Project guidance relies on the host loading AGENTS.md or, for Claude Code, CLAUDE.md. These instructions do not intercept filesystem writes.

Keep the measured version separate from current features

Our recorded build identifies version 0.3.1. The supplied current README describes version 0.4.0, including architecture review and outside-scope impact features. Those features were not verified by our run. The README at the measured commit provides the relevant historical boundaries.

Alternatives answer different needs

Code Review Graph builds a structural map with Tree-sitter and serves compact context over MCP. Choose it when the immediate need is repository context and dependency analysis. It can complement a human review artifact; its supplied documentation does not establish an equivalent conversational scope-confirmation workflow.

Superpowers is a software development methodology for coding agents built from composable skills. Its documented workflow includes design, implementation planning, testing and review. Choose it for that broader process. Before combining it with Birdview, inspect their activation and confirmation rules; the supplied evidence does not establish conflict-free operation together.

What the scores mean

These editorial ratings describe the available evidence, not measured product performance. Setup ease runs from 1 for unresolved basic installation barriers to 3 for documented installation with several manual steps and 5 for a verified path through activation. Documentation runs from 1 for missing operating guidance to 3 for basic instructions and 5 for detailed setup, workflow and limitation guidance.

Community measures documented feedback access: 1 means no route, 3 means one route and 4 means multiple routes; 5 would require evidence of responsive support. It does not measure adoption. Maturity runs from 1 for unresolved basic command failures to 3 for successful repository commands with operational behavior untested and 5 for independently verified operation across the intended workflow.

The retained scores are setup ease 3, documentation 5, community 4 and maturity 3. GitHub feedback and a QQ group support the community score's narrow meaning. The maturity score remains limited by untested agent behavior and unresolved installation and audit records.

Alternatives

ProjectWhat it isPick it when
Code Review Graph gh↗A structural code map built with Tree-sitter that supplies compact context over MCP.Choose it for repository context and dependency analysis. Treat it as a potential complement to Birdview's review artifact, rather than an established replacement for scope confirmation.
Superpowers gh↗A software development methodology built from composable coding-agent skills.Choose it for a broader design, planning, testing and review process. Inspect overlapping activation and approval rules before combining it with Birdview.

What people are saying

  1. [velocity-scout] Qiuner/birdview

Sources

  1. Birdview repository and README
  2. Birdview v0.3.1 release
  3. Birdview installation guide
  4. Birdview skill instructions
  5. Birdview activation modes
  6. Birdview measured commit

More dev tools reviews