new-feature
Skill93 starsChanged 8 days agoMITView on GitHub
Scaffold a new CQRS class (command, query, or service) with spec following project conventions
41 other projects use a version of this.
Adopted by
Most recently taken up by
- NemesLaszlo/claude-code-harnesstheir own version, first seen Nov 8, 2026
- ice-lfernandes/claude-spring-architecttheir own version, first seen Nov 7, 2026
- nerviz-ai/nerviztheir own version, first seen Nov 7, 2026
- michaelshimeles/rstacktheir own version, first seen Nov 1, 2026
- qbicus/skillstheir own version, first seen Oct 25, 2026
- ricci-labs/twisetheir own version, first seen Oct 20, 2026
Used with
Projects with it also use evidence-driven-testing, greploop-apps and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
jaydubya818Skillevidence-driven-testing
Capture observable runtime proof with video, screenshots, or measured output. Use when a change needs evidence beyond test reports.
Also in 6 projects that use this
jaydubya818Skillgreploop-apps
Run greploop through @greptile-apps when the normal trigger rejects a large PR. Use only with the companion greploop skill.
Also in 4 projects that use this
VercelSkillbefore-and-after
Add existing screenshots or screen recordings to a GitHub pull request as a before/after or preview block. Use when a PR needs visual media attached to its description. Browser navigation and capture belong to agent-browser.
Also in 6 projects that use this
BboyfaroukSkillgreploop
Iteratively improves a PR until Greptile gives it a 5/5 confidence score with zero unresolved comments. Triggers Greptile review, fixes all actionable comments, pushes, re-triggers review, and repeats. Use when the user wants to fully optimize a PR against Greptile's code review standards.
Also in 6 projects that use this
u9401066Skillbug-fix
Structured bug fixing workflow with root cause analysis and regression prevention. Triggers: BF, 修 bug, fix bug, debug, 除錯, 錯誤, error, 問題, issue, 修復, fix, 故障, fault, 異常, exception, 失敗, failure, 不能用, broken, 壞掉.
Also in 3 projects that use this
SvampenSkillinit-project
Generates a tailored .claude/project-config.md for the current project. Asks about project type, quality check commands, documentation paths, insight tags, and review strictness.
Also in 4 projects that use this
- +1 more from jaydubya818
Other versions41 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 41
- jhd3197/ServerKit★ 1.8ksame name
- michaelshimeles/rstack★ 1.4ksame name
- michaelshimeles/skills★ 1.4ksame name
- fpindej/netrock★ 234same name
- X-isdoingreat/canvas-pilot★ 123same name
- dan-the-dev/xp-developer-skills★ 31same name
- Fadi88/one-man-startup★ 16same name
- ice-lfernandes/claude-spring-architect★ 11same name
- nerviz-ai/nerviz★ 11same name
- yerdaulet-damir/vibe-coding-rules★ 10same name
31 more not listed
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 repository11 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- add-breadcrumb-pageSkill
- chaosSkill
- cqrs-patternsSkill
- demo-updateSkill
- host-app-safetySkill
- release-rulesSkill
- releaseSkill
- roadmap-statusSkill
- safety-checkSkill
- testSkill
The file
We split this skill into the rules it gives an agent
12 rules. 0 are common, 7 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 39 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Create a new command, query, or service class following the project's CQRS conventions.
- Very specific: line 17
If no arguments provided, ask the user: "What type (command/query/service) and what name?"
- Distinctive: line 33
Follow this pattern (read an existing file from the same directory for reference):
- Distinctive: line 46
Follow this pattern (read an existing spec from the same directory for reference):
- Very specific: line 48
Test self.call factory method
- Distinctive: line 50
Test edge cases (nil input, empty data, errors)
- Very specific: line 57
If the class needs to be autoloaded, check if lib/rails_error_dashboard.rb needs an autoload entry
- Very specific: line 58
If the class adds a dashboard feature, check if config/routes.rb needs a route
- Very specific: line 59
If the class adds a config option, add it to lib/rails_error_dashboard/configuration.rb
- Distinctive: line 63
Always read at least one existing file from the target directory to match:
- Distinctive: line 71
Run the new spec to verify it passes:
- Distinctive: line 75
Run RuboCop on the new files:
“Common” is measured: kept by at least 6 in 10 of the 39 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/new-feature — Scaffold CQRS Class + Spec
Create a new command, query, or service class following the project's CQRS conventions.
Usage
/new-feature command LogSomething— create a command/new-feature query SomeStats— create a query/new-feature service SomeCalculator— create a service
If no arguments provided, ask the user: "What type (command/query/service) and what name?"
Scaffolding Rules
1. Determine the Layer
| Type | Directory | Purpose | Verb Style |
| command | lib/rails_error_dashboard/commands/ | Write operations | Action verb (LogError, ResolveError) |
| query | lib/rails_error_dashboard/queries/ | Read operations | Noun/adjective (ErrorsList, DashboardStats) |
| service | lib/rails_error_dashboard/services/ | Pure algorithms | Algorithm name (ErrorNormalizer, SimilarityCalculator) |
2. Create the Class File
File name: lib/rails_error_dashboard/<type>s/<snake_case_name>.rb
Follow this pattern (read an existing file from the same directory for reference):
- Module:
RailsErrorDashboard::<Type>s::<ClassName> - Factory method:
def self.call(...) - Constructor:
def initialize(...) - Instance method:
def call - Commands: rescue errors, never raise in capture path
- Queries: return data, never mutate
- Services: pure computation, no DB access
3. Create the Spec File
Spec path: spec/<type>s/rails_error_dashboard/<snake_case_name>_spec.rb
Follow this pattern (read an existing spec from the same directory for reference):
RSpec.describe RailsErrorDashboard::<Type>s::<ClassName> do- Test
self.callfactory method - Test main behavior
- Test edge cases (nil input, empty data, errors)
- Commands: test that errors are rescued (never raise)
- Queries: test filters, sorting, empty results
- Services: test computation accuracy, edge cases
4. Register if Needed
- If the class needs to be autoloaded, check if
lib/rails_error_dashboard.rbneeds anautoloadentry - If the class adds a dashboard feature, check if
config/routes.rbneeds a route - If the class adds a config option, add it to
lib/rails_error_dashboard/configuration.rb
Before Creating
Always read at least one existing file from the target directory to match:
- Exact module nesting
- Code style (rails-omakase, array brackets with inner spaces)
- Error handling patterns
- ActiveSupport::Notifications instrumentation (commands)
After Creating
- Run the new spec to verify it passes:
bundle exec rspec spec/<type>s/rails_error_dashboard/<snake_case_name>_spec.rb - Run RuboCop on the new files:
bundle exec rubocop lib/rails_error_dashboard/<type>s/<snake_case_name>.rb spec/<type>s/rails_error_dashboard/<snake_case_name>_spec.rb
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.

