behavior-spec-to-ci-checks

Convert Gherkin .feature files into test scaffolds and GitHub Actions workflows.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/ytqh/agent-skills --skill behavior-spec-to-ci-checks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: behavior-spec-to-ci-checks
Source: https://github.com/ytqh/agent-skills/tree/main/skills/behavior-spec-to-ci-checks
Command: npx skills add https://github.com/ytqh/agent-skills --skill behavior-spec-to-ci-checks

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill converts Gherkin behavior specifications into automated PR quality gates and tests, reducing manual CI setup and ensuring consistent gate enforcement across repositories.

Core Features & Use Cases

  • Spec-driven test scaffolding: generates UT/Integration/E2E test skeletons from docs/spec*/**/*.feature.
  • CI workflow templating: copies workflow templates into the target repo to enforce gating.
  • Local generation only: the script is for local scaffolding and should not be invoked by CI.

Quick Start

Use the provided generator to scaffold tests and a CI workflow from your Gherkin specs: python "$HOME/.agents/skills/behavior-spec-to-ci-checks/scripts/generate_checks_from_gherkin.py"
--repo-root .
--tests-dir tests/behavior
--write-workflow

Frequently Asked Questions about behavior-spec-to-ci-checks

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

FAQPage Schema
How do I generate GitHub Actions CI checks from Gherkin feature files?

You can generate CI checks from Gherkin feature files by running a local Python script that scaffolds UT, Integration, and E2E tests, and copies a workflow template to enforce PR quality gates in GitHub Actions.

What is the best way to automate PR quality gates from behavior specs?

Automating PR quality gates from behavior specs involves converting Gherkin .feature files into automated test skeletons and a CI workflow template, ensuring consistent gate enforcement across repositories without manual CI setup.

Do I need to run the Gherkin to CI check generator inside my CI pipeline?

No, the Gherkin to CI check generator is designed for local scaffolding only. It should not be invoked by CI at runtime, as it avoids CI-time path assumptions by generating tests and workflows locally before committing.

Can I use this tool if my behavior specs are not in the docs/spec directory?

No, this tool specifically targets repositories containing behavior specs in the docs/spec or docs/specs directories with .feature files, converting those Gherkin behavior specifications into automated PR quality gates.

How does the script handle dependency injection and mocking for generated tests?

The script handles dependency injection and mocking by providing asset templates and references alongside the generated UT, Integration, and E2E test scaffolds, adhering to project guidelines for test setup.

What branch coverage standard is enforced by the generated GitHub Actions workflow?

The generated GitHub Actions workflow enforces a strict 100% branch coverage standard for core logic, acting as an automated PR quality gate to prevent merging untested code paths.