chimera

Analyze files changed during WrongStack sessions and generate one-line findings with severity and fixes.

224|27|Updated May 12, 2026
One-click install
npx skills add https://github.com/WrongStack/WrongStack --skill chimera
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chimera
Source: https://github.com/WrongStack/WrongStack/tree/main/packages/core/skills/chimera
Command: npx skills add https://github.com/WrongStack/WrongStack --skill chimera

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-session quality review of files changed during a WrongStack session, surfacing new issues without re-litigating prior decisions.

Core Features & Use Cases

  • Surgical, rule-based analysis that flags only real issues that emerged in the latest session.
  • Produces a structured, one-line-per-find report with severity and file:line context, plus a concise fix suggestion.
  • Works across WrongStack's REPL, TUI, and web UI to support fast iteration after sessions.

Quick Start

After finishing a WrongStack session, run Chimera to generate a concise quality report for changed files.

Frequently Asked Questions about chimera

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

FAQPage Schema
How do I automate code quality reviews for files modified during a development session?

Post-session code review automation analyzes files added or modified during a session, applying surgical rule-based analysis to flag only real issues that emerged. It generates a structured report with one finding per line, including severity, file:line context, and a concise fix suggestion.

What is the best way to surface new code issues without re-litigating prior decisions?

Surgical static analysis targets only new issues from the latest session changes, avoiding prior decision re-litigation. It produces a concise, one-line-per-find report with severity rankings and file:line context, plus a one-sentence fix suggestion for fast iteration.

Does post-session code review work across REPL, TUI, and browser UI workflows?

Post-session code review works across REPL, TUI, and web UI workflows to support fast iteration after sessions. It handles multiple files added or modified during a session, generating a concise quality report with surgical findings and severity rankings.

How do I generate a structured static analysis report with severity rankings for changed files?

Run a post-session code review to generate a structured report containing one finding per line with severity, file:line context, and a one-sentence fix. The prescribed output format includes a final summary of all surgical findings for the changed files.

What format does post-session static analysis output use for code review findings?

Post-session static analysis outputs one finding per line, specifying severity, file:line location, and a one-sentence fix suggestion. The prescribed format concludes with a final summary, providing concise and surgical findings for modified files.

When do I need post-session static analysis for code review?

Post-session static analysis is needed after finishing a development session to perform quality review of changed files. It surfaces new issues that emerged in the latest session, enabling fast iteration without re-litigating prior code decisions.