@programinglive/dev-workflow-mcp-server 1.8.1 → 1.10.0

package/.agent/workflows/dev-workflow-full-cycle.md

@@ -1,400 +0,0 @@
----
-description: Complete workflow demonstration showing all dev-workflow MCP server phases
----
-
-# Full Cycle Workflow Demonstration
-
-This workflow demonstrates a complete dev-workflow cycle from start to finish, showing all phases and tools.
-
-## Purpose
-
-This is a reference workflow showing:
-- All workflow phases
-- All MCP tools in action
-- Complete development cycle
-- Best practices
-
-## Scenario
-
-**Task:** Add user profile page with avatar upload
-
-## Complete Workflow
-
-### Phase 1: Task Start
-
-```
-Use start_task tool:
-- description: "Add user profile page with avatar upload and bio"
-- type: "feature"
-```
-
-**Response:**
-```
-✅ Task started
-📝 Task ID: task-20231122-001
-🔄 Phase: implementation
-Next: Implement the feature, then mark as fixed
-```
-
----
-
-### Phase 2: Implementation
-
-Code the feature:
-
-**Files created/modified:**
-- `components/ProfilePage.jsx`
-- `components/AvatarUpload.jsx`
-- `api/profile.js`
-- `styles/profile.css`
-
-**Implementation includes:**
-- Avatar upload with preview
-- Bio text editor
-- Form validation
-- API integration
-
----
-
-### Phase 3: Mark as Fixed
-
-```
-Use mark_bug_fixed tool:
-- summary: "User profile page with avatar upload, bio editor, and form validation"
-```
-
-**Response:**
-```
-✅ Feature marked as fixed
-⚠️  Reminder: Create tests now!
-🔄 Phase: testing
-Next: Create tests covering your changes
-```
-
----
-
-### Phase 4: Create Tests
-
-Write comprehensive tests:
-
-**Test files:**
-- `components/ProfilePage.test.jsx`
-- `components/AvatarUpload.test.jsx`
-- `api/profile.test.js`
-
-**Test coverage:**
-- Avatar upload flow
-- Image preview
-- Form validation
-- API calls
-- Error handling
-
-```
-Use create_tests tool
-```
-
-**Response:**
-```
-✅ Tests created
-📝 Phase: testing
-Next: Run tests and record results
-```
-
----
-
-### Phase 5: Run Tests
-
-// turbo
-Execute test suite:
-
-```bash
-npm test
-```
-
-**Output:**
-```
- PASS  components/ProfilePage.test.jsx
- PASS  components/AvatarUpload.test.jsx
- PASS  api/profile.test.js
-
-Tests: 18 passed, 18 total
-Coverage: 94.2%
-```
-
-Record results:
-
-```
-Use run_tests tool:
-- passed: true
-- testCommand: "npm test"
-- details: "18 new profile tests added. All tests pass. Coverage: 94.2%"
-```
-
-**Response:**
-```
-✅ Tests passed!
-🔄 Phase: documentation
-Next: Create or update documentation
-```
-
----
-
-### Phase 6: Create Documentation
-
-Update documentation:
-
-**Updated files:**
-- `README.md` - Added profile page usage section
-- `docs/API.md` - Documented profile endpoints
-- `CHANGELOG.md` - Added feature entry
-
-**Documentation includes:**
-- Component API reference
-- Usage examples
-- Screenshot of profile page
-- Migration notes if needed
-
-```
-Use create_documentation tool:
-- documentationType: "README"
-- summary: "Added profile page documentation with API reference, usage examples, and screenshots"
-```
-
-**Response:**
-```
-✅ Documentation created
-🔄 Phase: ready_to_commit
-Next: Check if ready to commit
-```
-
----
-
-### Phase 7: Ready Check
-
-```
-Use check_ready_to_commit tool
-```
-
-**Response:**
-```
-✅ All required steps completed
-✅ Fixed: Yes
-✅ Tests created: Yes
-✅ Tests passed: Yes
-✅ Documentation: Yes
-🎉 Ready to commit and push!
-```
-
----
-
-### Phase 8: Commit and Push
-
-```
-Use commit_and_push tool:
-- commitMessage: "feat(profile): add user profile page with avatar upload"
-```
-
-**Execution:**
-```bash
-git add .
-git commit -m "feat(profile): add user profile page with avatar upload"
-git push origin main
-```
-
-**Response:**
-```
-✅ Changes committed and pushed
-📦 Commit: feat(profile): add user profile page with avatar upload
-🌿 Branch: main
-🔄 Phase: release
-Next: Perform release
-```
-
----
-
-### Phase 9: Perform Release
-
-```
-Use perform_release tool:
-- command: "npm run release:minor"
-- notes: "v1.5.0 - User profile page feature"
-```
-
-**Execution:**
-```bash
-npm run release:minor
-# Creates tag v1.5.0
-# Updates CHANGELOG
-# Bumps version in package.json
-```
-
-**Response:**
-```
-✅ Release recorded
-📦 Release: npm run release:minor
-📝 Notes: v1.5.0 - User profile page feature
-🔄 Phase: complete
-Next: Complete the task
-```
-
----
-
-### Phase 10: Complete Task
-
-```
-Use complete_task tool:
-- commitMessage: "feat(profile): add user profile page with avatar upload"
-```
-
-**Response:**
-```
-✅ Task completed successfully!
-📋 Summary:
-   - Type: feature
-   - Description: Add user profile page with avatar upload and bio
-   - Tests: Passed (18 tests)
-   - Documentation: README
-   - Commit: feat(profile): add user profile page with avatar upload
-   - Release: npm run release:minor
-
-🎉 Workflow reset - ready for next task!
-📊 Task added to history
-```
-
----
-
-## View History
-
-Check completed tasks:
-
-```
-Use view_history tool:
-- limit: 5
-```
-
-**Response:**
-```
-📜 Recent Workflow History (5 tasks)
-
-1. feat(profile): add user profile page with avatar upload
-   Type: feature
-   Completed: 2023-11-22 14:30
-   Tests: Passed
-   Release: npm run release:minor
-
-2. fix(auth): correct token expiration handling
-   Type: bugfix
-   Completed: 2023-11-21 10:15
-   Tests: Passed
-   Release: npm run release:patch
-
-[... more history ...]
-```
-
----
-
-## Alternative: Quick Workflow with run_full_workflow
-
-For simple, well-defined tasks, use `run_full_workflow` to execute all steps at once:
-
-```
-Use run_full_workflow tool:
-  summary: "User profile page with avatar upload and bio editor"
-  testCommand: "npm test"
-  testsPassed: true
-  testDetails: "18 profile tests added, all pass, coverage 94.2%"
-  documentationType: "README"
-  documentationSummary: "Added profile page docs with API reference and examples"
-  commitMessage: "feat(profile): add user profile page with avatar upload"
-  releaseCommand: "npm run release:minor"
-  releaseNotes: "v1.5.0 - User profile page feature"
-```
-
-This executes all 9 steps in one call!
-
----
-
-## Workflow State Tracking
-
-Check status at any time:
-
-```
-Use get_workflow_status tool
-```
-
-**Example response (mid-workflow):**
-```
-📋 Current Workflow Status
-
-Task: Add user profile page with avatar upload and bio
-Type: feature
-Phase: documentation
-
-✅ Completed:
-   ✓ Task started
-   ✓ Feature fixed
-   ✓ Tests created
-   ✓ Tests passed
-
-⏳ Pending:
-   ○ Documentation
-   ○ Commit & push
-   ○ Release
-   ○ Complete
-
-Next step: Create documentation
-```
-
----
-
-## Complete Tool Summary
-
-Tools used in this workflow:
-
-1. **start_task** - Begin new task
-2. **mark_bug_fixed** - Mark implementation complete
-3. **create_tests** - Record test creation
-4. **run_tests** - Record test execution (blocks if failed)
-5. **create_documentation** - Record documentation
-6. **check_ready_to_commit** - Verify all steps complete
-7. **commit_and_push** - Automated git commit & push
-8. **perform_release** - Record release details
-9. **complete_task** - Finish and reset workflow
-10. **view_history** - See completed tasks
-11. **get_workflow_status** - Check current phase
-
-Optional tools:
-- **skip_tests** - Skip with justification (manual testing)
-- **drop_task** - Abandon task without completing
-- **force_complete_task** - Force complete (emergency use)
-- **rerun_workflow** - Restart current task
-- **run_full_workflow** - Execute all steps at once
-
----
-
-## Workflow Benefits
-
-This disciplined workflow ensures:
-
-- ✅ **Clear intent** - Every task starts with description
-- ✅ **Test coverage** - Tests are mandatory
-- ✅ **Quality gates** - Failing tests block commits
-- ✅ **Documentation** - Documentation is required
-- ✅ **Conventional commits** - Consistent commit messages
-- ✅ **Release tracking** - All releases are recorded
-- ✅ **Audit trail** - Complete history of all tasks
-
----
-
-## Next Steps
-
-- Use this as a reference for your own workflows
-- Customize for your project's needs
-- See other workflow templates:
-  - [dev-workflow-feature.md](./dev-workflow-feature.md)
-  - [dev-workflow-bugfix.md](./dev-workflow-bugfix.md)
-  - [dev-workflow-refactor.md](./dev-workflow-refactor.md)
-
----
-
-**Disciplined development leads to quality software!** 🚀

