fullsolve

An automated workflow for resolving a numbered GitHub issue from its specification through implementation and checks. It moves through planning, coding, testing, and quality review without waiting between stages.

In plain words
What is it for?
Use it when you want an issue carried through from agreed requirements to a reviewed change. It is intended for complete issue resolution, including tests or other quality checks when applicable.
Why use it?
It reduces the need to coordinate each development stage manually and repeats fixes when quality checks find problems.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/sequant-io/sequant/fullsolve
Any agent
npx skills add sequant-io/sequant --skill fullsolve
Clone the repo
git clone --depth 1 https://github.com/sequant-io/sequant

Made for: Claude Code, Codex.

Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 10,497 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00023 $0.10497
Opus 5 $0.00012 $0.05248
Sonnet 5 $0.00005 $0.02099
Haiku 4.5 $0.00002 $0.01050

Measured yesterday against content hash 5dba6cd9f192, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

fullsolve scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/fullsolve/SKILL.md · 1,114 lines

How it starts

The opening of the file, as written. The whole thing — 1,114 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Local overrides (read this first). Before following any instruction below, check whether .claude/.local/skills/fullsolve/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 /fullsolve without forking it — overrides.md lives under .claude/.local/, which sequant update and sync never overwrite.

Full Solve Command

You are the "Full Solve Agent" for the current repository.

Purpose

When invoked as /fullsolve <issue-number>, execute the complete issue resolution workflow with integrated quality loops. This command orchestrates all phases and automatically iterates until quality gates pass.

CRITICAL: Auto-Progression Between Phases

DO NOT wait for user confirmation between phases. This is an autonomous workflow — through PR creation.

After each phase completes successfully, immediately proceed to the next phase:

  1. /spec completes → immediately invoke /exec
  2. /exec completes → immediately invoke /test (if UI) or /qa
  3. /test completes → immediately invoke /qa
  4. /qa completes → immediately create the PR and post the final summary

The workflow's terminal state is PR created + final summary posted — not merged. Merging (§5.3), post-merge verification (§5.4), and the auto-merge-path lock release (§5.5) run only when --auto-merge is passed, run.autoMerge is true in .sequant/settings.json, or the user has explicitly instructed a merge in this conversation (invoking /fullsolve alone does not count). Without one of those, /fullsolve stops after the final summary — the PR is left open for human review. See "Merge Gate" below for how this is resolved, and §5.3 for the gate itself.

The user invoked /fullsolve expecting end-to-end automation up to a mergeable PR. Only stop for:

  • Unrecoverable errors (after retry attempts exhausted)
  • Final summary after PR creation — this is the workflow's terminal state, not a pause
  • Explicit user interruption

Read the full file on GitHub · 1,114 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 1,114 lines · 23 tokens per session scan A 5dba6cd9f192

Subscribe to this mod's changes

fullsolve is a skill published in the GitHub repository sequant-io/sequant (1 stars, last pushed yesterday), licensed MIT. It adds 23 tokens to every session and 10,497 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

agent-estate

Perpetual autonomous work loop for Claude Code — no end condition, no memory regression, no context overfill. Maintains a persistent ledger across all sessions.

MercuriusDream/agent-estate · 36 tokens

citation-audit

Zero-context verification that every bibliographic entry in the paper is real, correctly attributed, and used in a context the cited paper actually supports — catching hallucinated authors, wrong years, fabricated venues, version mismatches, and wrong-context citations. Use when user says "审查引用", "check citations"…

wanshuiyin/Auto-claude-code-research-in-sleep · 86 tokens

paper-illustration

Generate publication-quality AI illustrations for academic papers using Gemini image generation. Creates architecture diagrams, method illustrations with Claude-supervised iterative refinement loop. Use when user says "生成图表", "画架构图", "AI绘图", "paper illustration", "generate diagram", or needs visual figures for papers.

wanshuiyin/Auto-claude-code-research-in-sleep · 67 tokens

paper-illustration-image2

Generate publication-quality academic illustrations through a local Codex app-server bridge that uses Codex native image generation. This is a separate experimental alternative to paper-illustration, intended for Claude Code users who want a GPT-image-style renderer without modifying the original skill.

wanshuiyin/Auto-claude-code-research-in-sleep · 59 tokens

experiment-plan

Turn a refined research proposal or method idea into a detailed, claim-driven experiment roadmap. Use after research-refine, or when the user asks for a detailed experiment plan, ablation matrix, evaluation protocol, run order, compute budget, or paper-ready validation that supports the core problem, novelty…

wanshuiyin/Auto-claude-code-research-in-sleep · 80 tokens

paper-writing

Workflow 3: Full paper writing pipeline that goes from a narrative report to a polished, submission-ready PDF. Use when user says "写论文全流程", "write paper pipeline", "从报告到PDF", "paper writing", or wants the complete paper generation workflow.

wanshuiyin/Auto-claude-code-research-in-sleep · 58 tokens