Vendor user guide + bundled plugins; add /indigo:guide (v2.1.0) - #47
Merged
Conversation
Widen refresh_canonical.py's INCLUDE_PREFIXES to also emit the `user` and `plugins` trees, so general "how does Indigo work" questions (Z-Wave/Insteon/X10 interfaces, control-page/trigger/schedule concepts, reflectors & remote access, Apple Shortcuts, and the bundled plugins) have canonical grounding. Regenerated: 68 -> 127 pages. Existing pages are byte-identical (only INDEX.md and VERSION change); +59 new pages under user/ and plugins/. Standing cost is just a larger INDEX — pages still load individually on demand. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Arj5R66d73tc3PMPvHS65Z
…tions
New thin router over the vendored user guide + bundled-plugin docs, triggering on
Indigo usage/concept/interface questions (Z-Wave associations, reflectors, control
pages, triggers/schedules, Apple Shortcuts, SQL Logger, etc.) that the dev/api
skills don't cover. Routes into reference/canonical/user/ and /plugins/, anchored
to ${CLAUDE_PLUGIN_ROOT}; defers code questions to /indigo:dev and /indigo:api.
Cross-link the most relevant pages from existing skills: api -> web-server +
reflector (where local-secret/port auth actually lives); control-pages -> the
user-facing control-page concept page.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Arj5R66d73tc3PMPvHS65Z
Minor: new /indigo:guide skill + expanded canonical (user guide + bundled plugins). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Arj5R66d73tc3PMPvHS65Z
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (68)
📝 WalkthroughWalkthroughThe plugin version is bumped to 2.1.0, canonical documentation ingestion now includes user and bundled-plugin trees, and extensive Indigo guides, routing references, plugin documentation, interface documentation, remote-access guidance, maintenance pages, and troubleshooting content are added or refreshed. ChangesIndigo documentation release
Estimated code review effort: 3 (Moderate) | ~25 minutes Possibly related PRs
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The vendored canonical only covered the developer surface (
api,plugin-dev,scripting). General "how does Indigo work" questions — Z-Wave associations, reflectors, control-page/trigger/schedule concepts, bundled plugins — had no grounding and no skill to trigger them.What
Extend vendoring (P1) —
refresh_canonical.pyINCLUDE_PREFIXES += ("user", "plugins"). Regenerated 68 → 127 pages; existing pages are byte-identical (onlyINDEX.md/VERSIONchange), +59 new underuser/andplugins/. Standing cost is just a bigger INDEX (~+2k tokens/session) — pages still load individually on demand, so a typical query stays ~10–15k tokens.New
/indigo:guideskill + command (P2) — a thin router over the user guide + bundled-plugin docs, triggering on usage/concept/interface questions (Z-Wave/Insteon/X10, control pages, triggers/schedules/actions/conditions/variables, remote access, Apple Shortcuts, SQL Logger, Email+, NOAA, Timers & Pesters, Alexa…). Anchored to${CLAUDE_PLUGIN_ROOT}; defers code questions to/indigo:devand/indigo:api.Cross-links —
api→user/remote-access/{web-server,reflector}(where local-secret/port auth actually lives);control-pages→ the user-facing control-page concept page.Curation decision
Vendored
user+pluginswholesale rather than hand-excluding end-user "chrome" (mac-client UI, install, license transfer). Reasoning: a tool-side exclusion list would drift as Indigo adds pages — the exact problem this system avoids. Curation happens at the routing layer instead (/indigo:guidefeatures the dev-adjacent pages; chrome sits in INDEX, unfeatured but reachable — e.g. "how do I move Indigo to a new Mac?" is a legit guide answer).Verification
refresh_canonical.py --check(live): all 127 pages match docs.indigodomo.com — no drift.reference/canonical/…path referenced across skills/commands/docs resolves.🤖 Generated with Claude Code
https://claude.ai/code/session_01Arj5R66d73tc3PMPvHS65Z
Summary by CodeRabbit
New Features
Documentation
Chores