fix(cli): Add help recipe for the detect command#61
Merged
Conversation
`detect` is a registered subcommand, so it appeared in the `taskless help` topic index — but `taskless help detect` had no backing `detect.txt` and fell through to "Unknown command", exiting 1. Every other registered command already had a matching help file; `detect` was the lone gap. Add `detect.txt` documenting the `--json` output shape (linters, languages, ruleStyles) and cross-linking to the route/existing authoring flow that consumes those signals. 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 fixes a gap in the CLI help system by adding a missing help topic file for the registered detect subcommand, so taskless help detect no longer falls through to “Unknown command”.
Changes:
- Added
packages/cli/src/help/detect.txthelp recipe documentingdetect --jsonand how it feeds routing/authoring flows. - Added a changeset to release the help topic addition as a patch for
@taskless/cli.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| packages/cli/src/help/detect.txt | New help topic for detect, including JSON shape, routing guidance, and error code table. |
| .changeset/detect-help-topic.md | Patch changeset announcing the new detect help recipe. |
| "evidence": ["eslint.config.js", "dependency eslint (package.json)"] | ||
| } | ||
| ], | ||
| "languages": ["typescript", "javascript"], |
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.
taskless help detecterrored with "Unknown command: detect" (exit 1), even thoughdetectshows up in thetaskless helptopic index.The index is auto-generated from the registered subcommands, but the topic body is served from
packages/cli/src/help/<topic>.txt.detecthad no backing file, so it advertised itself in the index yet failed when asked for. Every other registered command (init,update,info,check,auth,onboard,rule) already had a matching help file —detectwas the lone gap. Reported by the marketing team.Adds
detect.txt, matching the house style of the sibling read-only/offline commandinfo.txt. It documents the real--jsonoutput shape (linters,languages,ruleStyles, verified against live output including the exactevidenceformat) and cross-links to theroute/existingauthoring flow that consumesdetect's signals.detect.txtis plain text embedded viaimport.meta.glob, so there is no type/lint surface. Verifiedtaskless help detectnow renders and exits 0, all 8 registered commands have help coverage, and the full CLI suite passes (363 tests, including thehelp-extensionstopic tests).🤖 Generated with Claude Code