agentsclimarketplace
Sign in

Reconcile tests

Skill TomerAberbach/claude-config/skills/reconcile-tests

Add, update, or delete tests for changes in the current commit.From its SKILL.md

Install
npx -y skills add TomerAberbach/claude-config --skill reconcile-tests

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.7 KB, 393 tokens by cl100k_base, as published. Nobody here has run it

Add, update, or delete tests for changes made in the current jj commit.

Before starting, load /authoring-tests.

Goals

  • Delete no longer applicable tests
  • Update outdated test expectations
  • Add tests for new behaviors

Target

jj show --git

Arguments: $ARGUMENTS

Reconcile tests for the target named in the arguments if given; otherwise the changes in the current commit shown above; if there are no arguments and the commit has no changes, ask the user what to reconcile tests for and stop.

Workflow

  1. Explore each deleted, updated, or added file, and identify:
    • Deleted logic
    • Modified logic (new branches, edge cases, changed behavior)
    • New logic
  2. Find the test files that import or reference the changed code. Create them if missing
  3. Run the relevant tests
  4. Examine failing tests and update them as necessary:
    1. Delete if no longer applicable
    2. Update if expectations are outdated
    3. Flag regressions to the user. Describe the changed behavior, the failing test, and your hypothesis about why it's a bug. Ask how to proceed Go back to step 3 after making updates until all tests pass
  5. Add tests for new behaviors
  6. Run the new tests
  7. Examine failing tests and update them as necessary:
    1. Update if there's a bug in the test
    2. Flag to the user if the tests caught a bug, Describe the behavior, the failing test, and your hypothesis about why it's a bug. Ask how to proceed Go back to step 7 after making updates
  8. Run tests with coverage if possible. If new logic is not covered, then go back to step 5

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,758. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.