skills.rest
paulnsorensen
paulnsorensenCOMMUNITY
Explore all skills by this author →
GitHub

press

Map cooked diffs to test coverage and add regression tests.

15|1|Updated May 4, 2026
Search Tags:#agent skills#gap analysis#regression testing#boundary testing#assertion strength#code review readiness#test hardening
One-click install
npx skills add https://github.com/paulnsorensen/easy-cheese --skill press
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: press
Source: https://github.com/paulnsorensen/easy-cheese/tree/main/skills/press
Command: npx skills add https://github.com/paulnsorensen/easy-cheese --skill press

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill strengthens the test surface after implementation changes, so weak or missing assertions are caught before review or shipping.

Core Features & Use Cases

  • Changed-behavior mapping: For each cooked change, it finds the tests that cover the touched behavior and verifies they truly exercise the new expectations.
  • Gap analysis and hardening: It identifies spec gaps, weak assertions, missing boundaries, and integration seams, then adds focused hardening tests and corrective fixes only when tests expose a defect.
  • Review readiness reporting: It writes a structured press report to .cheese/press/<slug>.md and determines whether you are ready for /age, should follow up, or must stop due to blockers.

Quick Start

Use the press skill after you have completed /cook for the same slug and ask it to press the changes before /age.

Frequently Asked Questions about press

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

FAQPage Schema
How do I strengthen weak assertions and close test coverage gaps after implementing code changes?▼

Test hardening closes coverage gaps by mapping a cooked diff to existing tests, strengthening weak assertions, and adding focused regression tests to validate integration seams before code review.

What is regression testing gap analysis and when do I need it for boundary testing?▼

Regression testing gap analysis identifies missing boundaries and integration seams within a cooked scope. You need it after successful implementation to verify touched behavior and enforce review readiness gating.

How do I generate an auditable report for code review readiness after cooking changes?▼

Generate an auditable press report artifact by reading the spec or acceptance criteria plus the cooked diff. The report determines whether you are ready for review, need follow-up, or must stop due to blockers.

Can I apply test hardening automatically before the aging process?▼

Yes, test hardening applies after successful cooking and before aging, enforcing readiness gating with --auto handoff rules to ensure all assertion strength and boundary testing requirements are met.

When should I not use automated gap analysis for missing boundaries?▼

Avoid automated gap analysis when no spec or acceptance criteria exist, as the hardening process requires reading these to map changed behavior and produce the structured readiness report accurately.

Related Skills

Explore More Software Engineering Skills→
JiggerFJiggerF

pr-impact-test

Map PR diff files to affected test suites and run targeted vitest commands.

Community
Advanced
paulnsorensenpaulnsorensen
15

cure

Apply code edits for selected age report findings and validate through tests.

Community
Advanced
dhruvinrsonidhruvinrsoni

mutation-testing

Inject faults into code and execute tests to identify surviving mutants.

Community
Advanced
tranceetrancee

swift-testing-reviewer

Audit Swift Testing code for weak assertions and missing edge cases.

Community
Intermediate