package/.agent/workflows/dev-workflow-refactor.md

@@ -1,238 +0,0 @@
----
-description: Refactoring workflow using dev-workflow MCP server
----
-
-# Refactoring Workflow
-
-This workflow guides you through refactoring code while maintaining functionality with the dev-workflow MCP server.
-
-## When to Use
-
-- Improving code structure
-- Removing code smells
-- Optimizing performance
-- Simplifying complex code
-
-## Workflow Steps
-
-### 1. Start the Task
-
-Define your refactoring goal:
-
-```
-Use start_task tool:
-- description: "Refactor [component/module] to [improvement goal]"
-- type: "refactor"
-```
-
-### 2. Ensure Test Coverage
-
-**Before refactoring**, verify you have good test coverage:
-
-```bash
-npm test -- --coverage
-```
-
-If coverage is low, write tests first to ensure refactoring doesn't break functionality.
-
-### 3. Refactor Code
-
-Make your improvements:
-- Extract methods/components
-- Simplify complex logic
-- Remove duplication
-- Optimize performance
-
-**Key principle:** Behavior should remain unchanged.
-
-### 4. Mark as Fixed
-
-```
-Use mark_bug_fixed tool:
-- summary: "[Brief description of refactoring]"
-```
-
-### 5. Update Tests
-
-Adapt tests to new structure if needed:
-- Update test structure for new organization
-- Ensure all existing tests still pass
-- Add tests for new abstractions
-
-```
-Use create_tests tool
-```
-
-### 6. Run Tests
-
-// turbo
-Verify all tests still pass:
-
-```bash
-npm test -- --coverage
-```
-
-Coverage should maintain or improve:
-
-```
-Use run_tests tool:
-- passed: true
-- testCommand: "npm test -- --coverage"
-- details: "[All tests pass, coverage maintained/improved]"
-```
-
-### 7. Document Changes
-
-Update documentation for new structure:
-- **Inline comments** - Document new abstractions
-- **Architecture docs** - Update diagrams if structure changed
-- **README** - Update examples if API changed
-
-```
-Use create_documentation tool:
-- documentationType: "inline-comments"
-- summary: "[What you documented]"
-```
-
-### 8. Commit and Push
-
-Use `refactor` commit type:
-
-```
-Use commit_and_push tool:
-- commitMessage: "refactor([scope]): [description]"
-```
-
-Examples:
-- `refactor(auth): extract authentication logic to custom hooks`
-- `refactor(api): simplify error handling with interceptors`
-
-### 9. Perform Release
-
-Refactoring can be minor or patch:
-- **Minor** - Significant internal improvements
-- **Patch** - Small structural improvements
-
-```
-Use perform_release tool:
-- command: "npm run release:minor"
-- notes: "v[X.Y.Z] - Internal improvements (refactoring)"
-```
-
-### 10. Complete Task
-
-```
-Use complete_task tool:
-- commitMessage: "refactor([scope]): [description]"
-```
-
-## Example: Extract Custom Hooks
-
-```
-1. start_task:
-     description: "Refactor authentication logic into reusable custom hooks"
-     type: "refactor"
-
-2. [Check test coverage: 89%]
-
-3. [Extract useAuth and usePermissions hooks from components]
-
-4. mark_bug_fixed:
-     summary: "Extracted useAuth and usePermissions hooks from component logic"
-
-5. [Update component tests to work with hooks]
-
-6. create_tests
-
-7. Run: npm test -- --coverage
-   
-8. run_tests:
-     passed: true
-     testCommand: "npm test -- --coverage"
-     details: "All 145 tests pass, coverage improved from 89% to 92%"
-
-9. [Add JSDoc comments to hooks, update README with hook examples]
-
-10. create_documentation:
-       documentationType: "inline-comments"
-       summary: "Added JSDoc for custom hooks and usage examples in README"
-
-11. commit_and_push:
-       commitMessage: "refactor(auth): extract authentication logic to custom hooks"
-
-12. perform_release:
-       command: "npm run release:minor"
-       notes: "v1.6.0 - Authentication refactoring (improved maintainability)"
-
-13. complete_task:
-       commitMessage: "refactor(auth): extract authentication logic to custom hooks"
-```
-
-## Refactoring Checklist
-
-Before starting:
-- [ ] Current code has adequate test coverage
-- [ ] Tests are passing
-- [ ] Refactoring goal is clear
-
-During refactoring:
-- [ ] Run tests frequently
-- [ ] Make small, incremental changes
-- [ ] Commit logical chunks if needed locally
-
-After refactoring:
-- [ ] All tests pass
-- [ ] Coverage maintained or improved
-- [ ] Code is simpler/cleaner
-- [ ] Documentation updated
-
-## Quick Reference
-
-```
-1. start_task → 2. Verify tests → 3. Refactor → 4. mark_bug_fixed
-→ 5. Update tests → 6. create_tests → 7. run_tests
-→ 8. Document → 9. create_documentation → 10. commit_and_push
-→ 11. perform_release → 12. complete_task
-```
-
-## Tips
-
-- **Test first** - Ensure good coverage before refactoring
-- **Small changes** - Refactor incrementally
-- **Keep tests passing** - Run tests frequently
-- **No behavior changes** - Functionality stays the same
-- **Document abstractions** - Explain new patterns
-- **Coverage goal** - Maintain or improve test coverage
-
-## Common Refactoring Patterns
-
-### Extract Method
-```
-refactor(utils): extract validation logic to separate functions
-```
-
-### Extract Component
-```
-refactor(ui): extract UserCard component from UserList
-```
-
-### Simplify Logic
-```
-refactor(cart): simplify price calculation logic
-```
-
-### Remove Duplication
-```
-refactor(api): consolidate duplicate request handlers
-```
-
-### Optimize Performance
-```
-refactor(search): optimize search algorithm complexity
-```
-
-## Need Help?
-
-- `get_workflow_status` - Check current phase
-- [EXAMPLES.md](../docs/antigravity/EXAMPLES.md) - Refactoring examples
-- [TROUBLESHOOTING.md](../docs/antigravity/TROUBLESHOOTING.md) - Common issues

