CtrlK
BlogDocsLog inGet started
Tessl Logo

vibe-ai/spec-as-source

Adds spec-as-source enforcement to any project using spec-driven development

87

2.34x
Quality

91%

Does it follow best practices?

Impact

82%

2.34x

Average score across 5 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

task.mdevals/scenario-2/

Use spec-ci-sync to update the CI workflow for this project.

Project state:

  • pytest.ini is present (the project uses pytest)
  • .spec-source-manifest.json exists and lists these test files:
    • tests/auth/test_login.py
    • tests/auth/test_rate_limit.py
  • .github/workflows/spec-verification.yml already exists with an outdated test step

Expected behaviour: detect pytest, collect the spec-declared test files, generate the updated workflow, show a diff of what will change, ask for confirmation before overwriting, then write the file.

README.md

tile.json