agentleFS
Sign inStart free
garthcodesgarthcodes/claude-skills/skills/component-test/SKILL.md

component-test

Skill2 starsChanged 34 days agoMITView on GitHub

Generate or review the RSpec spec for one ViewComponent, given its path. Thin command over viewcomponent-test-expert, which holds the patterns. Use when the user runs /component-test or hands over a single app/components or spec/components file to test.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Write or review the spec for the component at $ARGUMENTS.

    line 9
  2. Very specific:

    Spec present → review mode: Follow the review workflow in test-quality.md.

    line 18

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Component Test

Write or review the spec for the component at $ARGUMENTS.

  1. Read .claude/skills/rspec-test-expert/test-quality.md and .claude/skills/viewcomponent-test-expert/SKILL.md. Together they hold the yardstick, the app's component patterns, and the proof steps.
  2. Resolve the paths: the component .rb, its .html.erb (or inline template, or sidecar directory), and spec/components/<same path>_spec.rb.
  3. Spec missing → write mode. List what the template renders for each input and state, then write one example per state or decision as the expert skill describes. Spec present → review mode. Follow the review workflow in test-quality.md.
  4. Prove it: the spec is green with TEST_ENV_NUMBER=<n>, coverage of .rb and .html.erb shows no lost_lines, and 2–5 probes on the template's conditionals are all KILLED. Lint with bin/standardrb.
  5. Report what changed, lines and examples before→after, coverage, probes, and findings. Never edit the component itself; a suspected bug goes in findings.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free