A small setup.
A useful next check.
Choose the PR check or client-app journeys. The examples below show the setup; replace the app URL and project reference before running them.
GitHub Action
name: Antelier claim check
on:
pull_request:
types: [opened, synchronize, edited, reopened]
push:
issue_comment:
types: [created]
pull_request_review_comment:
types: [created]
permissions:
contents: read
pull-requests: write
checks: write
jobs:
claim-check:
if: ${{ github.event_name != 'push' || github.ref_name == github.event.repository.default_branch }}
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: antelier/action@v0- 1. Add the workflow.Create the file shown here in your repository. The Action checks opened, updated, edited, and reopened pull requests.
- 2. Open or update a PR.The source site describes one comment and one Check. Re-runs update the same comment.
- 3. Read “Needs your eyes.”Claims that the diff does not back require attention. A cited finding is the place to begin your review.
This file requests write access for pull-request comments and checks. Review the permissions and the Action source before adding it.
Read the Action source ↗Source-available, run-only license. GitHub today; GitLab is described as built and unwalked.
App journeys
npx antelier journeys init --app https://client-app.example --supabase YOUR_SUPABASE_PROJECT_REF npx antelier journeys suggest # a first journeys file from the app's own screens and routes npx antelier journeys run # journeys, screenshots, receipts, since-the-last-run npx antelier supabase check # row-level security, exposed keys, secrets in the repo npx antelier repair --pr # migration + REPAIR.md, opened as a claim-checked PR
- 1. Bring an app you control.You need its URL and two disposable test accounts that can sign in. Confirm the accounts or disable email confirmation for them.
- 2. Configure access when supported.For a live Supabase audit, supply the owner’s read-scope access token. The setup uses
.antelier/secrets.env, git-ignored by init. - 3. Read, then review the repair.The run writes screenshots, receipts, and a report. The repair command prepares a migration and, with
--pr, opens a PR. It does not apply the migration.
Ask for Journeys setup documentation ↗
Journeys test only configured steps. The current access audit covers supported Supabase surfaces; other backends remain unaudited. Do not read a passing journey as a security certificate.
What the labels mean.
| Label | Meaning |
|---|---|
| present | The described change appears in the diff at the cited hunk. |
| partial | Some of it does; the missing part is named. |
| absent | Nothing in the diff corresponds to the claim. |
| contradicted | The diff does the opposite of what the description says. |
| not checkable | The diff cannot settle behaviour, performance, or intent. Shown, never guessed. |
The free Action runs the deterministic check. The source site describes judged claims, attestation, team rules, and History as hosted-tier features. Ask about the hosted tier ↗