Verification

Submit a revision for verification

With the cloud connected, run the verifier from your repository. It sends the origin remote and the current commit; the server fetches that commit and runs its configured gates.

node ~/.claude/skills/asondy/scripts/asondy-verify-remote.js

Uncommitted changes are not checked. Commit and push the change first.

What the result identifies

The server returns an unsigned statement naming the repository, the commit and a digest of the checked content. It covers that commit only, not later edits.

Read the outcome

• Pass: every configured check passed on that commit.
• Fail: a check failed; its details name what to fix.
• Error: no result, for example from missing configuration, an unreachable commit or a network failure. Treat it as not passed.

Review the check results

Each result is recorded with its session and can be exported. Match it to the commit, read each check and verify again after a change.

Server verification and SDK submissions

--sdk mode sends a local diff and changed files instead. The server checks what the client sent, so use the default commit mode when the server must fetch the code itself.

What leaves your machine

Commit mode sends the repository name and commit; the server fetches the code. SDK mode sends the code. Job files are removed when the job ends. See What we receive and Privacy.

References

• Signing your work, Pro Git
• About commit signature verification, GitHub Docs