See the example
Open a real Shopify POS migration report to learn how findings, source links, and candidate edits are presented.
Shopify migration review · early preview
Know what changed.
Review the fix.
Specfaro checks known Shopify migration patterns in your code, links each finding to the official source, and prepares a patch you can inspect before changing anything.
✦ Try a public repository without an account, or scan private code locally.
specfaro / migration preview01 / 03
SHOPIFY API 2026-10
Breaking change found✳
POS UI extension · staff member session field
extensions/register/src/App.tsx line 2
− session.currentSession.staffMemberId
+ session.staffMember.value?.id
Candidate patch ready for review
START IN MINUTES
Choose how to try it.
Start with an example, scan public code in your browser, or keep a private repository on your machine.
Scan by URL
Paste owner/repository or a GitHub URL. No GitHub login or token is required. The web scan cannot write to the repo.
Run it locally
Download the Python kit to scan your checkout. Its optional agent reproduces an error, tries a bounded fix, runs your tests in temporary copies, and can save a report. Project commands run on your chosen machine or CI runner. AI is opt-in and sends selected excerpts to DeepSeek.
Download local kit ↓Local quick startUnzip the kit, then run this from your repository directory. Python 3.12+ recommended. The included README covers build, test, response-contract, and POS preview checks.
python path/to/specfaro-local-kit/cli.py . --target 2026-10The local kit is a snapshot of reviewed rules. Verify its SHA-256 checksum, check current source status, and test against a Shopify development shop before merging.CONNECTED REPAIR / PRIVATE PILOT
Connect a repository. See every decision.
Authorize the Specfaro GitHub App for selected repositories, choose the API version, and opt in to sending focused code and failure context to DeepSeek. Eligible failed CI runs wake an isolated worker. A separate verifier checks the patch and records a downloadable 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 your access and configure each repository. Specfaro will not start AI repair until you approve model data sharing for that repository.
YOUR SELECTED REPOSITORIES
GitHub account
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; any active work is stopped.
SHOPIFY + STRIPE / SOURCE REGISTRY
What Specfaro knows today.
Official Shopify and Stripe sources are checked and indexed. New announcements and schema changes enter a review queue; they do not become code edits automatically.
SOURCE CHECKLoading…
LATEST STABLE—From Shopify's version schedule
IMPLEMENTED RULES—Reviewed migration patterns
ANNOUNCEMENTS TO TRIAGE—Recent feed items, not necessarily relevant
Versions in scope
Implemented checks
Recent Shopify announcements
These are observed source items awaiting review. An item appears in “Implemented checks” only after a tested rule exists.
This is a tracked subset of Shopify changes, not a complete API schema. Official versioning guide ↗
01DetectFind version references and known patterns
02ProposeGenerate narrow, readable code edits
03ReviewInspect the diff and source guidance
THE AGENT / LIVE PREVIEW
Put your code to the test.
Paste a public GitHub repository. Specfaro reads eligible source files, checks its reviewed Shopify rules, and returns findings and any candidate patch for inspection.
PROACTIVE / READ ONLY
Check a version upgrade before CI breaks.
Scan a public repository at one Git commit for two documented changes: the Shopify POS staff signal and Stripe PaymentIntent charges removal. Results distinguish future upgrade exposure from possible current mismatch. No code runs and no patch is published.
Selected source files only · exact commit shown · static findings need target-version tests and provider version checks.ANALYSIS COMPLETE
Migration report
0FILES SCANNED
0FINDINGS
0CANDIDATE EDITS
What this report verifies
Static matching alone cannot prove the whole app is compatible. Review the linked source, inspect the patch, check Shopify API Health and the served API version, then run app-specific tests before merging.
DEEPSEEK / RETRIEVED SOURCES
AI migration proposal
Exact code matching is checked here. Project tests and live API responses require a connected development environment before merging.
PROPOSED PATCH
ISSUE-LED REPAIR / PREVIEW
Start with what broke.
Describe a failure in a public repository. Specfaro locates likely code and retrieves relevant Shopify or Stripe documentation. DeepSeek can propose up to four bounded edits when you opt in.
Issue analysis
This web preview does not run build, regression, or live API tests. A proposed edit is unverified until the local verifier observes a failing baseline and passing patched tests.
THE WORKFLOW
From changelog to code change.
Track the change
Rules map documented Shopify releases to concrete code patterns and include a link to the source for every finding.
Find affected code
Specfaro scans a public repository or a local checkout for version references and known migration points.
Prepare the edit
Exact substitutions become a unified diff. Changes needing context are marked for manual review.
TRUST & ACCESS
You decide what runs and what changes.
Clear boundaries for this preview, with a source link and verification path for every migration finding.
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.
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 explicitly 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 require target-version evidence. A code bug may have no relevant provider document, which the report states. Public scans do not run build tests or live API calls.
See the limits live
Source status shows how much of Shopify and Stripe documentation is indexed and fresh. The public migration 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 requires a selected-repository GitHub App installation and separate opt-in.
CURRENT SCOPE
Focused on the fixes
we can show.
This preview covers Shopify POS session migration in 2026-10, collection metafield integer field renames in 2027-01, API version references, and selected changes that require 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; no patch is merged or deployed automatically. A production rollout needs broader failure coverage and live provider checks.
Read Shopify versioning guidance