feat(cli): Surface routing recipes in the help index#26
Open
thecodedrift wants to merge 4 commits into
Open
Conversation
List route/existing/static/remote under an "Authoring recipes" section of the `taskless help` no-arg index so an agent can discover the rule-authoring front door. The existing help command already emits help_<topic> intent telemetry generically, so the routing topics inherit it. Add integration tests for index listing and topic resolution, plus an in-process test asserting help_route/existing/static/remote capture. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR makes the new routing authoring recipes discoverable from the taskless help no-args index by adding an “Authoring recipes” section, and adds automated coverage to ensure both topic resolution and intent telemetry work for the routing topics.
Changes:
- Add an “Authoring recipes” section to
taskless help(no args) listingroute,existing,static, andremote. - Add integration tests asserting the index lists the routing topics and
taskless help <topic>resolves each recipe. - Add an in-process test that mocks telemetry and asserts
help_<topic>capture for each routing topic.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| packages/cli/test/help-routing-telemetry.test.ts | Adds a unit-style telemetry capture test for help_route / help_existing / help_static / help_remote. |
| packages/cli/test/help-extensions.test.ts | Extends CLI integration tests to validate index discoverability and recipe resolution for routing topics. |
| packages/cli/src/commands/help.ts | Adds a recipe-topic index section and aligns table padding across command topics + recipe topics. |
| openspec/changes/local-rule-routing/tasks.md | Marks the “Help registration + telemetry” checklist items as completed. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
* feat/local-rule-recipes: docs(cli): Align route recipe with the three-state contract docs(cli): Show detect output shape in the route recipe docs(openspec): Clarify detect output schema is internal, not published docs(openspec): Address review feedback on local-rule-routing contract
* feat/local-rule-recipes: docs(cli): Address review on routing recipes fix(cli): Harden detect against malformed manifests and false positives
This was referenced Jun 12, 2026
* feat/local-rule-recipes: ci(openspec): Skip the archive check on non-tip stacked PRs (#31) docs(openspec): Clarify detect output schema is internal, not published docs(openspec): Address review feedback on local-rule-routing contract docs(openspec): Propose local-rule-routing change chore(skill): Refine the stacked-PR archive-check guidance chore(skill): Scope iterate-pr archive check to the stack tip chore(config): Allow git-town in project settings
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.
Make the routing recipes discoverable. The
taskless helpno-arg index previously listed only real subcommands; this adds an "Authoring recipes" section listingroute/existing/static/remoteso an agent landing on the index can find the rule-authoring front door.Intent telemetry needs no new code: the help command already emits
help_<topic>for any resolved topic, so the routing topics inherit it. Tests cover all three surfaces:taskless help <topic>(no unknown-topic error), and the index lists all four;help_route/help_existing/help_static/help_remoteare captured when each topic is fetched (telemetry module mocked, mirroring the existing posthog mock pattern).Stacked on #25. Skill posture change (engaging routing on a named linter) lands next.
Refs TSKL Runtime Rules
Stack generated by Git Town