REVIEW STORY / FIRST USEFUL TASK
Turn a reported concern into a clear next step.
Choose a review task, work through a labelled TLS example, then continue to your own authorized CodHub pull request. Keep evidence, personal decisions and manual repair work distinct.
INTERACTIVE EXAMPLE · NO ACCOUNT REQUIRED
One concern. A reasoned next step.
Try the evidence → personal decision → manual repair sequence with an original neutral sample. The expected result is illustrative; no account review runs here.
Nothing is sent to a provider, saved to an account or charged to an allowance by opening or using this example. Your sample notes stay in this tab’s memory and reset on reload.
01 / INSPECT
Read the sample source
examples/tls-client.ts
One sample file, two added lines. The sample source is never executed.
import https from 'node:https';
export const client = new https.Agent({ rejectUnauthorized: false });02 / DECIDE
Record a sample decision
0/500 · Sample only — not saved to your private notebook.
03 / PREPARE
Plan a manual verification
0/1000
A mark records an intention or a personal report. This example does not run those tests or verify a fix.
Inspect the result, choose a decision, and add a reason and repair plan to finish the example.
Now use your own authorized PR
Continue to the real preparation dialog with your task selected. Sign in with CodHub if needed, choose an accessible repository and synced PR, inspect scope, then explicitly run the available built-in checks. Opening the dialog does not run a review.
Continue with my CodHub PRThe real personal notebook is private account-backed work tied to an exact saved review. Sample notes are not transferred into it.
Choose the input that fits your task
- AntiCode
- Use a connected CodHub pull-request diff, revision evidence and your personal investigation notebook.
- CodLab
- Start with selected JavaScript or TypeScript files, then inspect retained findings, decisions and a manual handoff.
These are alternative starting points. Neither requires the other. Accounts, subscriptions and evidence are not automatically shared or transferred.
What you need for a real review
Use your CodHub account to sign in to AntiCode, authorize repository read access and choose a repository within your existing plan allowance. Sync its pull requests and explicitly select the change you want to inspect.
The real preparation dialog shows the synced head, base and target branch. You can save supported path exclusions and explicitly preview source scope before running built-in checks. That preview retrieves the authorized pull-request diff before applying inspection exclusions. Exclusions limit inspection scope; they do not prevent source retrieval. A preview is separate from a completed review.
Built-in website checks require a complete matching SHA-1 diff and verified provider file, addition and deletion counts. Missing counts, incomplete diffs and unsupported review formats remain explicit blockers. A paid plan or owner role does not activate unavailable tools.
A worked result you can inspect
The original example adds two lines in examples/tls-client.ts. Its HTTPS agent sets rejectUnauthorized to false. The expected supported pattern warning is high severity, points to line 2 and asks you to keep TLS certificate verification enabled.
The corrected control changes that option to true. It has no expected warning from this TLS pattern. Neither the warning nor its absence proves the behavior of a complete application, a successful repair or passing tests.
The example result is predefined and labelled. Inspect the source, record a temporary reasoned decision, and prepare a manual validation plan. Sample completion is an educational action in this tab, not a real review or account activation.
Keep your real investigation with its evidence
Review, Triage, Explain, Secure and Engineer retain the selected authorized pull request, finding and reviewed revision. A changed selection or account does not substitute another finding for you.
For a complete immutable saved finding, your private personal notebook can retain an investigation note, decision, reason, manual repair plan, reported validation and checklist marks. These are your reports, not independently verified defects, fixes or test results. Notebook decisions do not change the separate Triage inbox status or notify other reviewers.
Notebook saves use version checks. A concurrent conflict or uncertain save requires a reload before another write. Undo restores the previous content retained during the current visit using a new version number; the notebook does not offer a browsable version history. JSON and Markdown handoffs include the displayed evidence and saved personal record.
If your workspace has no pull requests
A completed sync that returns zero pull requests remains a real empty state. The sample is a separate learning path and is never inserted into your repositories, saved reviews or personal notebook.
Open Setup to inspect repository access and sync status. In New Review, sync again or include closed and merged requests when appropriate. Missing, partial or failed sync history does not prove that the repository is empty.
If the next step is blocked
If access has expired or was revoked, reconnect the repository connection in Setup with the CodHub identity already linked to this account. Existing owner and customer accounts remain separate; this walkthrough does not link identities or transfer subscriptions or history.
If the source or saved review changed, refresh, inspect the exact head, base and target branch, and explicitly select the finding again. Historical notebook marks remain historical personal reports and cannot establish completion for the new revision.
If notebook storage or a saved report is unavailable, the interface says so. It does not silently fall back to browser persistence or invent a successful save. Inspect any retained draft before reloading.
What this workflow does and does not do
Eligible manual built-in checks inspect a bounded CodHub pull-request diff on the AntiCode server without an AI request. Keep your own tests, dependency analysis, secret scanning and human review in the release process.
General CodHub AI reviews, automatic comments, CI ingestion, generated patches and full repository scans remain unavailable. A separately prepared finite delivery qualification is not ongoing automation and is not activated by this page.
The public example executes no sample source. The real notebook does not edit code, execute tests, approve or merge pull requests. A missing finding in a later saved run remains not recorded, not a verified fix. The installed Mac application has its own release track.