Lolpack Pyrefly Lsp
- 1 repo stars
- Updated January 23, 2026
- lolpack/pyrefly-lsp
lolpack-pyrefly-lsp is a Claude Code plugin that configures Pyrefly LSP integration so Python analysis stays consistent while the agent codes.
About
lolpack-pyrefly-lsp is a compact Claude Code plugin from lolpack/pyrefly-lsp that ships Pyrefly configuration for use with Claude. developers 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.
- 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
Lolpack Pyrefly Lsp by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin install lolpack-pyrefly-lsp@lolpack/pyrefly-lspAdd your badge
Show developers this plugin is listed on Skillselion. Paste this into your README.
| repo stars | ★ 1 |
|---|---|
| Last updated | January 23, 2026 |
| Repository | lolpack/pyrefly-lsp ↗ |
What it does
Wire Pyrefly language-server behavior into Claude Code so Python typing and analysis feedback stays consistent while the agent edits your project.
Who is it for?
Python developers already standardized on Pyrefly who want Claude Code edits to see the same LSP signals they do in the editor.
Skip if: JavaScript-only repos, teams on mypy or pyright without Pyrefly, or developers who do not use language-server integrations with agents.
What you get
After registration, the agent environment can honor Pyrefly-oriented LSP configuration so typing feedback matches your Pyrefly-based workflow.
- Agent-side Pyrefly LSP configuration parity with your workflow
- Fewer agent edits that ignore Pyrefly-visible issues
- A single-plugin integration surface for Pyrefly plus Claude Code
By the numbers
- Plugin count in bundle: 1
- Repository: lolpack/pyrefly-lsp
- Catalog keywords: lsp, pyrefly
Recommended Plugins
0xbigboss Linear CliLinear CLI built with Zig1
15195999826 LomomarketplaceLomo's Claude Code Plugin Marketplace1
1broseidon MarketplaceCurated collection of Claude Code plugins for fullstack development teams1
4rgon4ut Cc Zig LspZig LSP plugin for Claude Code4
708u TwigSimplify git worktree and branch management with configurable symlinks, change carrying, and cleanup.22
8avalon8 AvalonclaudemarketAvalon 的 Claude Code 插件市场How it compares
Pyrefly LSP bridge plugin, not a standalone code-review or test-runner skill.
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.