CtrlK
BlogDocsLog inGet started
Tessl Logo

igmarin/ruby-core-skills

Curated library of 16 public Ruby AI agent skills covering TDD, refactoring, code review, security review, DDD, YARD documentation, and common design patterns.

94

1.13x
Quality

96%

Does it follow best practices?

Impact

94%

1.13x

Average score across 16 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

BOUNDARY_GUIDE.mdskills/testing/triage-bug/

Bug Triage Boundary Guide

Maps common bug shapes to the highest-value first failing test.

Bug shapeLikely first testPath example
Wrong status code, params handling, response payloadRequest or integration testspec/requests/ or test/integration/
Invalid state transition, validation, calculationUnit or service testspec/models/ or test/unit/
Async side effect missing or duplicatedWorker/job or unit testspec/workers/ or test/jobs/
Component integration/configuration regressionIntegration testComponent test suite path
Third-party mapping/parsing issueIntegration or client-layer testspec/services/module_name/

Diagnosing the Right Layer

  • HTTP/API symptoms (wrong status, wrong payload shape, redirect loops): start at request or integration level
  • Data symptoms (wrong value saved, wrong validation message): start at unit or service class level
  • Timing/Async symptoms (missing notification, job not enqueued): start at background worker or unit service level
  • Integration/Component symptoms (module loading errors, route not found): use integration test or dummy app integration test

When the Boundary Is Unclear

  1. Write the test at the highest visible symptom boundary first.
  2. Run it — if it fails for the wrong reason (e.g., test setup error), move down a layer.
  3. The correct boundary is where the failure message directly names the missing behavior.

skills

testing

triage-bug

BOUNDARY_GUIDE.md

SKILL.md

README.md

tile.json