sequant-iosequant-io/sequant/.claude/skills/solve/SKILL.md

solve

Skill1 starsChanged 3 months agoMITView on GitHub

Deprecated: alias for /assess. Generate the recommended workflow for one or more GitHub issues.

7 other projects use a version of this.

Adopted by

Most recently taken up by

DaeSeokSong/oh-my-ouroborostheir own version, first seen Nov 1, 2026
RTGS2017/NagaAgenttheir own version, first seen Oct 8, 2026
Xxiii8322766509/NagaAgenttheir own version, first seen Oct 8, 2026
Z3Prover/z3their own version, first seen Oct 8, 2026
davidsolheim/skillstheir own version, first seen Oct 5, 2026
mdorf/agent-skillstheir own version, first seen Aug 13, 2026

Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
Z3Prover/z3★ 13ksame name
Xxiii8322766509/NagaAgent★ 1.5ksame name
RTGS2017/NagaAgent★ 1.5ksame name
DaeSeokSong/oh-my-ouroboros★ 3same name
corygabrielsen/skills★ 1same name
davidsolheim/skills★ 1same name
mdorf/agent-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- assessSkill
- cleanSkill
- docsSkill
- execSkill
- fullsolveSkill
- improveSkill
- loopSkill
- mergerSkill
- qaSkill
- reflectSkill
- releaseSkill
- security-reviewSkill
- setupSkill
- specSkill
- testgenSkill
- testSkill
- upstreamSkill
- verifySkill

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.

0
Common
Most of the 4 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
This command has been merged into /assess: Use /assess instead.
line 28
Very specific:
When invoked as /solve <issue-numbers>, display this notice:
line 32
Very specific:
When persisting to issue comments, use the new assess: marker format:
line 61
Very specific:
After showing the deprecation notice, the output should follow the /assess output format exactly, including:
line 73

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Local overrides (read this first). Before following any instruction below, check whether .claude/.local/skills/solve/overrides.md exists. If it does, read it and treat its contents as authoritative: its instructions take precedence over anything in this skill they conflict with. This is the supported way to tailor /solve without forking it — overrides.md lives under .claude/.local/, which sequant update and sync never overwrite.

/solve — Deprecated Alias for /assess

This command has been merged into /assess. Use /assess instead.

Deprecation Notice

When invoked as /solve <issue-numbers>, display this notice:

⚠ /solve is deprecated — use /assess instead.
  /assess now includes workflow recommendations alongside health checks.
  Running /assess for you...

Then immediately execute the full /assess workflow for the provided issue numbers, following the assess SKILL.md instructions exactly.

Behavior

/solve is functionally identical to /assess. The only difference is the deprecation notice shown before the assessment output.

/solve 152 → Shows deprecation notice, then runs /assess 152
/solve 152 153 → Shows deprecation notice, then runs /assess 152 153

Migration

# Before (deprecated):
/solve 152

# After (preferred):
/assess 152

Comment Format

When persisting to issue comments, use the new assess: marker format:

<!-- assess:phases=spec,exec,qa -->
<!-- assess:action=PROCEED -->
<!-- assess:quality-loop=true -->

The old solve: markers are still parsed for backward compatibility, but new comments should use assess: markers.

Output Verification

After showing the deprecation notice, the output should follow the /assess output format exactly, including:

Deprecation Notice — Shown before assessment output
Action Headline — → ACTION — reason
Health Checks — Signals that informed the action
Workflow Plan — Full CLI command with flags (for PROCEED)
HTML Markers — Using assess: prefix (not solve:)

Generated by /assess

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free