test-engine
Skill26 starsChanged 4 months agoMITView on GitHub
Use when setting up or reviewing dummy-app and engine specs. Trigger words: test engine, dummy app, engine specs.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- korchard333/claude-power-platform-communitytheir own version, first seen Apr 4, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- korchard333/claude-power-platform-community★ 46same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository32 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- apply-code-conventionsSkill
- apply-stack-conventionsSkill
- code-reviewSkill
- create-engine-installerSkill
- create-engineSkill
- document-engineSkill
- extract-engineSkill
- generate-api-collectionSkill
- implement-authorizationSkill
- implement-background-jobSkill
- implement-graphqlSkill
- implement-hotwireSkill
- load-contextSkill
- optimize-performanceSkill
- plan-testsSkill
- rails-featureSkill
- rails-maintenanceSkill
- rails-reviewSkill
- refactor-codeSkill
- release-engineSkill
- review-architectureSkill
- review-engineSkill
- review-migrationSkill
- security-checkSkill
- seed-databaseSkill
- setup-environmentSkill
- test-serviceSkill
- upgrade-engineSkill
- version-apiSkill
- write-testsSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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
- Very specific: line 32
Add the smallest integration test that proves mounting and boot work.
- Distinctive: line 33
Add request, routing, configuration, and generator coverage as needed.
- Distinctive: line 34
Add regression tests for coupling bugs before refactoring.
- Very specific: line 35
Run the full test suite (bundle exec rspec) to verify all specs pass.
- Distinctive: line 113
When completing engine test setup, summarise results as:
≈ “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.
Files
Test Engine
HARD-GATE
EVERY engine MUST have a dummy app for testing.
If it doesn't exist, generate it:
cd my_engine && bundle exec rails plugin new . --dummy-path=spec/dummy --skip-git
Validate the dummy app boots before proceeding:
cd spec/dummy && bundle exec rails runner "puts 'Boot OK'"
If this fails, check the engine's `engine.rb` initializer order and ensure the engine is correctly mounted in `spec/dummy/config/routes.rb` before writing any specs.Core Process
- Identify the engine type and public behaviors.
- Add the smallest integration test that proves mounting and boot work. Verify it passes before continuing — if it fails, check
engine.rbinitializer order and mount configuration. - Add request, routing, configuration, and generator coverage as needed.
- Add regression tests for coupling bugs before refactoring.
- Run the full test suite (
bundle exec rspec) to verify all specs pass.
Minimal request spec to prove the engine mounts:
# spec/requests/my_engine/root_spec.rb
require 'rails_helper'
RSpec.describe 'MyEngine mount', type: :request do
it 'returns ok for the engine root' do
get my_engine.root_path
expect(response).to have_http_status(:ok)
end
endConfiguration spec (engine respects host config):
# spec/my_engine/configuration_spec.rb
RSpec.describe MyEngine::Configuration do
around do |example|
original = MyEngine.config.widget_count
MyEngine.config.widget_count = 3
example.run
MyEngine.config.widget_count = original
end
it 'uses configured value' do
expect(MyEngine.config.widget_count).to eq(3)
end
endAdvanced Coverage Patterns
Namespace-scoped routing spec:
# spec/routing/my_engine/widgets_routing_spec.rb
require 'rails_helper'
RSpec.describe MyEngine::WidgetsController, type: :routing do
routes { MyEngine::Engine.routes }
it 'routes GET /widgets to widgets#index' do
expect(get: '/widgets').to route_to('my_engine/widgets#index')
end
endGenerator idempotency spec:
# spec/generators/my_engine/install_generator_spec.rb
require 'rails_helper'
require 'generators/my_engine/install/install_generator'
RSpec.describe MyEngine::Generators::InstallGenerator, type: :generator do
destination File.expand_path('../tmp', __dir__)
before { prepare_destination }
it 'generates the initializer' do
run_generator
expect(file('config/initializers/my_engine.rb')).to exist
end
it 'is idempotent on re-run' do
run_generator
expect { run_generator }.not_to raise_error
expect(file('config/initializers/my_engine.rb')).to exist
end
endOutput Style
When completing engine test setup, summarise results as:
Engine Test Report — [Engine Name]
- Dummy app: [location], boot ✓, migrations ✓
- Specs: mounting ✓, generators ✓, core (<n> examples, 0 failures)
- Suite: bundle exec rspec — <n> examples, 0 failuresIntegration
| Skill | When to chain |
| create-engine | When structuring the engine for testability or adding configuration seams |
| review-engine | When validating test coverage adequacy or identifying gaps |
| write-tests | When improving spec structure, matchers, or shared examples |
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
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.

