test

Generate comprehensive tests for specified files or recent changes using sr:test-writer.

9|2|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/fjpulidop/specrails-core --skill test-fjpulidop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test
Source: https://github.com/fjpulidop/specrails-core/tree/main/specrails-plugin/skills/test
Command: npx skills add https://github.com/fjpulidop/specrails-core --skill test-fjpulidop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing comprehensive tests for implementation files can be time-consuming and error-prone without tooling or guidance.

Core Features & Use Cases

  • Generate focused tests for specific files or all recently changed files to speed up validation.
  • Align test generation with existing project conventions using sr:test-writer to improve consistency.
  • Use cases include validating new modules, ensuring CI coverage, and quickly auditing changes for regressions.

Quick Start

Run sr:test-writer to generate tests for the target files you specify or for all recently changed files.

Frequently Asked Questions about test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate tests for files changed in the latest commit?

Yes, sr:test-writer can target explicit file paths or glob patterns to generate focused tests. This allows you to validate specific new modules quickly by producing deterministic test artifacts for those files.

Does sr:test-writer enforce existing project test patterns?

Yes, sr:test-writer aligns test generation with existing project-standard test patterns to improve consistency. It ensures the generated tests match your established conventions for validating modules and auditing regressions.

Can I automate test generation for TypeScript implementation files?

You can automate test generation for TypeScript implementation files using sr:test-writer. It speeds up validation by producing comprehensive tests for specified files or recently changed files in your project.

What is the best way to ensure CI coverage for recently changed code?

The best way to ensure CI coverage is running sr:test-writer to automatically generate tests for all recently changed files. This produces review-ready artifacts that help quickly audit changes for regressions.