🔍 Claude Code User Documentation Review - 2026-03-31 #23722
Closed
Replies: 1 comment
-
|
This discussion has been marked as outdated by Claude Code User Documentation Review. A newer discussion is available at Discussion #23897. |
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
For the third consecutive day, this review confirms that Claude Code users can successfully adopt gh-aw without critical blockers. The Quick Start guide presents Claude as a first-class AI engine alongside Copilot, authentication documentation is comprehensive, and 35 Claude-engine example workflows exist in the repository. However, four documentation issues identified on day 1 remain unaddressed after three review cycles — the most important being a broken API key setup link and missing Claude/Gemini examples in the web search guide.
Key Finding: No changes since yesterday's review. Overall score holds at 8/10. Four persistent issues need attention before they become accepted as permanent documentation debt.
Persona Context
This documentation was reviewed as a developer who:
Day-Over-Day Comparison
No documentation issues have been fixed across 3 review cycles. The workflow count dropped by 1 for both
claudeandcopilotengines (natural variation; no documentation impact).Question 1: Onboarding Experience
Can a Claude Code user understand and get started with gh-aw?
Yes, with good clarity. The Quick Start guide (
docs/src/content/docs/setup/quick-start.mdx) explicitly lists Claude in prerequisites:The interactive
gh aw add-wizardcommand is described as guiding users to "Select an AI Engine - Choose between Copilot, Claude, or Codex," and Step 3 explicitly documents that users need eitherCOPILOT_GITHUB_TOKEN,ANTHROPIC_API_KEY, orOPENAI_API_KEY. The How It Works page (docs/src/content/docs/introduction/how-they-work.mdx) states:Specific Issues Found:
docs/src/content/docs/setup/quick-start.mdx, Prerequisites section and Step 3. Gemini is a supported engine (withGEMINI_API_KEY) but is absent from the onboarding path. Users who come to the tool specifically to use Gemini would not find setup instructions in the Quick Start.docs/src/content/docs/introduction/how-they-work.mdxsays Copilot is "default." This is technically accurate but can imply preferential support. The engines reference clearly documents all engines as equal citizens.Recommended Fixes:
GEMINI_API_KEYalongside the other three secretsadd-wizarddescription to mention all four enginesQuestion 2: Inaccessible Features for Non-Copilot Users
What features or steps don't work without Copilot?
Features That Require Copilot
max-continuationsdocs/src/content/docs/reference/engines.mdline 30engine.agent(custom agent files)docs/src/content/docs/reference/engines.mdline 33.github/agents/file support; Copilot onlydocs/src/content/docs/reference/auth.mdxline 36These are clearly documented in the Engine Feature Comparison table at
docs/src/content/docs/reference/engines.mdlines 27-36.Features That Work Without Copilot (Engine-Agnostic)
All tools are engine-agnostic unless noted:
tools.edit— file editingtools.github— full GitHub API toolsettools.bash— shell command executiontools.web-fetch— web content fetching (all engines)tools.playwright— browser automationtools.cache-memory/tools.repo-memory— persistent memorytools.agentic-workflows— workflow introspectionmcp-servers:) — all enginesmax-turns— Claude only, but documentedMissing Documentation:
docs/src/content/docs/guides/web-search.md) only shows a Copilot engine example. Claude and Codex both support web search via MCP, but there are no non-Copilot examples provided.Question 3: Documentation Gaps and Assumptions
Where does the documentation assume Copilot usage?
Copilot-Centric Language Found
docs/src/content/docs/introduction/how-they-work.mdx— States "GitHub Copilot (default)" which correctly notes the default but could imply Copilot is the primary/preferred enginedocs/src/content/docs/guides/web-search.mdline 17 — Example workflow hardcoded withengine: copilot, with no Claude/Codex alternatives showndocs/src/content/docs/reference/engines.mdline 21 — "Copilot CLI is the default —engine:can be omitted when using Copilot." This is accurate but could confuse users who want the default to be Claudedocs/src/content/docs/reference/auth.mdxline 48 — The CLI example under "Adding secrets using the CLI" only showsCOPILOT_GITHUB_TOKEN, not a Claude exampleMissing Alternative Instructions:
Severity-Categorized Findings
🚫 Critical Blockers (Score: 0)
None found. A Claude Code user can successfully complete the Quick Start guide and run workflows.
Obstacle 1: ANTHROPIC_API_KEY Setup URL Points to Docs Page (Day 3 - Persistent)
Impact: Friction during onboarding — user lands on a documentation page instead of the API key creation console
Current State:
docs/src/content/docs/reference/auth.mdxline 103:The 1-workflow drop in both claude and copilot counts is likely due to normal codebase evolution (e.g., workflow restructuring or removal). It does not indicate a documentation regression.
Quality of Claude Examples
With 35 Claude workflows covering use cases including: daily reports, code analysis, security review, documentation maintenance, and observability — Claude users have ample real-world examples. Workflow categories using
engine: claudeinclude production workflows used in this very repository (e.g.,claude-code-user-docs-review.md— the workflow generating this report).Recommended Actions
Priority 1: Fix the Anthropic API Key Setup URL (Major Obstacle)
(platform.claude.com/redacted) with the direct API console URL — File:docs/src/content/docs/reference/auth.mdx:103`Priority 2: Add Gemini to Quick Start Onboarding
docs/src/content/docs/setup/quick-start.mdxGEMINI_API_KEYto Step 3 — List all four secrets in the add-wizard step description — File:docs/src/content/docs/setup/quick-start.mdxPriority 3: Nice-to-Have Enhancements
engine: copilottoengine: claudeor add a second snippet — File:docs/src/content/docs/guides/web-search.mdanthropic.com/index/claudewith a current URL — File:docs/src/content/docs/reference/engines.md:17Positive Findings
What works well for Claude Code users:
engines.md) clearly shows what Claude supports vs. what's Copilot-onlyengine: { id: claude, version: "2.1.70" }example providedANTHROPIC_BASE_URLdocumented for proxy/enterprise setupsConclusion
Can Claude Code Users Successfully Adopt gh-aw?
Answer: Yes, with minor friction
The documentation has matured to treat Claude as a genuine first-class engine. A developer who uses Claude Code exclusively can follow the Quick Start guide, select Claude as their engine, set
ANTHROPIC_API_KEY, and have a working automated workflow within the documented ~10 minutes. The engine feature comparison table ensures no surprises about which Copilot-specific features they won't have access to.The four persistent issues are genuine improvement opportunities but none prevent successful adoption. The most impactful fix (Priority 1) is a two-line change to a single file.
Overall Assessment Score: 8/10
Trend: Stable at 8/10 for 3 consecutive days
No documentation regressions. No fixes applied to the persistent issues either. Recommend flagging these four issues for a documentation sprint before they accumulate further.
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/introduction/architecture.mdxdocs/src/content/docs/reference/tools.mddocs/src/content/docs/setup/cli.mddocs/src/content/docs/reference/engines.mddocs/src/content/docs/reference/auth.mdxdocs/src/content/docs/guides/web-search.mdReferences:
Beta Was this translation helpful? Give feedback.
All reactions