Project credentials
- MIT Licensed
- Open Source
- TypeScript
What is Sequant
How It WorksWorkflow automation for Claude Code. Sequant turns GitHub issues into merge-ready pull requests through structured phases and quality gates.
Claude Code is remarkably capable. But capability without process means results may vary — vague issues produce vague implementations, there's no formal review, and context drifts over long sessions. Sequant provides the discipline: a repeatable pipeline where every issue follows the same lifecycle.
Each phase runs in a fresh session inside an isolated worktree. No context drift — code never touches main until gates pass.
Security, types, scope, tests, build regression, and anti-patterns — checked automatically on every PR.
Batch issues, chain dependencies, and resume failed runs. Process your backlog overnight with cost-efficient sub-agents.
What runs underneath
18 slash commands that tell Claude Code what to do in each phase
Pre-tool blocks secrets and unsafe commands. Post-tool formats and observes quality.
Tracks phase progress, metrics, and run logs — updated at every phase boundary
Plans, verdicts, and phase markers that carry context between sessions
A Smarter Way to Code
2 Ways to Solve IssuesPoint it at an issue. Walk away. Come back to a finished PR — spec'd, built, tested, and QA'd.
Stay in the loop. Run each phase — /spec, /exec, /test, /qa — with full control.
Skills
CommandsRun any skill by name in conversation, as a /slash command, or via npx sequant run. Not sure where to start? Try /solve.
Quality Loop
Automated IterationWhen tests fail, Sequant doesn't stop. It analyzes the failure, fixes the code, and retests — automatically. You review working code, not broken builds.
Or interactively: /loop 123. Built into /fullsolve by default.
Control retries with --max-iterations 5. Gate chains with --qa-gate.
for test failures
for QA issues
intervention
Quick Start
Zero to First PRInstall the package, then scaffold your project.
Requires Claude Code and GitHub CLI (gh auth login)
Point it at one or many GitHub issues.
Analyzes your issues and recommends the right workflow — including npx sequant run flags like --chain, --sequential, and --quality-loop. Run reference →
Full pipeline, headless, or step by step.
Skills also work without slash commands — just describe what you need. Cheat sheet →
FAQ
Common QuestionsWhat is Sequant?
A CLI tool that adds structured workflows to Claude Code. It orchestrates your AI coding sessions through defined phases — spec, exec, test, qa — with automated quality gates. Think of it as a workflow engine between your GitHub issues and Claude Code.
How is this different from using Claude Code directly?
Claude Code is freeform conversation. Sequant adds structure: acceptance criteria extracted from issues, isolated git worktrees for safe experimentation, automated test iteration, and quality gates that verify code before merge. You get the speed of AI with the confidence of a defined process.
What are the prerequisites?
Claude Code (requires a Claude subscription), GitHub CLI (gh auth login), Git, and Node.js 18+. Optional: Chrome DevTools MCP server for browser-based testing, Semgrep for enhanced security scanning.
Does it work with existing projects?
Yes. Run npm i sequant && npx sequant init in any git repository. It auto-detects your stack (Node.js, Python, Rust, Go, Next.js, Astro, and more) and configures accordingly. The worktree-based workflow works with any git repository.
What happens if the quality loop can't fix something?
The loop has bounded retries — 3 for test failures, 2 for QA issues. If a fix requires architectural decisions or ambiguous requirements, it stops and hands off for manual review. You're never stuck in an infinite loop.
Is my code sent anywhere?
Sequant collects zero telemetry, analytics, or user data. The only external communication is GitHub CLI operations you initiate (reading issues, creating PRs). Your code stays local.
Does it work with other AI models?
Sequant is built specifically for Claude Code. The workflow concepts are model-agnostic, but the current implementation requires Claude Code as the underlying AI engine.
Can I customize the workflow?
Extensively. Add project-specific coding standards via a constitution file, create custom slash commands, configure phase selection (skip spec, skip test), set custom base branches, and adjust loop iteration limits. Customizations live in .claude/.local/ and are never overwritten by updates.