skills.rest
mkaput
mkaputCOMMUNITY
Explore all skills by this author →
Website𝕏@jajakobylyGitHub

parser-grill

Distill failing Elixirij parser fixtures into minimal, anonymized smoke tests.

3|1|Updated Nov 26, 2025
Search Tags:#fixtures#elixir#gradle#parser#smoke-tests#anonymize#grill
One-click install
npx skills add https://github.com/mkaput/elixirij --skill parser-grill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: parser-grill
Source: https://github.com/mkaput/elixirij/tree/main/.agents/skills/parser-grill
Command: npx skills add https://github.com/mkaput/elixirij --skill parser-grill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Distills failing Elixirij parser fixtures into minimal, anonymized smoke tests that can be reviewed and fixed iteratively.

Core Features & Use Cases

  • Gradle-based grilling workflow that runs ParserGrill.kt against a target path to produce parser smoke-test fixtures.
  • Automates minimization and anonymization of fixtures to prevent leakage of proprietary code.
  • Renames tests and fixtures to clearly describe the underlying bug for easier tracking.
  • Supports iterative verification by regenerating outputs and re-running parser tests.

Quick Start

Run the Gradle task to grill a target path for Elixir sources and generate parser smoke-test fixtures.

Frequently Asked Questions about parser-grill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I minimize failing Elixir parser fixtures into smoke tests?▼

You can minimize failing Elixir parser fixtures into smoke tests by running a Gradle-based grilling task that distills failing parser outputs into minimal, anonymized test cases for easier review and tracking.

How do I anonymize Elixir parser test fixtures to prevent proprietary code leakage?▼

You anonymize Elixir parser test fixtures by applying automated anonymization during the fixture minimization process, stripping out proprietary code while preserving the underlying parser bug for tracking.

Does the parser smoke-test generation workflow require Gradle?▼

Yes, the parser smoke-test generation workflow requires Gradle to run the grilling task against a target codebase path, producing deterministic parser fixtures and verifying regressions iteratively.

What is the best way to rename Elixir parser smoke tests for bug tracking?▼

The best way to rename Elixir parser smoke tests for bug tracking is to use the grilling workflow, which automatically renames tests and fixtures to clearly describe the underlying parser bug being addressed.

Why are my generated Elixir parser smoke tests failing during regression verification?▼

Generated Elixir parser smoke tests may fail during regression verification if the fixture minimization or anonymization altered the parsing logic, requiring you to iteratively regenerate outputs and re-run the parser tests.

Related Skills

Explore More Software Engineering Skills→
lhotarilhotari
8

investigate-ci

Analyze failing GitHub Actions CI logs and test reports for Maven or Gradle Java projects.

Community
Advanced
meta-pytorchmeta-pytorch
2.5k

implement

Generate minimal code changes to fix failing tests from /write-tests runs.

Official
Intermediate
LeKayLeKay

smoke-check

Execute automated and manual smoke tests in CI/CD pipelines.

Community
Advanced
constructive-ioconstructive-io
232

code-generation

Generate TypeScript AST code and PostgreSQL keyword lists from protobuf definitions.

Official
Intermediate