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

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

@@ -1,250 +0,0 @@
----
-description: Bug fix workflow using dev-workflow MCP server
----
-
-# Bug Fix Workflow
-
-This workflow guides you through fixing bugs with the dev-workflow MCP server, ensuring proper testing and documentation.
-
-## When to Use
-
-- Fixing defects
--修复 unexpected behavior
-- Addressing user-reported issues
-- Fixing regressions
-
-## Workflow Steps
-
-### 1. Start the Task
-
-Begin by defining the bug:
-
-```
-Use start_task tool:
-- description: "Fix [bug description]"
-- type: "bugfix"
-```
-
-### 2. Reproduce and Fix
-
-1. **Reproduce** the bug locally
-2. **Identify** the root cause
-3. **Fix** the issue
-4. **Verify** the fix works
-
-Tips:
-- Document expected vs actual behavior
-- Take notes on the root cause
-- Test edge cases
-
-### 3. Mark as Fixed
-
-Once the fix is implemented:
-
-```
-Use mark_bug_fixed tool:
-- summary: "[Brief description of the fix]"
-```
-
-### 4. Create Regression Tests
-
-**Critical:** Write tests that would have caught this bug!
-
-Create regression tests:
-- Test the specific bug scenario
-- Test edge cases around the bug
-- Update existing tests if needed
-
-Then mark tests as created:
-
-```
-Use create_tests tool
-```
-
-### 5. Run Tests
-
-// turbo
-Execute your test suite:
-
-```bash
-npm test
-```
-
-Ensure the new regression tests pass:
-
-```
-Use run_tests tool:
-- passed: true
-- testCommand: "npm test"
-- details: "[Include regression test results]"
-```
-
-### 6. Document the Fix
-
-Update documentation:
-- **CHANGELOG** - Add bug fix entry
-- **Code comments** - Explain why the fix was necessary
-- **Issue tracker** - Reference issue number
-
-```
-Use create_documentation tool:
-- documentationType: "changelog"
-- summary: "[What you documented]"
-```
-
-### 7. Commit and Push
-
-Use conventional commit with `fix` type:
-
-```
-Use commit_and_push tool:
-- commitMessage: "fix([scope]): [description]"
-```
-
-Examples:
-- `fix(auth): prevent token expiration edge case`
-- `fix(ui): correct button alignment on mobile`
-
-### 8. Perform Release
-
-Bug fixes are patch releases:
-
-```
-Use perform_release tool:
-- command: "npm run release:patch"
-- notes: "v[X.Y.Z] - Bugfix for [issue]"
-```
-
-### 9. Complete Task
-
-```
-Use complete_task tool:
-- commitMessage: "fix([scope]): [description]"
-```
-
-## Example: Date Formatting Bug
-
-```
-1. start_task:
-     description: "Fix incorrect date format in transaction history"
-     type: "bugfix"
-
-2. [Reproduce bug, find issue in formatDate.js, implement fix]
-
-3. mark_bug_fixed:
-     summary: "Corrected date formatting to use ISO 8601 format"
-
-4. [Write regression test in formatDate.test.js]
-
-5. create_tests
-
-6. Run: npm test
-   
-7. run_tests:
-     passed: true
-     testCommand: "npm test -- utils/formatDate.test.js"
-     details: "2 new regression tests pass, all 45 tests pass"
-
-8. [Update CHANGELOG.md with fix entry]
-
-9. create_documentation:
-     documentationType: "changelog"
-     summary: "Added bug fix entry for date formatting issue"
-
-10. commit_and_push:
-      commitMessage: "fix(utils): correct date formatting to use ISO 8601"
-
-11. perform_release:
-      command: "npm run release:patch"
-      notes: "v1.2.1 - Date formatting hotfix"
-
-12. complete_task:
-      commitMessage: "fix(utils): correct date formatting to use ISO 8601"
-```
-
-## Handling Test Failures
-
-If tests fail during development:
-
-```
-run_tests:
-  passed: false
-  testCommand: "npm test"
-  details: "3 tests failed in auth module"
-```
-
-Response:
-```
-❌ Tests FAILED!
-🚫 Cannot proceed with failing tests
-```
-
-Fix the issues, then re-run:
-
-```
-run_tests:
-  passed: true
-  testCommand: "npm test"
-  details: "All tests now pass"
-```
-
-## Quick Reference
-
-```
-1. start_task → 2. Reproduce & fix → 3. mark_bug_fixed 
-→ 4. Write regression tests → 5. create_tests → 6. run_tests
-→ 7. Document → 8. create_documentation → 9. commit_and_push
-→ 10. perform_release → 11. complete_task
-```
-
-## Tips
-
-- **Regression tests** - Always write tests that would catch this bug
-- **Root cause** - Fix the underlying issue, not just symptoms
-- **Documentation** - Update CHANGELOG for user visibility
-- **Patch versions** - Bug fixes bump patch version (X.Y.Z)
-- **Conventional commits** - Use `fix` prefix
-
-## Hotfix Workflow
-
-For critical production bugs:
-
-```
-start_task:
-  description: "HOTFIX: [critical issue]"
-  type: "bugfix"
-
-[Implement minimal fix]
-
-mark_bug_fixed:
-  summary: "[Fix description]"
-
-[Focused regression test]
-
-create_tests
-
-run_tests:
-  passed: true
-  testCommand: "npm test -- [critical-path]"
-  details: "[Critical tests pass]"
-
-create_documentation:
-  documentationType: "changelog"
-  summary: "HOTFIX: [issue] - [fix]"
-
-commit_and_push:
-  commitMessage: "fix([scope])!: HOTFIX - [description]"
-
-perform_release:
-  command: "npm run release:patch"
-  notes: "v[X.Y.Z] - HOTFIX: [issue]"
-
-complete_task:
-  commitMessage: "fix([scope])!: HOTFIX - [description]"
-```
-
-## Need Help?
-
-- `get_workflow_status` - Check current phase
-- [EXAMPLES.md](../docs/antigravity/EXAMPLES.md) - Detailed examples
-- [TROUBLESHOOTING.md](../docs/antigravity/TROUBLESHOOTING.md) - Common issues

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

