Parser Fix
SkillMonitoring & opsRun a TDD parser-fix workflow for perl-parser-core or related parser crates. Use when a parser bug has a concrete failing construct and needs tests, a minimal fix, and verification.
Available today. Use it from your connected AI after setup.
No other account needed.
Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
Then ask your AI: use the Parser Fix skill
What this skill tells your AI
The instructions your AI receives, as published by effortlessmetrics/perl-lsp in docs/reference/archive/old-infrastructure/skills/parser-fix/SKILL.md and read by ahel’s review.
Fix a parser bug with a failing test first. Bug: $ARGUMENTS
Workflow
- Find the relevant parser code under
crates/perl-parser-core/src/engine/parser/ - Add failing tests first in the right parser test file
- Implement the smallest fix that makes the new tests pass
- Verify the parser crates cleanly
- Return a concise receipt for the handoff or PR
Root-Cause Search
Start with the file surface most likely to own the construct:
variables.rsstatements.rsexpressions/postfix.rsexpressions/precedence.rsdeclarations.rs
Understand why the construct fails before editing.
Test-First Rule
Add tests before the fix. Prefer crate-local parser tests that parse a Perl snippet and assert success or the intended AST shape.
Verification
cargo fmt --all
cargo clippy -p perl-parser-core --lib
cargo test -p perl-parser-core
cargo test -p perl-parser
Keep the fix narrow. If the failure turns out to be primarily lexer or corpus work, route it into the right worker instead of silently widening the slice.
Signals
- GitHub stars
- 26
- Forks
- 7
- Last commit
- Sep 2026
Advanced
- Item type
- skill
- Key
parser-fix- Source
- github.com/effortlessmetrics/perl-lsp