skills.rest
pure-golang
pure-golangOFFICIAL
Explore all skills by this author →
GitHub

x-bdd-knowledge-harvest

Convert legacy code, docs, and git history into structured BDD .feature scenarios.

2|Updated Apr 12, 2026
Search Tags:#bdd#git history#given when then#feature files#legacy reverse engineering#scenario extraction#test translation
One-click install
npx skills add https://github.com/pure-golang/level85 --skill x-bdd-knowledge-harvest
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: x-bdd-knowledge-harvest
Source: https://github.com/pure-golang/level85/tree/main/.agents/skills/x-bdd-knowledge-harvest
Command: npx skills add https://github.com/pure-golang/level85 --skill x-bdd-knowledge-harvest

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves the problem of scattered legacy knowledge by helping you systematically extract business scenarios from code, tests, docs, git history, and human interviews into consistent BDD .feature files.

Core Features & Use Cases

  • Reverse-engineers observable behavior from legacy sources and converts it into Given/When/Then business scenarios.
  • Translates Arrange/Act/Assert into BDD while keeping technical details out of steps.
  • Produces ready-to-verify feature drafts using the expected file structure and cross-skill conventions (notably readiness checks via x-bdd-api and x-bdd-product-workflow).

Quick Start

Tell the AI: “Harvest BDD knowledge for the login flow in this repo and generate a feature file in features/ with business-readable scenarios, using existing tests and docs as the primary sources.”

Frequently Asked Questions about x-bdd-knowledge-harvest

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

FAQPage Schema
How do I extract BDD feature files from legacy code and git history?▼

To extract BDD feature files from legacy code and git history, you reverse-engineer observable behavior by translating Arrange/Act/Assert test structures and fragmented documentation into Given/When/Then business scenarios.

What is the best way to convert Arrange/Act/Assert tests into Given/When/Then scenarios?▼

Converting Arrange/Act/Assert tests into Given/When/Then scenarios involves extracting business-language steps from technical test setups and assertions, ensuring technical implementation details are kept out of the final BDD feature file steps.

How do I generate BDD scenarios for a repository that runs but lacks tests?▼

You generate BDD baseline scenarios by systematically harvesting knowledge from code, doc.go files, existing documentation, git history, and human interviews, structuring them into ready-to-verify .feature file drafts before refactoring.

Can I use git history and interviews to reverse-engineer legacy behavior into feature files?▼

Yes, you can reverse-engineer legacy behavior into feature files by analyzing git history and interview notes alongside source code, translating the discovered fragmented knowledge into structured Given/When/Then scenarios.

How do I align extracted BDD feature files with x-bdd-api naming conventions?▼

Aligning extracted BDD feature files with x-bdd-api conventions requires structuring the generated scenarios using the expected file structure, applying execution tags per channel policy, and matching cross-skill naming standards.

Related Skills

Explore More Software Engineering Skills→
ggazzoggazzo

reversa-detective

Extract implicit business rules and state machines from legacy Git repositories.

Community
Advanced
pure-golangpure-golang
2

x-bdd-product-workflow

Converts product requirements into business-ready BDD .feature files.

Official
Intermediate
MolcajeteAIMolcajeteAI
2

gherkin

Generate BDD scaffolds with feature files and step definitions.

Official
Intermediate
0xdeafcafe0xdeafcafe

backfill-feature

Backfill retroactive ADRs, Gherkin specs, and characterization tests for existing software features.

Community
Advanced