@@ -1,201 +0,0 @@
----
-description: Feature development workflow using dev-workflow MCP server
----
-
-# Feature Development Workflow
-
-This workflow guides you through developing a new feature with the dev-workflow MCP server.
-
-## When to Use
-
-- Adding new functionality
-- Building new components
-- Implementing new features
-
-## Workflow Steps
-
-### 1. Start the Task
-
-Begin by defining your feature:
-
-```
-Use start_task tool:
-- description: "Add [feature name] to [component/area]"
-- type: "feature"
-```
-
-The server confirms task start and moves you to the implementation phase.
-
-### 2. Implement the Feature
-
-Write your code as usual. The workflow doesn't interfere with your development process.
-
-Tips:
-- Keep commits atomic
-- Follow coding standards
-- Write clean, maintainable code
-
-### 3. Mark as Fixed
-
-Once implementation is complete:
-
-```
-Use mark_bug_fixed tool:
-- summary: "[Brief description of what was implemented]"
-```
-
-The server reminds you that tests are now mandatory.
-
-### 4. Create Tests
-
-Write comprehensive tests:
-- Unit tests for new functions/components
-- Integration tests for interactions
-- End-to-end tests for user flows (if applicable)
-
-Then mark tests as created:
-
-```
-Use create_tests tool
-(no parameters needed)
-```
-
-### 5. Run Tests
-
-// turbo
-Execute your test suite:
-
-```bash
-npm test
-```
-
-Record the results:
-
-```
-Use run_tests tool:
-- passed: true (or false if tests failed)
-- testCommand: "npm test"
-- details: "[Number of tests, coverage, etc.]"
-```
-
-**Important:** If tests fail, fix them before proceeding. The workflow blocks commits with failing tests.
-
-### 6. Create Documentation
-
-Update relevant documentation:
-- README with feature usage
-- Inline code comments
-- API documentation
-- CHANGELOG entry
-
-Then mark documentation as complete:
-
-```
-Use create_documentation tool:
-- documentationType: "README" (or "inline-comments", "API-docs", "changelog")
-- summary: "[What you documented]"
-```
-
-### 7. Commit and Push
-
-The MCP server automatically stages, commits, and pushes:
-
-```
-Use commit_and_push tool:
-- commitMessage: "feat([scope]): [description]"
-```
-
-Use conventional commit format:
-- `feat(auth): add social login`
-- `feat(ui): add dark mode toggle`
-
-The branch is auto-detected (main or master). To specify a branch:
-
-```
-Use commit_and_push tool:
-- commitMessage: "feat([scope]): [description]"
-- branch: "feature/your-branch"
-```
-
-### 8. Perform Release
-
-Record the release:
-
-```
-Use perform_release tool:
-- command: "npm run release:minor" (features are usually minor versions)
-- notes: "v[X.Y.Z] - [Feature highlights]"
-```
-
-### 9. Complete Task
-
-Mark the task as complete:
-
-```
-Use complete_task tool:
-- commitMessage: "feat([scope]): [description]" (same as commit message)
-```
-
-This resets the workflow for your next task.
-
-## Example: Adding Shopping Cart
-
-```
-1. start_task:
-     description: "Add shopping cart functionality"
-     type: "feature"
-
-2. [Implement cart component, add/remove logic, localStorage persistence]
-
-3. mark_bug_fixed:
-     summary: "Shopping cart with add/remove items and localStorage persistence"
-
-4. [Write cart tests: add item, remove item, update quantity, persistence]
-
-5. create_tests
-
-6. Run: npm test
-   
-7. run_tests:
-     passed: true
-     testCommand: "npm test"
-     details: "12 cart tests added, all pass. Coverage: 94%"
-
-8. [Update README with cart API, add inline comments]
-
-9. create_documentation:
-     documentationType: "README"
-     summary: "Added shopping cart API documentation and usage examples"
-
-10. commit_and_push:
-      commitMessage: "feat(cart): add shopping cart with localStorage persistence"
-
-11. perform_release:
-      command: "npm run release:minor"
-      notes: "v1.5.0 - Shopping cart feature"
-
-12. complete_task:
-      commitMessage: "feat(cart): add shopping cart with localStorage persistence"
-```
-
-## Quick Reference
-
-```
-1. start_task → 2. Code → 3. mark_bug_fixed → 4. Write tests
-→ 5. create_tests → 6. run_tests → 7. Document → 8. create_documentation
-→ 9. commit_and_push → 10. perform_release → 11. complete_task
-```
-
-## Tips
-
-- **Keep features small** - One complete feature per workflow
-- **Test thoroughly** - Don't skip tests 
-- **Document as you go** - Don't wait until the end
-- **Use conventional commits** - feat(scope): description
-- **Minor versions** - Features bump minor version (X.Y.0)
-
-## Need Help?
-
-- Check `get_workflow_status` to see where you are
-- Review [EXAMPLES.md](../docs/antigravity/EXAMPLES.md) for detailed examples
-- See [TROUBLESHOOTING.md](../docs/antigravity/TROUBLESHOOTING.md) for common issues