agentsclimarketplace

Triz refactor

Skill christianmerkwirth/triz-skills/skills/triz-refactor

TRIZ (Theory of Inventive Problem Solving) Agent Skills for Software Engineering workflows.

Install
npx -y skills add christianmerkwirth/triz-skills --skill triz-refactor

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

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 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.

What its author says it does

Copied from the file, not written here

Refactors a module by applying a chosen TRIZ principle or auditing for ideality gaps.

SKILL.md

1.3 KB, as published. Nobody here has run it

When to invoke

Invoke this skill to refactor existing code to improve ideality (reduce waste, complexity, harmful effects) or to apply a specific TRIZ principle to resolve a known issue.

Inputs needed

A module path AND either (a) a stated contradiction, or (b) a request to "audit for ideality gaps".

Reference data used

  • reference/principles.md
  • reference/matrix.json (if a contradiction is provided)

Procedure

  1. Receive the module path and the specific contradiction or the request to audit for ideality gaps.
  2. If auditing for ideality gaps, identify areas of waste, unnecessary complexity, or harmful side-effects. If a contradiction was stated, resolve it using reference/matrix.json.
  3. Propose a refactoring plan that cites the specific TRIZ principle to be applied.
  4. Stop. Ask the user to confirm. Do not proceed until they reply.
  5. Apply the edits strictly scoped to the specified module.
  6. Confirm separately before performing any destructive operation. Do not add any new major dependencies.

Output format

A diff summary of the proposed changes, a citation of the applied principle, and a brief rationale explaining how it improves ideality or resolves the contradiction.

Gives 0 of the 12 instructions most refactoring skills give

Counted across 521 of the 525 authors here whose files we hold, read 2026-08-06

  • run tests after each changein 59 of 521, across 56 files
  • write tests before refactoringin 27 of 521, across 24 files
  • preserve external behaviorin 26 of 521, across 22 files
  • remove dead codein 25 of 521, across 24 files
  • make small incremental changesin 20 of 521, across 17 files
  • break the implementation into tiny commitsin 18 of 521, across 5 files
  • ask the user about alternative optionsin 17 of 521, across 4 files
  • create a GitHub issue with the planin 17 of 521, across 4 files
  • explore the repository to verify assertionsin 17 of 521, across 4 files
  • interview the user about the refactorin 16 of 521, across 3 files
  • check the codebase for test coveragein 16 of 521, across 3 files
  • refactor one thing at a timein 16 of 521, across 12 files

Said here and by no other author read

  • receive a module path and contradiction or audit request
  • identify waste, complexity, or harmful side-effects
  • resolve contradictions using the reference matrix
  • propose a refactoring plan citing the TRIZ principle
  • stop and ask the user to confirm
  • apply edits strictly scoped to the module

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 328,083. 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.