You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A lot has shipped over the past two weeks (24 merged PRs since 2026-04-17) but our docs have largely not kept up. Most files under docs/ were last touched around 2026-04-10 to 2026-04-15. This issue is for planning the documentation refresh — auditing what's drifted, deciding the structure, and assigning sections — before opening focused doc PRs.
→ Needs: a single "Automation" doc (or major section) explaining the full lifecycle: assignment → workspace → session → review → PR open → status response → completion. Cross-link from configuration.md and getting-started.md.
→ Needs: cli-reference.md updates for crow rename-terminal (or whatever the verb landed as), troubleshooting entry for Ghostty recovery, and a new section in architecture.md explaining the dual Ghostty/tmux backend and the env flag.
Audit pass — a single PR or commit walking each doc file and flagging concrete drift against this list. (Output: a checklist comment on this issue.)
Automation doc — new docs/automation.md covering the full auto-flow lifecycle and every toggle in Settings → Automation, cross-referenced from README.md and configuration.md.
CLI reference refresh — sweep docs/cli-reference.md against the actual CLI surface (terminal rename, any new flags from the past two weeks).
docs/automation.md exists and is linked from README.md.
docs/cli-reference.md matches actual crow CLI output as of HEAD.
CHANGELOG.md is current through the latest release/tag.
README screenshot reflects current UI.
Out of scope
Writing the docs themselves — that happens in follow-up PRs.
Restructuring the docs site / adding tooling (mkdocs, etc.) — separate concern.
Notes
The dev acceptance and feature-flag-cleanup docs for the tmux backend (#229) probably want to live in the automation doc once the flag flips on by default. For now, document the flag and the opt-in path.
Goal
A lot has shipped over the past two weeks (24 merged PRs since 2026-04-17) but our docs have largely not kept up. Most files under
docs/were last touched around 2026-04-10 to 2026-04-15. This issue is for planning the documentation refresh — auditing what's drifted, deciding the structure, and assigning sections — before opening focused doc PRs.Doc staleness snapshot
README.mddocs/configuration.mddocs/troubleshooting.mddocs/architecture.mddocs/cli-reference.mddocs/getting-started.mdCHANGELOG.mdCLAUDE.mdThemes that shipped and need coverage
1. Automation & auto-modes (largest gap)
crow:autolabelcrow:autoon open→ Needs: a single "Automation" doc (or major section) explaining the full lifecycle: assignment → workspace → session → review → PR open → status response → completion. Cross-link from configuration.md and getting-started.md.
2. Review board & session management
→ Needs: a Review Board doc / section, plus updates to getting-started screenshots and session-management coverage.
3. Terminal runtime & rename
CROW_TMUX_BACKENDfeature flag→ Needs: cli-reference.md updates for
crow rename-terminal(or whatever the verb landed as), troubleshooting entry for Ghostty recovery, and a new section in architecture.md explaining the dual Ghostty/tmux backend and the env flag.4. GitLab path
GITLAB_HOSTmismatch→ Needs: configuration.md note on multi-host GitLab setup; troubleshooting.md note on nested-group repos.
5. Branding / minor
Proposed deliverables
docs/automation.mdcovering the full auto-flow lifecycle and every toggle in Settings → Automation, cross-referenced from README.md and configuration.md.docs/cli-reference.mdagainst the actual CLI surface (terminal rename, any new flags from the past two weeks).CROW_TMUX_BACKENDflag.Acceptance criteria
docs/automation.mdexists and is linked from README.md.docs/cli-reference.mdmatches actualcrowCLI output as of HEAD.Out of scope
Notes
The dev acceptance and feature-flag-cleanup docs for the tmux backend (#229) probably want to live in the automation doc once the flag flips on by default. For now, document the flag and the opt-in path.