No account for a public scan
Enter a public repository URL. The web scanner fetches public code and has no GitHub write permission. For private code, the downloadable scanner runs in your checkout.
Example
Shopify 2026-10 took one field away from POS extensions.
In 2026-10, session.currentSession no longer carries staffMemberId. The signed-in staff member now lives at session.staffMember.value?.id, available since 2026-07. Specfaro finds every use, links the release note, and writes the replacement line.
export function Register({ session }) {- const staffId = session.currentSession.staffMemberId;+ const staffId = session.staffMember.value?.id; return <p>Signed in as {staffId}</p>; }
Checks
Every check points back to a changelog.
Each folder is one API release. Open it to see the rules inside; every rule links to the official entry it was written from. Patch rules get an exact edit. Review rules are flagged for you to change by hand.
New announcements wait in a review queue. A rule ships only after it passes against code that should match and code that should not. See live source status
Scanner
Paste a repository. Read the report.
Specfaro reads eligible source files from a public GitHub repository, runs its reviewed Shopify rules, and returns each finding with its source and any candidate patch.
Migration report
0Files scanned
0Findings
0Candidate edits
What this report verifies
Static matching cannot prove the whole app is compatible. Read the linked source, inspect the patch, check Shopify API Health and the API version your app is served, then run your own tests before merging.
AI migration proposal
Exact code matching is checked here. Project tests and live API responses need a connected development environment before merging.
Proposed patch
Check an upgrade before CI breaks. Read only
Scans one Git commit of a public repository for two documented changes: the Shopify POS staff field and Stripe's removal of charges from PaymentIntent. Results separate future upgrade exposure from a possible mismatch today, without running code or publishing a patch.
Get started
Three ways to run it.
Look at a finished report, scan public code from this page, or keep a private repository on your own machine.
See the example
A real Shopify POS migration report: how findings, source links and candidate edits are laid out.
Scan by URL
Paste
Go to the scannerowner/repositoryor a GitHub URL. You need no GitHub login or token, and the web scan cannot write to the repository.Run it on your machine
The Python kit scans your checkout. Its optional agent reproduces an error, tries a bounded fix and runs your tests in temporary copies. Project commands run where you choose. AI is opt-in and sends selected excerpts to DeepSeek.
Download the local kit
Local quick startUnzip the kit and run this from your repository directory. Python 3.12 or later. The bundled README covers build, test, response-contract and POS preview checks.
python path/to/specfaro-local-kit/cli.py . --target 2026-10
The kit is a snapshot of the reviewed rules. Verify its SHA-256 checksum, check current source status, and test against a Shopify development store before merging.
Issue repair
Start from what broke. Preview
Describe a failure in a public repository. Specfaro finds the likely code and pulls the relevant Shopify or Stripe documentation. If you opt in, DeepSeek can propose up to four bounded edits.
Issue analysis
This preview does not run build, regression or live API tests. A proposed edit stays unverified until the local verifier sees a failing baseline and passing patched tests.
Connected repair
Connect a repository. See every decision. Private pilot
Connect GitHub and choose repositories. Specfaro suggests the provider and the API version each repository runs on, shows what is missing, and waits for you to opt in to sending focused code and failure context to DeepSeek. An eligible failed CI run starts an isolated worker. A separate verifier checks the patch and records a report before any optional draft pull request.
Start with your GitHub account
Install the App on only the repositories you choose, then sign in to confirm access and configure each one. Specfaro will not start AI repair until you approve model data sharing.
GitHub account
Repositories
Add or remove repositories on GitHubSpecfaro reads package.json, package-lock.json, Shopify configuration, workflow files and Stripe client setup to suggest settings. It never writes to your repositories. The API version is the one each repository runs on, as pinned in its code or configuration, not the version of a particular change. Check every value before enabling.
Repair history
GitHub access is checked again before settings changes, private history and patch downloads. Sessions expire after 20 minutes and GitHub user tokens stay in server memory. Verified patches are fetched on demand from the private worker artifact and are not saved in the controller database. You can disable a repository at any time; active work stops.
Source status
What Specfaro knows right now.
Official Shopify and Stripe sources are checked and indexed on a schedule. New announcements and schema changes go into a review queue; none of them becomes a code edit automatically.
Source checkLoading
Latest stable—From Shopify's version schedule
Implemented rules—Reviewed migration patterns
Announcements to triage—Recent feed items, not all relevant
Versions in scope
Implemented checks
Recent Shopify announcements
Observed source items awaiting review. An item moves to implemented checks only after a tested rule exists.
A tracked subset of Shopify changes, not a complete API schema. Official versioning guide
Trust
You decide what runs and what changes.
The boundaries of this preview, stated plainly. Every migration finding comes with a source link and a way to verify it.
Review before editing
The web scanner returns findings and a downloadable diff. It cannot commit, open a pull request, deploy or merge. The local command is read only unless you add --write.
AI is optional
Opt in to send selected public code excerpts, your issue description when using issue repair, and relevant official passages to DeepSeek. Migration proposals need target-version evidence. A code bug may have no relevant provider document, and the report says so. Public scans do not run build tests or live API calls.
The limits are on this page
Source status shows how much Shopify and Stripe documentation is indexed and fresh. The public scanner covers a reviewed subset of Shopify changes; the connected Stripe repair pilot is separate and read only.
Public scan files are processed in memory and are not added to the source-document database. Standard web access logs may record requests. Never paste a private repository, token or secret into the public scanner. Connected repair needs a selected-repository GitHub App installation and a separate opt-in.
Scope
Narrow on purpose.
This preview covers the Shopify POS session change in 2026-10, collection metafield integer renames in 2027-01, API version references, and selected changes that need manual review.
The connected pilot independently verified repairs in the selected Shopify and Stripe test repositories. Only the Shopify pilot can open a draft PR; nothing is merged or deployed automatically. A production rollout needs broader failure coverage and live provider checks.
Shopify versioning guidance