🔍 Claude Code User Documentation Review - 2026-03-30 #23552
Closed
Replies: 1 comment
-
|
This discussion has been marked as outdated by Claude Code User Documentation Review. A newer discussion is available at Discussion #23722. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Executive Summary
gh-aw documentation is well-structured for Claude Code users — Claude is presented as a first-class engine alongside Copilot from the very first step of Quick Start. No critical blockers exist for a developer who uses Claude Code exclusively. The 4 minor issues identified yesterday remain unfixed (day 2 persistent), and today's glossary update (
e4eade4) did not address them.Key Finding: Claude Code users can successfully adopt gh-aw today, with minimal friction. The
add-wizardflow explicitly offers Claude as an engine choice, authentication docs are complete, and 36 example workflows useengine: claude.Persona Context
I reviewed this documentation as a developer who:
Question 1: Onboarding Experience
Can a Claude Code user understand and get started with gh-aw?
Yes, with minimal friction. The Quick Start prerequisites (
docs/src/content/docs/setup/quick-start.mdx:29) explicitly lists:The
add-wizardinteractive flow (quick-start.mdx:67) tells users to "Select an AI Engine - Choose between Copilot, Claude, or Codex." The tool will prompt forANTHROPIC_API_KEYautomatically if Claude is selected.Specific Issues Found:
quick-start.mdx:29— Gemini is listed as a supported engine inengines.mdandauth.mdxbut is missing from the prerequisites list (4 engines exist: Copilot, Claude, Codex, Gemini)engines.md:17— Link to Claude product page uses outdated URLwww.anthropic.com/index/claude(that path no longer resolves correctly)Recommended Fixes:
engines.mdtohttps://www.anthropic.com/claudeQuestion 2: Inaccessible Features for Non-Copilot Users
What features or steps don't work without Copilot?
Features That Require Copilot (clearly documented):
max-continuations— Copilot-only autopilot multi-run feature (engines.mdfeature comparison table)engine.agent— Custom.github/agents/file for customized Copilot system prompts (engines.md:33)COPILOT_GITHUB_TOKEN— Copilot-specific PAT requirementFeatures That Work Without Copilot (engine-agnostic):
edit,github,bash,web-fetch,playwright,cache-memory,repo-memory,qmd,agentic-workflowssafe-outputssystem (create-issue, create-pr, create-comment, etc.)gh aw compile,gh aw run,gh aw logs,gh aw audit,gh aw trialmax-turns(Claude-only, for turn limiting)Missing Documentation:
guides/web-search.md) only shows a Copilot example for MCP-based web search. Since Claude uses the same MCP approach (via MCPin engines feature table), a Claude-specific example would reduce friction.Question 3: Documentation Gaps and Assumptions
Where does the documentation assume Copilot usage?
The docs do not broadly assume Copilot. The main assumption areas are:
Language that could mislead:
how-they-work.mdx:26— "Workflows support GitHub Copilot (default), Claude by Anthropic, and Codex." Leading with "default" is accurate but could cause a Claude user to skim past the engine options.auth.mdx(CLI example) —gh aw secrets set COPILOT_GITHUB_TOKENis shown as the primary CLI example, with Claude/Codex/Gemini shown below. Low risk since section headings are clear.Missing Alternative Instructions:
guides/web-search.md— Full code example only showsengine: copilot. Claude users would need to swap inengine: claudethemselves, which works, but it's not shown.Severity-Categorized Findings
🚫 Critical Blockers (Score: 0)
None. Claude Code users face no absolute blockers.
Obstacle 1: Web Search Guide Has No Claude Example
Impact: Claude users adding web search must mentally translate the only example, which uses
engine: copilotCurrent State:
docs/src/content/docs/guides/web-search.mdshows a single code block:Note: Workflow counts in this repo reflect the gh-aw team's internal usage, not a representative sample. Claude has strong representation (36 files) across diverse use cases: daily reports, security scanning, PR analysis, doc maintenance, schema checking.
Claude Examples Quality: Good. Workflows like
audit-workflows.md,daily-doc-updater.md,claude-code-user-docs-review.mddemonstrate real-world Claude usage patterns across scheduling, safe-outputs, MCP tools, and repo-memory.Recommended Actions
Priority 1: Quick Wins (all 1-line fixes)
[Google Gemini]((aistudio.google.com/redacted) toquick-start.mdx:29— File:docs/src/content/docs/setup/quick-start.mdx`https://www.anthropic.com/index/claudetohttps://www.anthropic.com/claude— File:docs/src/content/docs/reference/engines.md:17(platform.claude.com/redacted) tohttps://console.anthropic.com/settings/keys` — File:docs/src/content/docs/reference/auth.mdx:103Priority 2: Small Content Addition
engine:field — File:docs/src/content/docs/guides/web-search.mdPriority 3: Nice-to-Have
how-they-work.mdxsummarizing which features are engine-specific vs universalPositive Findings
add-wizardwizard flowauth.mdxclearly documents all 4 engine secrets with setup stepsengines.mdhas a clear table showing what's supported per engine (rare in AI tooling docs)gh aw new --engine claude— CLI scaffolding bakes Claude into the frontmatter templategh aw secrets bootstrap --engine claude— Engine-specific secret management CLIANTHROPIC_BASE_URLandanthropic-proxypatterns are documented for enterprise usersConclusion
Can Claude Code Users Successfully Adopt gh-aw?
Answer: Yes
The documentation treats Claude as a first-class engine. The Quick Start wizard, authentication reference, CLI tooling, and engine reference all explicitly support Claude without requiring Copilot. A developer who has never used GitHub Copilot can follow the Quick Start end-to-end and have a Claude-powered agentic workflow running.
The 4 persistent issues are all minor quality improvements, not adoption blockers. The most impactful fix would be updating the
ANTHROPIC_API_KEYsetup URL to point directly at the API key creation page — this reduces friction at the most critical setup moment.Overall Assessment Score: 8/10
Trend vs. 2026-03-29: No change (score stable at 8/10, same 4 issues persist, no new issues found, glossary-only doc change today)
Appendix: Files Reviewed
Complete List of Documentation Files Analyzed
README.mddocs/src/content/docs/setup/quick-start.mdxdocs/src/content/docs/introduction/how-they-work.mdxdocs/src/content/docs/reference/engines.mddocs/src/content/docs/reference/tools.mddocs/src/content/docs/reference/auth.mdxdocs/src/content/docs/setup/cli.mddocs/src/content/docs/guides/web-search.md.github/workflows/audit-workflows.md(Claude example).github/workflows/claude-code-user-docs-review.md(this workflow's own frontmatter)References: §23746552250
Beta Was this translation helpful? Give feedback.
All reactions