Menü
Fix RSpec test failures systematically, one file at a time.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | fix-rspec |
| description | Fix RSpec test failures systematically, one file at a time. |
Skip discovery and go straight to fixing. Otherwise, run rspec to identify failures.
For each failing spec file:
rspec spec/<path>/<file>_spec.rb:<line_number>
Run only previously failed specs:
rspec --only-failures
If any fail, repeat from step 2.
Only when --only-failures passes, run the full suite:
rspec
If any spec fails, start over from step 2 with the new failures.
Before fixing, determine the root cause:
Signs the test is wrong:
Signs the implementation is wrong:
When uncertain:
Ensure spec/spec_helper.rb has:
RSpec.configure do |config|
config.example_status_persistence_file_path = "spec/examples.txt"
end
This enables --only-failures to work.
End-to-end Jira ticket creation harness. Gathers a summary and rough description, enhances the description in a chosen writing style, confirms with the user, and creates the ticket via the Atlassian MCP. Use when the user says "create a ticket", "open a Jira ticket", "file a bug", "draft a ticket", "new issue for ...", or otherwise asks to create work in Jira. Supports an optional writing style passed up front (e.g. "create a ticket in bug_report style"); when no style is given, the harness asks which style to use.
End-to-end Jira ticket implementation harness. Fetches ticket from Jira, creates an implementation plan, executes it with proper branching, commits, quality gates, and opens a PR. Use when the user says "implement TICKET-ID", "work on TICKET-ID", "pick up TICKET-ID", "start TICKET-ID", or provides a Jira ticket key (e.g., PREFIX-1810, TICKET-450) with implementation intent. Covers bugs, tasks, stories, and any other Jira issue type.
Review a GitHub pull request end-to-end and produce specific, actionable change requests classified as "required" or "good_to_have". Use when the user invokes the /review-pr command with a PR link, says "review this PR", "review pull request", or asks for a code review on a GitHub PR URL. Detects PR ownership via the gh CLI — for the user's own PRs, outputs findings locally; for collaborator PRs, presents findings as approve/reject/change questions and then posts approved feedback as inline review comments at file and line (or as a general PR comment when not line-specific).
Use this skill when writing, reviewing, or refactoring Ruby and Rails code in Develoz's preferred Rails style. Applies to Rails models, controllers, services, jobs, helpers, mailers, views, tests, routing, and architecture. Emphasizes clear Rails conventions, rich domain models, pragmatic service objects, RESTful defaults with practical exceptions, Hotwire, Tailwind, RSpec, FactoryBot, and simple infrastructure choices.
Perform comprehensive code audits of Ruby on Rails applications based on thoughtbot best practices. Use this skill when the user requests a code audit, code review, quality assessment, or analysis of a Rails application. The skill analyzes the entire codebase focusing on testing practices (RSpec), security vulnerabilities, code design (skinny controllers, domain models, PORO with ActiveModel), Rails conventions, database optimization, and Ruby best practices. Outputs a detailed markdown audit report grouped by category (Testing, Security, Models, Controllers, Code Design, Views) with severity levels (Critical, High, Medium, Low) within each category.
Debug and optimize slow ActiveRecord queries in a Ruby on Rails application. Use this skill when the user reports slow pages or jobs, suspects N+1 queries, asks to "optimize", "speed up", "profile", "add indexes", or "explain" an ActiveRecord query, or mentions tools like Bullet, rack-mini-profiler, pghero, pg_stat_statements, EXPLAIN/EXPLAIN ANALYZE, load_async, strict_loading, or query log tags. Also triggers on database-specific performance questions for PostgreSQL, MySQL, or SQLite inside a Rails codebase.