Make rails-docs and tailwind-docs derive version dynamically - #747
Merged
Conversation
Hardcoded version claims (Rails 8.0, Tailwind v3) go stale the moment the project upgrades and nothing flags it. Both skills now instruct Claude to check Gemfile.lock / repo structure at query time instead, so they stay correct across future version bumps without edits.
mattlindsey
marked this pull request as ready for review
July 30, 2026 14:32
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.
Summary
rails-docs,hotwire-docs, andtailwind-docsskills.rails-docsandtailwind-docshardcoded version-specific claims ("this project pins Rails 8.0" / "pins Tailwind v3") that would go stale silently the moment either dependency is bumped, with nothing to flag it.rails-docs: grepsGemfile.lockfor the installedrailsversion and builds the versioned guide/API URLs from that.tailwind-docs: checks forconfig/tailwind.config.js(v3-style JS config) vs@themein the stylesheets (v4-style CSS config) to determine which docs to consult.Test plan