package/.env.production

@@ -1,16 +0,0 @@
-# Production Environment Configuration for Docker Deployment
-# Copy this file to .env on your GCP instance
-
-# Database Configuration
-DEV_WORKFLOW_DB_TYPE=postgres
-DEV_WORKFLOW_DB_URL=postgres://devworkflow:YOUR_SECURE_PASSWORD_HERE@postgres:5432/devworkflow
-
-# PostgreSQL Password (used by docker-compose)
-# IMPORTANT: Change this to a secure password!
-POSTGRES_PASSWORD=YOUR_SECURE_PASSWORD_HERE
-
-# Optional: User ID for multi-user environments
-# DEV_WORKFLOW_USER_ID=your-username
-
-# Node Environment
-NODE_ENV=production

package/.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,34 +0,0 @@
----
-name: Bug Report
-about: Create a report to help us improve
-labels: bug
----
-
-## Describe the bug
-
-A clear and concise description of what the bug is.
-
-## To Reproduce
-
-Steps to reproduce the behavior:
-1. Go to '...'
-2. Run command '...'
-3. See error
-
-## Expected behavior
-
-A clear and concise description of what you expected to happen.
-
-## Screenshots / Logs
-
-If applicable, add screenshots or paste logs to help explain your problem.
-
-## Environment (please complete the following information):
-
-- OS: [e.g. macOS 14.5]
-- Node version: [e.g. 20.14.0]
-- npm version: [e.g. 10.8.2]
-
-## Additional context
-
-Add any other context about the problem here.

package/.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,25 +0,0 @@
----
-name: Feature Request
-about: Suggest an idea for this project
-labels: enhancement
----
-
-## Summary
-
-Describe the feature you'd like to see added.
-
-## Problem Statement
-
-What problem does this feature solve? Why is it important?
-
-## Proposed Solution
-
-Describe how you think this should work.
-
-## Alternatives Considered
-
-List any alternative solutions or features you've considered.
-
-## Additional context
-
-Add any other context, screenshots, or references about the feature request here.