Add Rubydex skill library with CLI command - #982
Open
dersam wants to merge 4 commits into
Open
Conversation
Every failure to produce a `Skill` now raises `SkillError`: `load` wraps the errors `File.read` raises, and the frontmatter parse wraps Psych's, so the CLI reports a bad skill file instead of a backtrace. `SkillRegistry#fetch` raises `SkillError` naming the available ids rather than `KeyError`, which removes the `key?` guard at the call site, and it rejects a skill whose frontmatter `name` disagrees with its directory so the id has one spelling. `rdx skill` rejects a trailing argument like `rdx mcp` does, reports an empty library, and wraps long descriptions under the first line through `CLI.describe`, which is now public for that. The skill files are required by the CLI command instead of `lib/rubydex.rb`, so a gem consumer no longer loads psych for a command it may never run. The `send-private-method` skill claimed a bare `private` makes `def self.bar` private and that moving the definition promotes it; both are false, and an agent following them would flag a public method and then "fix" it with a no-op. The examples now run, and the trigger no longer implies a detector Rubydex does not have. Documents the library in README.md and AGENTS.md.
`SkillRegistry#fetch` raised a message that spelled out the available ids, which made the registry answer a question only an interface can answer. It now raises `UnknownSkillError` naming just the id, and `rdx skill` builds the "Available skills" line from `SkillRegistry#ids` when it renders the failure — the same line it prints for an empty library. A second interface picks its own wording from the same data.
dersam
marked this pull request as ready for review
August 5, 2026 20:37
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
1 participant
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.
Summary
Adds a skill system that lets the
rdxCLI load and display skill files — Markdown documents with YAML frontmatter that encode remediation guidance for linter rules.This is the first part of a system that will allow Rubydex tools to provide references to detailed skills for fixing issues, without having to load every skill. The linter finding is the trigger point for skill loading, rather than relying on the agent pulling from context.
Skill files live at
skills/<id>/SKILL.mdand use YAML frontmatter to declare anameanddescription. This is the standard agent skill format.rdx skill— lists available skills with id and description, aligned in columnsrdx skill <id>— loads and prints the skill bodyrdx skill <unknown id>— reportsunknown skill: <id>on stderr, exits non-zeroThe skills directory is resolved relative to the source file (
__dir__), so it works both in development and when installed as a gem. Skills are also added to the gemspec file list.The diagram below illustrates the intended use of skill ids in a Rubydex tooling loop.