zalom
- 5 skills
- 0 followers
- 18 hours ago last updated
- ▌ Ruby Testing · zalom bundleWrites and refactors Ruby and Rails tests in the project's own framework, Minitest or RSpec, with its fixtures or factories and its mocking library. Use when writing, reviewing, or refactoring tests or specs; adding unit, collaboration, or integration tests; checking that a class sends the right message to a mailer, gateway, or job; removing shared state from specs; choosing Minitest or RSpec for a new project; making code testable with injection; fixing flaky, order-dependent, or slow tests; or when a Minitest 5 suite breaks on Minitest 6.
- ▌ Plain Writing · zalom bundleGoverns writing style and communication quality. Use when writing or editing any prose, documentation, README, code comment, commit message, release note, report, summary, or reply to the user. Also fires on indirect requests that never name writing directly, such as "make this readable," "tell me what you found," "clean this up," or "write the announcement." Applies to both authored documents and the agent's own communication with the user.
- ▌ Skill Creating · zalom bundleAuthor or revise an Agent Skill, a subagent or agent role file, or a lifecycle hook with progressive disclosure. Use when creating or editing a SKILL.md, writing its description or frontmatter, designing the slim body, or scaffolding a new skill. Also use when a skill is over budget, prompts are bloated, or an agent keeps missing a step or ignoring instructions.
- ▌ Skill Evaluating · zalom bundleEvaluate skills for correctness, convention compliance, and progressive disclosure. Use when testing whether a skill produces good outputs, verifying convention compliance after changes, running evals against a skill, or checking whether a description triggers correctly. Also use when the user says "evaluate", "run evals", or "check conventions", or when unsure whether a skill is still needed.
- ▌ Ruby Quality Checking · zalom bundleChecks a Ruby or Rails change on the changed code only: lint in the project's style guide, green tests, patch coverage, mutation score, and CRAP scores. Use when checking a branch before a push or pull request; adding coverage, mutation testing, CRAP scores, RuboCop, Standard, or rubocop-rails-omakase to a project; explaining what a CRAP score, mutation score, or patch coverage number means; reading or fixing surviving mutants, uncovered lines, or high CRAP scores; writing the test or spec that kills a named surviving mutant; when someone asks to run the whole test suite to check a small change; or when tests passed but a bug still shipped and someone asks whether the tests can be trusted. For writing or refactoring tests in general, use ruby-testing.