team-toon-tack 3.2.2 → 3.2.4

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
 	"name": "team-toon-tack",
 	"description": "Linear/Trello task sync & management CLI for Claude Code - saves tokens vs MCP",
-	"version": "2.4.0",
+	"version": "2.5.0",
 	"author": {
 		"name": "wayne930242",
 		"email": "wayne930242@gmail.com"

package/commands/ttt:done.md

@@ -57,8 +57,6 @@ Also:
 ## Before Running
 
 Ensure you have:
-1. **Run project validation** - Use `/validate` command or validation skill if available
-2. Committed your changes with a meaningful message
-3. Pushed to remote branch (if applicable)
-
-**Important**: If validation fails, fix issues before marking as done.
+1. Committed your changes with a meaningful message
+2. Pushed to remote branch (if applicable)
+3. Verified code quality (lint, type-check) if applicable

package/commands/ttt:work-on.md

@@ -44,36 +44,48 @@ ttt work-on next
 
 1. Read the task description and requirements
 2. Check out the suggested branch: `git checkout -b <branch-name>`
-3. **Run project validation** (see below)
+3. **Check for work-on skill** (see below)
 4. Begin implementation
 
-## Project Validation
+## Work-On Skill
 
-Before starting work, check for validation tools:
+Check for project-specific work guidelines:
 
-### 1. Check for Existing Validation
+### 1. Check for Existing Work-On Skill
 
 Look for:
-- **Commands**: `/validate`, `/check`, `/lint` in available commands
-- **Skills**: `validate`, `check`, `verify` in available skills
-- **Scripts**: `lint`, `type-check`, `test` in `package.json` or `Makefile`
+- **Skills**: `work-on`, `start-work`, `begin-task` in `.claude/skills/`
+- **Alternative**: Check for `validate`, `check` skills that define project guidelines
 
-### 2. If No Validation Found
+### 2. If No Work-On Skill Found
 
-Ask user:
+Suggest user create one:
 ```
-No validation command or skill found for this project.
+No work-on skill found for this project.
+
+A work-on skill defines best practices for starting tasks:
+- Code style and conventions
+- Pre-work validation checks
+- Branch naming conventions
+- Required setup steps
+
 Would you like to create one? (y/n)
 ```
 
 If yes, run:
 ```
-/ttt:write-validate
+/ttt:write-work-on-skill
 ```
 
-### 3. Run Validation
+The work-on skill should include:
+- **Validation**: lint, type-check, test commands
+- **Code style**: formatting, naming conventions
+- **Workflow**: branch naming, commit message format
+- **Setup**: required dependencies, environment checks
+
+### 3. Use Work-On Skill
 
-Once validation is available:
-- Use `/validate` command if exists
-- Or use validation skill if available
-- Or run detected scripts directly
+Once available:
+- Follow the guidelines defined in the skill
+- Run any validation checks specified
+- Ensure code style compliance

package/commands/ttt:write-work-on-skill.md

@@ -0,0 +1,159 @@
+---
+name: ttt:write-work-on-skill
+description: Create a project-specific work-on skill with best practices, validation, and workflow conventions
+arguments:
+  - name: skill-name
+    description: Name for the skill (default: work-on)
+    required: false
+---
+
+# TTT Write Work-On Skill Command
+
+Create a project-specific work-on skill by analyzing the codebase.
+
+## Process
+
+### 1. Detect Project Type
+
+Check for project indicators:
+
+| File | Project Type |
+|------|--------------|
+| `package.json` | Node.js / Bun |
+| `Cargo.toml` | Rust |
+| `go.mod` | Go |
+| `pyproject.toml`, `requirements.txt` | Python |
+
+### 2. Find Existing Configurations
+
+Look for configurations to include in best practices:
+
+**Linting**: `biome.json`, `.eslintrc.*`, `ruff.toml`
+**Type Check**: `tsconfig.json`, `mypy.ini`
+**Testing**: `jest.config.*`, `vitest.config.*`, `pytest.ini`
+**Formatting**: `.prettierrc`, `.editorconfig`
+
+### 3. Check package.json Scripts
+
+If Node.js project:
+```bash
+cat package.json | jq '.scripts | keys[]' 2>/dev/null
+```
+
+Look for: `lint`, `type-check`, `test`, `check`, `validate`, `format`
+
+### 4. Create Skill File
+
+Create `.claude/skills/{{ $1 | default: "work-on" }}/SKILL.md`:
+
+```markdown
+---
+name: {{ $1 | default: "work-on" }}
+description: Project-specific best practices for starting and completing tasks
+---
+
+# Work-On Skill
+
+Best practices for working on tasks in this project.
+
+## Before Starting
+
+### 1. Validation Checks
+\`\`\`bash
+{{ lint-command }}
+{{ type-check-command }}
+\`\`\`
+
+### 2. Branch Naming
+- Feature: `feature/<issue-id>-<short-description>`
+- Bugfix: `fix/<issue-id>-<short-description>`
+- Refactor: `refactor/<issue-id>-<short-description>`
+
+### 3. Environment Setup
+- Ensure dependencies are installed
+- Check for required environment variables
+
+## Code Style
+
+### Formatting
+{{ formatting-rules }}
+
+### Naming Conventions
+{{ naming-conventions }}
+
+### File Structure
+{{ file-structure-notes }}
+
+## Before Completing
+
+### 1. Run All Checks
+\`\`\`bash
+{{ combined-validation-command }}
+\`\`\`
+
+### 2. Commit Message Format
+\`\`\`
+<type>(<scope>): <description>
+
+<body>
+\`\`\`
+
+Types: feat, fix, refactor, docs, test, chore
+
+### 3. Self-Review Checklist
+- [ ] Code compiles without errors
+- [ ] All tests pass
+- [ ] No linting errors
+- [ ] Changes are focused on the task
+- [ ] No debug code or console.logs left
+```
+
+### 5. Output
+
+After creating:
+1. Show created file path
+2. Display detected configurations
+3. Suggest customizing the skill
+
+## Examples
+
+### Node.js with Biome + TypeScript
+```
+Detected: Node.js project with Biome + TypeScript
+
+Created: .claude/skills/work-on/SKILL.md
+
+Configurations found:
+  Lint: bun run lint
+  Type: bun run type-check
+  Format: bun run format
+  Test: bun run test
+
+The skill has been created with these defaults.
+Please review and customize for your team's conventions.
+```
+
+### Python with Ruff + mypy
+```
+Detected: Python project with Ruff + mypy
+
+Created: .claude/skills/work-on/SKILL.md
+
+Configurations found:
+  Lint: ruff check .
+  Type: mypy .
+  Format: ruff format .
+  Test: pytest
+
+The skill has been created with these defaults.
+Please review and customize for your team's conventions.
+```
+
+## Customization Tips
+
+After creating the skill, consider adding:
+
+1. **Team-specific conventions**: PR review process, documentation requirements
+2. **Project-specific checks**: Security scanning, dependency audits
+3. **Environment setup**: Database migrations, API key checks
+4. **Testing requirements**: Coverage thresholds, required test types

package/dist/scripts/lib/done/linear-handler.js

@@ -120,8 +120,8 @@ export async function handleLinearCompletion(context) {
         default:
             result = await handleSimpleCompletion(context);
     }
-    // Add comment with commit info
-    if (commit) {
+    // Add comment with commit info (only if promptMessage provided)
+    if (commit && promptMessage) {
         const commentBody = buildCompletionComment(commit, promptMessage);
         const commentSuccess = await addComment(task.linearId, commentBody);
         if (commentSuccess) {

package/dist/scripts/lib/done/trello-handler.js

@@ -31,8 +31,8 @@ export async function handleTrelloCompletion(context) {
         if (result.success) {
             console.log(`Trello: ${task.id} → ${transitions.done}`);
         }
-        // Add comment with commit info
-        if (commit) {
+        // Add comment with commit info (only if promptMessage provided)
+        if (commit && promptMessage) {
             const commentBody = buildCompletionComment(commit, promptMessage);
             const commentResult = await adapter.addComment(sourceId, commentBody);
             if (commentResult.success) {

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "team-toon-tack",
-	"version": "3.2.2",
+	"version": "3.2.4",
 	"description": "Linear & Trello task sync & management CLI with TOON format",
 	"type": "module",
 	"bin": {

package/skills/linear-task-manager/SKILL.md

@@ -211,20 +211,20 @@ The `ttt done` command behaves differently based on configured mode:
 - No cycle or parent issue support
 - Always uses simple completion mode
 
-## Project Validation
+## Work-On Skill
 
-Before starting or completing tasks, run project validation:
+Before starting tasks, check for project-specific work guidelines:
 
-1. **Check for validation command/skill**: Look for `/validate`, `/check` commands or validation skills
+1. **Check for work-on skill**: Look for `work-on`, `start-work` skills in `.claude/skills/`
 2. **Check package.json/Makefile**: Look for `lint`, `type-check`, `test` scripts
 
-If no validation exists, suggest running `/ttt:write-validate` to create a project-specific validation command.
+If no work-on skill exists, suggest running `/ttt:write-work-on-skill` to create project-specific best practices (includes validation, code style, workflow conventions).
 
 ## Best Practices
 
 ### DO
 - Always `ttt sync` before starting work
-- **Run project validation** before starting and before completing tasks
+- **Check for work-on skill** before starting tasks
 - Use `ttt work-on next` for auto-prioritization
 - Include meaningful messages with `ttt done -m "..."`
 - Check `ttt status` to verify state before commits
@@ -234,7 +234,7 @@ If no validation exists, suggest running `/ttt:write-validate` to create a proje
 - Don't manually edit `cycle.toon` - use CLI commands
 - Don't skip sync - local data may be stale
 - Don't forget to commit before `ttt done`
-- Don't mark tasks done without running validation
+- Don't mark tasks done without verification
 - Don't use `--all` on sync unless you need completed issues
 
 ## Troubleshooting

package/commands/ttt:write-validate.md

@@ -1,122 +0,0 @@
----
-name: ttt:write-validate
-description: Create a project validation command by detecting project type and existing lint/test configurations
-arguments:
-  - name: command-name
-    description: Name for the command (default: validate)
-    required: false
----
-
-# TTT Write-Validate Command
-
-Create a project-specific validation command by analyzing the codebase.
-
-## Process
-
-### 1. Detect Project Type
-
-Check for project indicators:
-
-| File | Project Type |
-|------|--------------|
-| `package.json` | Node.js / Bun |
-| `Cargo.toml` | Rust |
-| `go.mod` | Go |
-| `pyproject.toml`, `requirements.txt` | Python |
-
-### 2. Find Existing Configurations
-
-Look for static analysis configs:
-
-**Linting**: `biome.json`, `.eslintrc.*`, `ruff.toml`
-**Type Check**: `tsconfig.json`, `mypy.ini`
-**Testing**: `jest.config.*`, `vitest.config.*`, `pytest.ini`
-
-### 3. Check package.json Scripts
-
-If Node.js project:
-```bash
-cat package.json | jq '.scripts | keys[]' 2>/dev/null
-```
-
-Look for: `lint`, `type-check`, `test`, `check`, `validate`
-
-### 4. Create Command File
-
-Create `.claude/commands/{{ $1 | default: "validate" }}.md`:
-
-```markdown
----
-name: {{ $1 | default: "validate" }}
-description: Run project validation (lint, type-check, test)
----
-
-# Project Validation
-
-Run validation checks for this project.
-
-## Process
-
-### 1. Lint
-\`\`\`bash
-{{ lint-command }}
-\`\`\`
-
-### 2. Type Check
-\`\`\`bash
-{{ type-check-command }}
-\`\`\`
-
-### 3. Test (optional)
-\`\`\`bash
-{{ test-command }}
-\`\`\`
-
-## Quick Validate All
-
-\`\`\`bash
-{{ combined-command }}
-\`\`\`
-
-## On Failure
-
-1. Show error output
-2. Identify failing file(s) and line(s)
-3. Suggest fixes
-4. Re-run validation after fixes
-```
-
-### 5. Output
-
-After creating:
-1. Show created file path
-2. Display detected validation commands
-3. Suggest running `/{{ $1 | default: "validate" }}` to test
-
-## Examples
-
-### Node.js with Biome
-```
-Detected: Node.js project with Biome + TypeScript
-Created: .claude/commands/validate.md
-
-Commands:
-  Lint: bun run lint
-  Type: bun run type-check
-  Test: bun run test
-
-Try: /validate
-```
-
-### Python with Ruff
-```
-Detected: Python project with Ruff + mypy
-Created: .claude/commands/validate.md
-
-Commands:
-  Lint: ruff check .
-  Type: mypy .
-  Test: pytest
-
-Try: /validate
-```