review-seq

Orchestrates batched Python code analysis tools with disk-persisted, resumable workflows.

Updated Sep 9, 2024
One-click install
npx skills add https://github.com/axel-kaliff/dotfiles --skill review-seq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-seq
Source: https://github.com/axel-kaliff/dotfiles/tree/main/claude/.claude/skills/review-seq
Command: npx skills add https://github.com/axel-kaliff/dotfiles --skill review-seq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a resilient, disk-backed code review orchestration that prevents findings from being lost to context overflow by persisting per-tool outputs, compacting context between waves, and supporting resume after interruptions. It ensures every automated analysis gets full attention and that large or long-running reviews remain deterministic and recoverable.

Core Features & Use Cases

  • Batched analysis with persistence: Run analysis tools in parallel batches or sequentially while writing findings to a claude_session directory so no results depend on ephemeral context.
  • Resume and compaction points: Recover interrupted runs and compact context between batches to avoid context-window loss while preserving a full audit trail.
  • Scoring, root-cause, and fix plan generation: Aggregate findings, deduplicate and score them, run root-cause analysis waves, and produce a prioritized fix plan with anchors for safe automated fixes in review-fix mode.
  • Practical scenarios: Use for pre-merge gate checks, automated review-and-fix workflows, or multi-session reviews on large Python changesets where tools like ruff, ty, semgrep, and pytest are used.

Quick Start

Run the review-seq pipeline on the current branch in review-fix mode to persist findings, score and analyze root causes, and produce a prioritized fix plan.

Frequently Asked Questions about review-seq

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a persistent code review pipeline that survives context overflow?

Batched code review with disk persistence writes per-tool findings to a claude_session directory, compacts context between analysis waves, and supports resume after interruptions so no results depend on ephemeral context windows.

Can I resume an interrupted multi-batch code review without losing previous findings?

Yes, interrupted multi-batch code reviews resume deterministically because all per-tool findings are persisted to a claude_session directory on disk, preserving a full audit trail and allowing recovery without re-running completed analysis waves.

What static analysis tools do I need for a Python branch diff pre-merge review?

Python branch diff pre-merge reviews require ruff, ty, semgrep, and pytest, with optional import-linter for full checks. You also need repository git access and the ability to write claude_session state files to disk.

How does batched static analysis with semgrep and ruff generate a prioritized fix plan?

Batched static analysis with semgrep and ruff persists findings to disk, then aggregates, deduplicates, and scores them. Root-cause analysis waves produce a prioritized fix plan with anchors for safe automated fixes in review-fix mode.

What's the best way to review and auto-fix large Python changesets without losing analysis results?

Reviewing and auto-fixing large Python changesets is best handled by a disk-persisted batched pipeline that runs analysis tools in parallel, compacts context between waves, and produces a prioritized fix plan with anchors for safe automated fixes.

When should I not use a disk-persisted batched code review pipeline?

A disk-persisted batched code review pipeline is not suited for environments lacking git access, the ability to write claude_session state files, or required analysis tools like ruff, ty, semgrep, and pytest. It also adds overhead for small, quick reviews.