trace-state-machine

Map PR status transitions in TypeScript sources with triggers and file locations.

Updated Jan 30, 2026

Search Tags:#typescript #code-analysis #anomaly-detection #state-machine #pr-status #transition-graph

Ready to run

npx skills add https://github.com/martin-janci/claude-code-reviewer --skill trace-state-machine

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: trace-state-machine
Source: https://github.com/martin-janci/claude-code-reviewer/tree/main/.claude/skills/trace-state-machine
Command: npx skills add https://github.com/martin-janci/claude-code-reviewer --skill trace-state-machine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and map all PR status transitions within the claude-code-reviewer project to understand lifecycle behavior and spot inconsistencies.

Core Features & Use Cases

Extract all PRStatus values from src/types.ts and enumerate transitions across src/reviewer/reviewer.ts, src/webhook/server.ts, src/state/store.ts, src/reviewer/comment-verifier.ts, src/polling/poller.ts, and other related files.
Build a complete transition graph detailing From, To, Trigger, and File:Line for every detected transition.
Flag anomalies and compare against the documented flow to ensure consistency and detect gaps.

Quick Start

Run the trace-state-machine skill to generate the transition graph and anomaly report for the current codebase.

Frequently Asked Questions about trace-state-machine

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

FAQPage Schema

How do I map PR status transitions in a TypeScript codebase?▼

Mapping PR status transitions involves scanning TypeScript source files to extract PRStatus values and detect setStatus or store.update calls, producing a transition table with From, To, Trigger, and File:Line columns.

What is a state machine transition graph for pull request lifecycles?▼

A PR lifecycle transition graph enumerates valid status changes by detailing From and To states, the Trigger causing the change, and the exact File:Line location to validate behavioral consistency.

How do I detect anomalies in my state machine's status assignments?▼

Detect status assignment anomalies by building a complete transition graph from the codebase and comparing detected transitions against the documented flow to flag inconsistencies and gaps.

Does this state machine analysis work with any TypeScript project structure?▼

This state machine analysis targets the claude-code-reviewer project structure, specifically scanning source files under src like reviewer.ts, server.ts, and store.ts to enumerate and validate transitions.

What's the best way to trace state transitions triggered by setStatus and store.update?▼

Trace setStatus and store.update transitions by analyzing TypeScript sources to extract all PRStatus values and output a comprehensive transition table with File:Line references for every detected change.