Loading
Reactive Python style review using PEP 8, project-specific style rules, and relevant companion conventions for docstrings and type annotations.
npx skills add Reactive-Skills/skills --skill pep8-reviewnpx -y @reactive-skills/axi invoke pep8-review7
Hierarchical nodes
INIT
Bootstrap entrypoint
4
Whitelisted for safety
2
Automated projections
Visual state machine topology parsed directly from the official STATECHART.md in Reactive-Skills/skills:
Each state is an isolated operational slice. Transitions occur only when typed signals satisfy programmatic guard conditions.
Verify reactive runtime access
Outgoing Transitions
payload.compatible === trueCollect review input and scope
Outgoing Transitions
payload.review_input != null && ['changed_lines', 'full_files'].includes(payload.review_scope)Read project style rules and settings
Outgoing Transitions
Array.isArray(payload.style_sources) && payload.style_sources.length > 0 && payload.project_rules != nullCheck Python changes against applicable style rules
Outgoing Transitions
Array.isArray(payload.findings) && payload.finding_count === payload.findings.length && payload.outcome === (payload.findings.length === 0 ? 'no_findings' : 'findings') && payload.findings.every(item => item && item.file && Number.isInteger(item.line) && item.rule && item.explanation && item.suggestion)Deliver the completed style review
Recover from work outside the signal contract
Explain why the review could not start
Inspect or drive this state machine directly via the token-efficient AXI CLI:
Check state:
Inspect hierarchy:
Tail events:
Runtime variables persisted across state transitions:
runtimereview_inputreview_subjectproject_rootchanged_filesreview_scopepython_versionproject_rulesstyle_sourcesfindingsfinding_countreview_summaryoutcomeerror_reasonbypass_reasonRead models automatically rendered upon transition:
Add to your Claude Desktop, Cursor, or VS Code settings:
{
"mcpServers": {
"reactive-skills": {
"command": "npx",
"args": [
"-y",
"@reactive-skills/axi",
"mcp"
]
}
}
}