gti-test

Generate empty test case shells from Gherkin feature files.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/CodeMachine0121/gti-agent-cycle-skill --skill gti-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gti-test
Source: https://github.com/CodeMachine0121/gti-agent-cycle-skill/tree/main/skills/gti-test
Command: npx skills add https://github.com/CodeMachine0121/gti-agent-cycle-skill --skill gti-test

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill automates the creation of test case stubs, translating Gherkin scenarios into executable test function shells, accelerating the TDD cycle.

Core Features & Use Cases

  • Gherkin to Test Mapping: Converts each scenario in a .feature file into a corresponding empty test function.
  • Framework Agnostic: Detects and adapts to various testing frameworks (Vitest, Jest, JUnit, pytest, Go testing, Rust, RSpec).
  • Use Case: After defining feature requirements in Gherkin, use this Skill to instantly generate the structure for all your tests, ensuring no scenario is missed before implementation begins.

Quick Start

Use the gti-test skill to generate test shells for the feature defined in docs/user_login/user_login.feature.

Frequently Asked Questions about gti-test

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

FAQPage Schema
How do I generate test stubs from Gherkin feature files?

To generate test stubs from Gherkin feature files, this Skill maps scenarios to snake_case or camelCase function names, creating describe/it or Test/it blocks without assertions for frameworks like Vitest, Jest, and pytest.

Can I generate empty test shells for Go and Rust testing frameworks?

Yes, you can generate empty test shells for Go and Rust testing frameworks. The Skill detects the project's test framework and adapts the test case structures to match the target language conventions.

Does generating Gherkin test case shells support Java and Ruby?

Generating Gherkin test case shells supports Java and Ruby by mapping scenarios to executable test function shells. It adapts to JUnit and RSpec structures to accelerate the TDD cycle.

What is the best way to automate test structure creation for BDD scenarios?

Automating test structure creation for BDD scenarios is best handled by translating Gherkin feature files into empty test function shells. This ensures no scenario is missed before implementation begins.

How do I convert Gherkin scenarios to executable test functions?

To convert Gherkin scenarios to executable test functions, the Skill reads .feature files and maps each scenario to an empty test function shell, instantly generating the structure for all tests.

Why does the generated test shell not contain assertions?

Generated test shells do not contain assertions because the Skill is designed to automate the creation of test case stubs, providing the structural describe/it or Test/it blocks to accelerate the TDD cycle before implementation.