Skip to content

Troubleshooting home for /dex-doctor + /feedback, and Doctor's onboarding moment - #432

Open
davekilleen wants to merge 1 commit into
mainfrom
feat/feedback-awareness-remainder
Open

Troubleshooting home for /dex-doctor + /feedback, and Doctor's onboarding moment#432
davekilleen wants to merge 1 commit into
mainfrom
feat/feedback-awareness-remainder

Conversation

@davekilleen

Copy link
Copy Markdown
Owner

Scope

Completes the remaining scope of Build Card feedback-loop-launch-awareness (workstream 4 + the Doctor-in-onboarding verification). PR #431 already delivered the onboarding introduction of /feedback and post-update what's-new announcements; the v1.82.0 changelog entry is the release copy. This PR does not touch any of that machinery.

1. Troubleshooting surfaces

  • 06-Resources/Dex_System/Dex_System_Guide.md — canonical passage. The existing "Vault Health (/dex-doctor)" section gains a "Troubleshooting: When Something Seems Broken" subsection: Doctor is the first stop (fixes what's safe, guides the rest); if it's a genuine Dex bug, /feedback reports it with zero homework — Dex investigates on your machine, you approve exactly what's sent, nothing from notes/meetings/conversations ever leaves, and you hear back when the fix ships.
  • README.md — short pointer at the end of the "Troubleshooting: Common Setup Issues" block, covering the "something broke after setup" case.
  • 06-Resources/Dex_System/Dex_Technical_Guide.md — one-paragraph pointer in the Testing Doctor section (repeat-BROKEN → /feedback, with a reference to the System Guide passage).
  • .claude/skills/dex-doctor/SKILL.md/feedback added to Related Commands (the skill body already invokes it in two places).
  • docs/Dex_System/ copies of both guides kept byte-identical to their 06-Resources sources, matching how past commits handle the pair.

2. Doctor's onboarding moment

Verified PR #431's changes: .claude/flows/onboarding.md introduced /feedback in the completion message and .claude/skills/getting-started/SKILL.md added a /feedback discovery bullet — but neither mentioned /dex-doctor (the flow's only prior Doctor reference was a calendar-skip aside). Added light-touch mentions:

  • Onboarding completion: the "if anything ever feels broken" beat now leads with /dex-doctor as the anytime checkup, then hands off to the existing /feedback copy unchanged.
  • Getting-started completion: one /dex-doctor bullet alongside the existing /feedback bullet.

Verified

  • bash scripts/check-founder-content.sh — pass
  • python3 scripts/check-instructed-tools.py — pass (163 defined tools, 114 instruction files)
  • .venv/bin/python -m pytest core/tests/test_skill_integrity.py -q — 118 passed
  • No core/*.py or hook changes, so check-doc-drift is unaffected
  • All new user-facing copy checked against the CFO test (no jargon)
  • No CHANGELOG entry: guide/onboarding copy only, no behavior change — the v1.82.0 entry already announces /feedback itself

🤖 Generated with Claude Code

…tor's onboarding moment

Remaining scope of the feedback-loop-launch-awareness card (PR #431 covered
onboarding /feedback intro and post-update announcements):

- Canonical troubleshooting passage in Dex_System_Guide.md (Vault Health
  section): /dex-doctor as first stop when something seems broken, /feedback
  when it's a genuine Dex bug — with the privacy promise spelled out.
- Brief pointers: README setup-troubleshooting block, Dex_Technical_Guide's
  Testing Doctor section, and dex-doctor SKILL.md Related Commands.
- Doctor's onboarding moment: the completion message's 'if anything ever
  feels broken' beat now introduces /dex-doctor before /feedback, and the
  getting-started completion list gains a /dex-doctor bullet.
- docs/Dex_System copies kept byte-identical to 06-Resources sources.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Aug 8, 2026

Copy link
Copy Markdown

What this pull request touches

  • skills — feeds the guided workflows and commands people use with Dex.

Gates that will judge this change

  • Personal-data gate: added lines must not expose real identities or personal vault content.
  • Change-aware gates: source changes are checked for tests, path-contract use, documentation drift, and touched-file coverage.
  • Tests and coverage: the Python, MCP, migration, hook, and script suites must remain healthy.
  • Safety and quality: security, lint, distribution, path consistency, and large-vault checks still apply.

Based on 8 changed files.

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