chore(#84): add cd apexyard to quickstart step 02#85
Conversation
Makes step 02 self-contained - reader knows explicitly which directory to run `claude` from, rather than implicitly relying on having stayed in the directory created by step 01. Closes #84 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
atlas-apex
left a comment
There was a problem hiding this comment.
Code Review: PR #85
Commit: 5402b153d4b5f7fcdb965c7fd5f6635010ff1de7
Summary
One-line content fix in site/index.html — adds cd apexyard as the first line of the quickstart step 02 code block so the reader knows explicitly which directory to run claude from, rather than implicitly relying on state left by step 01. Closes #84.
Checklist Results
- Architecture & Design: N/A (static HTML content)
- Code Quality: Pass (minimal, correct diff)
- Testing: N/A (content-only; CI lint + lychee green)
- Security: Pass (no executable code, no user input, no data flow)
- Performance: Pass (one extra line of text)
- PR Description & Glossary: Pass (summary, diff, testing steps,
Closes #84, glossary present) - Technical Decisions (AgDR):N/A (documentation tweak, no library / architecture / pattern choice)
Verification
- Diff is exactly +2/-1 on
site/index.htmlas advertised. - Added line
cd apexyardappears exactly once in the step 02<pre class="step__code">…</pre>block (now line 1347). - Tag balance preserved:
<pre class="step__code">opens on 1347,</pre>closes on 1350;<span class="acc">and<span class="cm">each open and close on the same line. - No other content altered; surrounding anchors and steps untouched.
- The prior
cd apexyardat line 1338 is the existing step-01 fork-and-cd block — unrelated, unchanged. - CI checks green (Verify Ticket ID: pass, lychee: pass).
- PR title
chore(#84): add \cd apexyard` to quickstart step 02matches the convention; branchchore/GH-84-cd-apexyard-step-02` has the ticket ID.
Issues Found
None.
Suggestions
None. Change is the minimum necessary to make the step self-contained, which is exactly what the PR description promises.
Note on design review
This is a user-visible UI change (a line of text in a code block on the landing page), so in the strict sense the "UI change → design review" rule applies. In practice this is instructional content inside an existing <pre>, not a visual / layout / component change. Flagging it so the CEO can decide whether a design marker is wanted before merge; not treating it as a blocker.
Verdict
APPROVED (posted as comment — GitHub blocks self-approval; reviewer is the PR author)
Reviewed by Rex (Code Reviewer Agent)
Reviewed commit: 5402b153d4b5f7fcdb965c7fd5f6635010ff1de7
Makes step 02 self-contained - reader knows explicitly which directory to run `claude` from, rather than implicitly relying on having stayed in the directory created by step 01. Closes me2resh#84 Co-authored-by: me2resh <ahmed.abdelaliem@gmail.com> Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Makes step 02 self-contained - reader knows explicitly which directory to run `claude` from, rather than implicitly relying on having stayed in the directory created by step 01. Closes me2resh#84 Co-authored-by: me2resh <ahmed.abdelaliem@gmail.com> Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Summary
One-line content fix in
site/index.html. Step 02 in the quickstart ("claude, /setup") now starts withcd apexyardso the reader knows explicitly which directory to runclaudefrom, rather than implicitly relying on having stayed in the directory created by step 01.Diff
Step 02 code block — was:
Now:
Testing
site/index.html— quickstart step 02 shows the new first line.Closes #84
Glossary