Launching today

ViewDoctor

Launching today

SwiftUI checks for agents in multi-module repos

3 followers

SwiftUI checks for agents in multi-module repos

3 followers

Visit website

ViewDoctor gives coding agents a compact SwiftUI checkpoint after a coherent change, then runs a separate staged gate before commit. It includes new untracked Swift files, attaches ownership from SwiftPM, Tuist, or Xcode modules, and outputs agent JSON, text, full JSON, or SARIF. Everything runs locally. Version 0.1.7 keeps three deliberately narrow rules and reports when Tuist helpers make the static module graph incomplete.

Free

Launch tags:Developer Tools•GitHub

Launch Team

Context.devOne API to scrape, enrich, and extract the internet

Promoted

Maker

📌

I wanted a deterministic check I could run after an AI coding pass without feeding the repository back to another model. ViewDoctor maps module ownership from SwiftPM, Tuist, and Xcode manifests, then scans the current Git diff for three SwiftUI risks. The same result can go to a person as terminal text, an agent as bounded JSON, or GitHub code scanning as SARIF. Source stays on the machine. Version 0.1 is intentionally small. It does not prove performance regressions or enforce dependency direction yet. The next decision is rule coverage. Which deterministic SwiftUI check would save you the most review time without creating warning fatigue?

Report

1d ago

Forum Threads

p/viewdoctor

•

1d ago

Agent checkpoint or pre-commit gate?

A user asked whether ViewDoctor's diff scan should run after every coding-agent change or only before commit. The old workflow made both interpretations possible.

In 0.1.7 I split them:

Agent checkpoint after one coherent edit:

viewdoctor scan . --git-diff --format agent

View all