Lolpack Pyrefly Lsp
lolpack-pyrefly-lsp is a Claude Code plugin for the Build phase that configures Pyrefly LSP integration so Python analysis stays consistent while the agent codes.
by lolpack · github.com/lolpack/pyrefly-lsp
Wire Pyrefly language-server behavior into Claude Code so Python typing and analysis feedback stays consistent while the agent edits your project.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install lolpack-pyrefly-lsp@lolpack/pyrefly-lspBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:lolpack/pyrefly-lsp") and the paste-ready config with skillselion.get_install_config("plugin:lolpack/pyrefly-lsp").
What it does
lolpack-pyrefly-lsp is a compact Claude Code plugin from lolpack/pyrefly-lsp that ships Pyrefly configuration for use with Claude. Solo builders on Python often run Pyrefly locally for fast type and analysis feedback, but the agent side can drift—different roots, ignored paths, or missing LSP hooks—so suggestions compile in chat yet fail Pyrefly in CI. This marketplace entry exists to align the agent’s language-server view with the Pyrefly workflow you already chose, which keeps implementation loops tighter when Claude Code is doing multi-file edits. With only one plugin and keywords limited to lsp and pyrefly, expect a narrow integration layer rather than a full testing or DevOps suite. Install it during active backend or tooling build on Python codebases; skip it if you do not use Pyrefly or if your project language is not in its scope.
Highlights
- Single-plugin bundle: Pyrefly LSP configuration tailored for Claude
- Bridges Python static analysis through the language-server protocol in the agent environment
- Minimal surface area—focused on pyrefly and lsp keywords rather than broad framework scaffolding
- Helps keep type and analysis signals aligned between your local Pyrefly setup and Claude Code
- Best for Python repos where Pyrefly is already the chosen checker
Why builders use it
Claude Code can edit Python without your Pyrefly LSP settings, so agent changes miss the same diagnostics you rely on locally and in CI.
After registration, the agent environment can honor Pyrefly-oriented LSP configuration so typing feedback matches your Pyrefly-based workflow.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 1 stars, 0 votes.
FAQ
Who is lolpack-pyrefly-lsp for?
Developers using Pyrefly on Python projects who want Claude Code to respect that checker through LSP-style configuration.
When should I use lolpack-pyrefly-lsp?
Use it when you start agent-assisted Python work and notice mismatches between Pyrefly diagnostics locally and what Claude assumes in the repo.
How do I add lolpack-pyrefly-lsp to my agent?
Add the lolpack/pyrefly-lsp plugin from Skillselion to Claude Code and ensure your project’s Pyrefly config paths match what the plugin documents.
Comments
Share how you use lolpack-pyrefly-lsp, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.