feat(skill): Engage routing when a linter is named#27
Open
thecodedrift wants to merge 5 commits into
Open
Conversation
Reverse the named-tool suppression: naming a linter (eslint, ruff, biome, ast-grep) now ENGAGES the skill's routing flow via `taskless help route` instead of quieting it. Replace the "Quiet suggestion" section with a route-through-route body that forbids fetching `rule create` directly and adds no linter knowledge, and relax the install gate so the `existing` path (which only reads the repo) is not blocked when `.taskless/` is absent. Description measures 835/1024 chars. Skill version is build-locked to the package version, so a minor changeset drives the bump rather than a hand-edited mismatch. 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 updates the consolidated taskless agent skill to treat “named linter” rule-authoring requests as an explicit entry into Taskless’s new local-first routing flow (route → existing/static/remote), removing the previous suppression/quiet-offer behavior.
Changes:
- Update
skills/taskless/SKILL.mdtrigger + body so rule-authoring always starts atnpx @taskless/cli help route, even when a specific linter is named; remove the “Quiet suggestion” suppression path. - Relax the install gate so
route/existing(repo-reading paths) are not blocked by the absence of.taskless/, while still offering install when routing lands onstatic/remote. - Add a changeset intended to drive a minor version bump for this behavior change.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| skills/taskless/SKILL.md | Switch rule-authoring posture to always route via help route (including named linters) and remove suppression path. |
| openspec/changes/local-rule-routing/tasks.md | Mark the skill-posture tasks complete and note the intended release/versioning approach. |
| .changeset/local-rule-routing.md | Add a minor changeset describing the local-first routing layer and updated skill behavior. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
* feat/local-rule-help: 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
PR #27 review: - The changeset targeted the private, unpublished root `@taskless/skills` package, which produces no release and is overwritten by sync-skill-versions. Target `@taskless/cli` — the published package and the version source of truth that skill metadata.version is locked to. - Add `stylelint` to the skill body's example tool list so it matches the description's list. - Update the tasks.md 4.3 note to describe the real release mechanism (@taskless/cli version drives the skill version via sync-skill-versions). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
* feat/local-rule-help: docs(cli): Address review on routing recipes fix(cli): Harden detect against malformed manifests and false positives
* feat/local-rule-help: 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.
Flip the skill's posture toward the routing layer. Previously, naming a linter (eslint, ruff, biome, ast-grep) suppressed the skill to a one-line offer. Now it ENGAGES the routing flow via
taskless help route, because Taskless can help author the rule in that tool's own dialect.Changes to
skills/taskless/SKILL.md:taskless help route(the body forbids fetchingrule createdirectly and adds no linter knowledge — the skill stays a thin router).existingpath (which only reads the repo) isn't blocked when.taskless/is absent;static/remotestill offer install.The skill
metadata.versionis build-locked equal to the package version (enforced byassertSkillVersions), so this ships aminorchangeset to drive the bump in lockstep rather than hand-editing a mismatch.Stacked on #26. The validation/eval/smoke pass lands last.
Refs TSKL Runtime Rules
Stack generated by Git Town