sharpy

Suggest and apply a semver version bump based on commits since the last tag

Push current branch to remote origin

Scaffold a new Sharpy.Stdlib module (spy-sourced or handwritten C#) with all required files, conventions, docs, and tests

Implement a plan with a coordinated agent team

Run compiler or cross-language benchmarks and compare results

Regenerate C# snapshot tests and spy stdlib after intentional codegen changes

Stress-test property tests across many rounds to find rare bugs. Each round uses fresh random seeds.

Build the Sharpy solution with smart output truncation

Run Sharpy tests with smart output - shows summary on success, last 80 lines on failure with full log saved

Run the Sharpy playground (Blazor WASM) locally with hot reload

Get LSP hover tooltip for a position in a .spy file (emulates VS Code hover)

Interactive LSP review session — user reports hover/coloring issues from VS Code, Claude files GitHub issues

Stage and commit current changes with an auto-generated message

Format code whitespace per project conventions (also auto-formatted on save by Claude hook)

Close GitHub issues that have been implemented, with verification

Run a comprehensive compiler health audit

Emit C# and run a .spy file or inline source in one shot

Emit compiler output (csharp, ast, tokens, diagnostics) from a .spy file or inline source

Compile and run a Sharpy source file or inline source code

Run all gap discovery tests and present a unified summary

Create a file-based integration test (.spy + .expected/.error pair)

Kill zombie dotnet processes and clean build artifacts

Create an implementation plan from GitHub issues or a description

Verify completed plan implementation, fix gaps/bugs/regressions, and commit fixes

Run dogfooding iterations to test the Sharpy compiler

Verify a plan for accuracy and architectural soundness

Analyze dogfood results and classify failures by root cause

Run a Python 3 expression or snippet to verify behavior before implementing Sharpy semantics