@martinffx/atelier 1.0.1 → 1.1.0

package/skills/code-conventional-commit/workspace/iteration-1/eval-1/with_skill/outputs/eval_metadata.json

@@ -1,6 +0,0 @@
-{
-  "eval_id": 1,
-  "eval_name": "validate-commit",
-  "prompt": "Validate this commit message: 'feat: added new login page' - is it valid conventional commit format?",
-  "assertions": []
-}

package/skills/code-conventional-commit/workspace/iteration-1/eval-1/with_skill/outputs/validation-result.txt

@@ -1,16 +0,0 @@
-VALIDATION RESULT
-=================
-Message: 'feat: added new login page'
-
-IS VALID: NO
-
-Format Check:
-- Type: 'feat' ✓ (valid type)
-- Scope: (optional, omitted) ✓
-- Subject: 'added new login page' 
-
-Issues Found:
-1. Subject must use imperative mood: use 'add' instead of 'added'
-
-Correct format:
-feat: add new login page

package/skills/code-conventional-commit/workspace/iteration-1/eval-2/with_skill/outputs/commit-message.txt

@@ -1,8 +0,0 @@
-feat(api)!: restructure /v1/users response format
-
-The /v1/users endpoint now returns a different JSON structure
-with nested data envelope and updated field names.
-
-BREAKING CHANGE: Response format changed from flat structure
-to { data: {...}, meta: {...} }. Clients must update parsing
-to access user fields via response.data instead of directly.

package/skills/code-conventional-commit/workspace/iteration-1/eval-2/with_skill/outputs/eval_metadata.json

@@ -1,6 +0,0 @@
-{
-  "eval_id": 2,
-  "eval_name": "breaking-change-commit",
-  "prompt": "Create a commit message that properly indicates breaking changes to the /v1/users API endpoint",
-  "assertions": []
-}