agentleFS
Sign inStart free
KadirHarmancKadirHarmanc/nazar-skill/skills/yaml-gen/SKILL.md

yaml-gen

Skill0 starsChanged 8 months agoMITView on GitHub

Generate YAML test files from project structure. Use when user says 'generate test', 'test olustur', 'yaml olustur', 'create test file', 'test yaz', 'generate yaml'.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Write YAML files to .nazar/tests/ directory:

    line 23

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Nazar YAML Test Generator

Auto-generate YAML UI test files from your project structure.

How to run

  1. Scan project structure:
    • React Native: look in src/screens/, src/pages/, app/ for screen components
    • Flutter: look in lib/screens/, lib/pages/ for widget files
    • Expo: check app/ directory (file-based routing) or src/screens/
  2. For each screen found:
    • Detect navigation elements (buttons, links, tab items)
    • Detect form inputs (TextInput, TextField, input elements)
    • Detect interactive elements (touchable, gesture detector, button)
  3. Generate test scenarios:
    • Navigation flow: launch -> navigate to each screen -> verify visible
    • Form flow: navigate to form -> fill inputs -> submit -> verify result
    • Auth flow: if login screen found, generate login test
  4. Write YAML files to .nazar/tests/ directory:
    • One file per screen or flow
    • apiVersion: nazar/v1 format
  5. Report: N test files generated, M screens covered, K interactions mapped
  6. Suggest: "Run /nazar:live-test to execute these tests"

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free