Git repositories
Connect the repo and review any revision or diff — including the one that just landed.
AI schematic review · available now
AI schematic review, powered by the context of your entire electronics workflow.
A schematic is never just one file. Circuitly reviews schematic and layout the way your team does — against revision history, firmware, requirements, datasheets, MCAD context, component availability, and your own engineering standards — then gives you findings you can inspect and a report you can hand to anyone.
The first capability in the Circuitly harness · Same product, same login · Engineers approve every consequential action
CONNECTED CONTEXTsensor_gateway.gitrevs A · B · Csensor_gateway_revC.kicad_pcbenclosure/outline.steprequirements.mdfirmware/adc_cal.cTPS54331.pdfstock & EOL feedreview-checklist.md
The Circuitly review workspaceThe same product and login as the rest of the harness — review is a capability, not a separate app.
What you connect
Bring the design the way it already lives.
Connect the repository and the sources of truth around it. Every additional input makes the review stronger — and none of them require changing how your team works.
KiCad and Altium projects
Native schematic files, libraries, and project structure — not screenshots or exports.
Requirements and specs
The documents that define what the design must do, so coverage can be checked, not assumed.
Firmware sources
The code that runs against the hardware — pin maps, calibration constants, interface assumptions.
Datasheets
Component behavior, limits, and application guidance for the parts actually on the board.
Availability and lifecycle data
Stock, pricing, and EOL status for supported component data sources.
MCAD context
Board outline, enclosure fit, and keep-outs alongside the electrical sources.
What Circuitly examines
The review an isolated PDF can never do.
Because the review runs inside the harness, it can reason across everything you connected — not just inspect one drawing in isolation.
What changed, and why it matters
Diffs between revisions, traced to the requirements and circuits they affect.
Cross-domain inconsistencies
Pin assignments, calibration constants, and interface assumptions checked against the code.
Missing pins and missing information
Unconnected pins, absent decoupling, undocumented assumptions, placement-sensitive nets, keep-out conflicts with the mechanical outline, and gaps a reviewer would flag.
Availability and EOL risk
Parts going end-of-life or out of stock, surfaced before they become a respin.
Requirements coverage
Which requirements the design satisfies, which are at risk, and which nobody has addressed.
Organization-specific checks
Your review checklists and engineering standards, applied alongside Circuitly's native review logic.
Your standards, in Markdown
Teach Circuitly how your organization reviews.
Add Markdown instructions, checklists, and engineering standards to the repository. Circuitly applies them on every review — the institutional knowledge that usually lives in a senior engineer's head becomes a check that runs every time.
- Plain Markdown, versioned with the design.
No rule language to learn; edit the file, and the next review uses it. - Applied alongside native checks.
Findings from your standards are labeled so reviewers know where a rule came from. - Shared across the team.
Every project that connects the standard gets the same review discipline.
— review-checklist.md
# Power
- Every rail gets a test point and a bulk cap
- Regulators: verify FB divider against the rail spec
- Flag any part > $4 with a single supplier
# Connectors
- ESD protection on every external interface
- Mounting: no bottom-side connectors on rev A builds
# Handoff
- Open questions must name an owner
- BOM must resolve to orderable MPNs
# Power
- Every rail gets a test point and a bulk cap
- Regulators: verify FB divider against the rail spec
- Flag any part > $4 with a single supplier
# Connectors
- ESD protection on every external interface
- Mounting: no bottom-side connectors on rev A builds
# Handoff
- Open questions must name an owner
- BOM must resolve to orderable MPNs
What engineers receive
Findings you can interrogate. A report you can circulate.
The review lives in two forms: an interactive record for the engineers doing the work, and a polished PDF for everyone who just needs to read it.
Prioritized findings with evidence
Every finding links to the schematic objects, diffs, documents, and data behind it — accept, reject, or dig in.
Suggested next actions
Concrete proposals with their reasoning shown, ready for an engineer to approve or push back on.
A polished PDF report
Download it and circulate it internally — reviewers, managers, and contractors read it without creating an account.
Human in the loop
Circuitly proposes and explains. Engineers approve.
- Inspect the evidence.
Findings point back to schematic objects, revisions, rules, firmware lines, and documentation. - Accept, reject, or discuss.
Consequential actions wait for an engineer's approval — the record keeps that judgment visible. - Carry context forward.
Decisions from this review become context for the next revision, and for every other capability in the harness.
Why the harness matters
More context in, better review out.
Review is the first capability of the Circuitly harness — not a separate upload tool. That difference shows up in the findings.
Reviewing an isolated PDF
- Sees one drawing, frozen at export time
- No revision history — can't tell what changed or why
- Blind to firmware, requirements, and supply data
- Generic checklist, same for every company
- Findings live in comments nobody can trace
Reviewing inside Circuitly
- Reads the native design files and libraries
- Understands the diff and the revisions behind it
- Checks firmware, requirements, datasheets, and EOL data together
- Applies your Markdown standards next to native checks
- Findings stay linked to evidence — and to the next revision
Where teams use it
Review work that happens throughout the hardware lifecycle.
Start with the review your team already has on its plate this week.
Review your next revision with the full picture.
Connect a repository, run a review, and hand your team a report the same day — or talk to us about where AI belongs in your workflow first.