@martinffx/atelier 0.1.0

package/package.json

@@ -0,0 +1,44 @@
+{
+  "name": "@martinffx/atelier",
+  "version": "0.1.0",
+  "description": "Personal development toolkit - spec-driven development, code quality, deep thinking, and ecosystem patterns",
+  "type": "module",
+  "bin": {
+    "atelier": "dist/atelier.js"
+  },
+  "repository": "github:martinffx/atelier",
+  "keywords": ["cli", "claude-code", "opencode", "ai-agents", "spec-driven-development"],
+  "license": "MIT",
+  "files": [
+    "dist/",
+    "skills/",
+    "agents/",
+    "README.md",
+    "LICENSE",
+    "CHANGELOG.md"
+  ],
+  "scripts": {
+    "build": "bun build ./src/atelier.ts --outdir ./dist --target bun",
+    "typecheck": "tsgo --noEmit",
+    "test": "bun test",
+    "publish": "bun run build && npm publish",
+    "prepare": "simple-git-hooks"
+  },
+  "simple-git-hooks": {
+    "commit-msg": "npx --no -- commitlint --edit $1"
+  },
+  "dependencies": {
+    "commander": "^13.1.0",
+    "gray-matter": "^4.0.3",
+    "inquirer": "^12.5.2",
+    "zod": "^3.25.0"
+  },
+  "devDependencies": {
+    "@commitlint/cli": "^19.8.0",
+    "@commitlint/config-conventional": "^19.8.0",
+    "@types/bun": "^1.3.13",
+    "@types/node": "^22.14.1",
+    "simple-git-hooks": "^2.12.1",
+    "@typescript/native-preview": "^7.0.0-dev.20260514.1"
+  }
+}

package/skills/code-conventional-commit/SKILL.md

@@ -0,0 +1,134 @@
+---
+name: code-conventional-commit
+description: Generate and validate conventional commit messages following the conventionalcommits.org spec. Use whenever the user wants to commit code, mentions commit messages, git commit, or asks to create a commit. Triggers on "commit", "git commit", "conventional", or when reviewing commit message format.
+user-invocable: true
+---
+
+# Conventional Commit Skill
+
+Generate and validate commit messages following the [Conventional Commits](https://www.conventionalcommits.org/) specification.
+
+## Conventional Commit Format
+
+```
+<type>(<scope>): <subject>
+
+[optional body]
+
+[optional footer(s)]
+```
+
+### Types
+
+| Type | Description |
+|------|-------------|
+| `feat` | New feature |
+| `fix` | Bug fix |
+| `docs` | Documentation only |
+| `style` | Code style (formatting, semicolons, etc.) |
+| `refactor` | Code change that neither fixes nor adds |
+| `test` | Adding or updating tests |
+| `chore` | Build, tooling, dependencies |
+| `perf` | Performance improvement |
+| `ci` | CI configuration changes |
+| `build` | Build system or dependencies |
+| `revert` | Reverting a previous commit |
+
+### Rules
+
+- **Subject**: Short description, imperative mood, lowercase, no period at end
+- **Scope**: Optional, lowercase, describes what was changed (e.g., `auth`, `api`, `ui`)
+- **Breaking changes**: Add `!` after type/scope: `feat(auth)!: change API`
+- **Footer**: For breaking changes (`BREAKING CHANGE:`) or issue references (`Closes #123`)
+
+## Operations
+
+### 1. Generate Commit from Diff
+
+When user wants to commit changes:
+
+1. Run `git status` to see changed files
+2. Run `git diff --staged` for staged changes
+3. Analyze what changed to determine:
+   - **Type**: Which type best describes the changes?
+   - **Scope**: What area was affected? (optional)
+   - **Subject**: What was done? (imperative: "add" not "added")
+4. Create a conventional commit message
+5. Run `git commit -m "<message>"`
+
+**Example:**
+```
+feat(auth): add JWT token refresh
+
+Implements token refresh endpoint to extend sessions
+without requiring re-authentication.
+
+Closes #142
+```
+
+### 2. Validate Commit Message
+
+When user asks to validate or check a commit message:
+
+1. Parse the commit message
+2. Check format: `<type>(<scope>): <subject>`
+3. Validate type is from the allowed list
+4. Check subject follows rules (lowercase, imperative, no period)
+5. Flag any issues found
+
+## Input Methods
+
+| Input | Action |
+|-------|--------|
+| User says "commit" or "git commit" | Generate from git diff, then commit |
+| User says "validate commit" | Check the commit message format |
+| User pastes commit message | Validate the provided message |
+
+## Auto-Commit Workflow
+
+When generating a commit:
+
+1. Show the user the commit message first
+2. Ask for confirmation before committing (unless user explicitly says "just do it")
+3. Execute `git commit -m "<message>"` after confirmation
+4. Show the result of the commit
+
+## Error Handling
+
+- If no staged changes: `git status` shows nothing → warn user nothing to commit
+- If git not initialized: Initialize repo or warn user
+- If commit fails: Show error and offer to retry
+
+## Examples
+
+**Input:** "I fixed the login bug"
+**Output:**
+```
+fix(auth): resolve login timeout issue
+
+Users were logged out after 5 minutes due to
+incorrect token expiry calculation.
+```
+
+**Input:** "I added a new API endpoint for users"
+**Output:**
+```
+feat(api): add user profile endpoint
+
+GET /users/:id returns user profile data including
+name, email, and avatar URL.
+
+Closes #89
+```
+
+**Input:** "I changed the auth API, this breaks old clients"
+**Output:**
+```
+feat(auth)!: change token validation endpoint
+
+The /auth/verify endpoint now requires Bearer token
+instead of query parameter.
+
+BREAKING CHANGE: Clients must update to send
+Authorization header with Bearer token.
+```

package/skills/code-conventional-commit/evals/evals.json

@@ -0,0 +1,23 @@
+{
+  "skill_name": "conventional-commit",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Generate a commit message for these changes: Added a new user profile page component that displays user name, email, and avatar. Also added a settings modal for updating preferences.",
+      "expected_output": "Should produce a feat commit with proper scope, imperative subject, and optional body",
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "Validate this commit message: 'feat: added new login page' - is it valid conventional commit format?",
+      "expected_output": "Should identify issues: subject should be lowercase, imperative (add not added), possibly missing scope",
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "I made breaking changes to the API - the old /v1/users endpoint now returns different JSON structure. Create a commit message that properly indicates this is a breaking change.",
+      "expected_output": "Should produce a commit with ! in type (e.g., feat! or fix!) and BREAKING CHANGE footer",
+      "files": []
+    }
+  ]
+}

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

@@ -0,0 +1,4 @@
+feat(profile): add user profile page with settings modal
+
+Adds new profile page component displaying user name, email, and
+avatar. Includes settings modal for updating user preferences.

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

@@ -0,0 +1,6 @@
+{
+  "eval_id": 0,
+  "eval_name": "generate-commit",
+  "prompt": "Generate a commit message for these changes: Added a new user profile page component that displays user name, email, and avatar. Also added a settings modal for updating preferences.",
+  "assertions": []
+}

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

@@ -0,0 +1,6 @@
+{
+  "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

@@ -0,0 +1,16 @@
+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

@@ -0,0 +1,8 @@
+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

@@ -0,0 +1,6 @@
+{
+  "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": []
+}