Skip to content

docs: add a Claude Code QA walkthrough - #1233

Closed
EivMeyer wants to merge 1 commit into
mainfrom
docs/claude-code-qa-agent
Closed

EivMeyer wants to merge 1 commit into
mainfrom
docs/claude-code-qa-agent

Conversation

@EivMeyer

Copy link
Copy Markdown
Collaborator

Summary

Add a practical Claude Code QA guide that takes an HTTP service through implementation, independent acceptance and code review, and bounded repair. It reuses the existing review-loop graph, adds downloadable Claude runtime and task inputs, and appears in the Guides navigation.

Validation

  • Example accepted by zeroshot 10.10.1 with --validate-only.
  • Strict MkDocs build and all 16 documentation tests passed; rendered page inspected in the browser.
  • Tracked pre-commit checks passed, including Rust formatting, repository lint, and tooling tests.
  • Opcore pre-commit accepted; dependency analysis reports no introduced findings with partial repository coverage.
  • Recipient, Truth, Editor, and Voice reviews passed.

No model run was started. Validation checks the graph and inputs, not application startup, model availability, or an observed acceptance result.

@EivMeyer EivMeyer closed this Oct 11, 2026
@greptile-apps

greptile-apps Bot commented Oct 11, 2026 •

Copy link
Copy Markdown

RetriggerConfidence Score: 4/5

[Low impact] Adds documentation and example files for a QA workflow.

The PR appears safe to merge, with a non-blocking correction to the repository prerequisites.

Findings

  1. P2 GitHub prerequisite is missing ▶

Summary

Adds a Claude Code QA walkthrough using the existing review loop.

  • The guide shows how Claude Code checks and repairs an HTTP change.

Review checks were read-only. No model run, build, or browser check was performed.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  W[Worker implements or repairs] --> R[Acceptance and code reviews run in parallel]
  R --> A{Both accept this pass?}
  A -->|Yes| S[Run succeeds]
  A -->|No| B{Four passes used?}
  B -->|No: return both reviews| W
  B -->|Yes| F[Run fails; changes remain in worktree]
Loading

Reviews (1) · Last reviewed commit: "docs: add a Claude Code QA walkthrough" · Reviewed by Greptile

Comment on lines +18 to +19
You need [zeroshot installed](../getting-started/install.md), Claude Code installed and signed in,
and a Git repository containing an HTTP service with documented setup, start, and test commands.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 GitHub prerequisite is missing

The prerequisites allow any Git repository, but a local run requires remote.origin.url to point to a repository on github.com, even without Git delivery. If a reader uses a local-only repository or a GitLab origin, --validate-only can pass, but the actual run fails before any agent starts. Add the GitHub origin requirement and a check for it under “Prepare the repository.”

Suggested change
You need [zeroshot installed](../getting-started/install.md), Claude Code installed and signed in,
and a Git repository containing an HTTP service with documented setup, start, and test commands.
You need [zeroshot installed](../getting-started/install.md), Claude Code installed and signed in,
and a Git repository containing an HTTP service with documented setup, start, and test commands.
The repository's `remote.origin.url` must point to a repository on `github.com`, even for local runs
without Git delivery. Check it with `git remote get-url origin` before continuing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant