@programinglive/dev-workflow-mcp-server 1.0.7 → 1.0.8

package/LICENSE

@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2025 programinglive
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+MIT License
+
+Copyright (c) 2025 programinglive
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -1,66 +1,66 @@
-# Development Workflow MCP Server
-
-An MCP (Model Context Protocol) server that helps enforce development discipline and workflow best practices. This server acts as your coding conscience, reminding you to follow proper development workflows.
-
-## 🎯 Purpose
-
-This MCP server guides you through a disciplined development workflow:
-
-1. **Start Conscious** - Be clear about what you're coding
-2. **Fix/Implement** - Write your code
-3. **Create Tests** - Always test your changes
-4. **Run Tests** - Tests must pass (GREEN)
-5. **Document** - Update documentation
-6. **Commit & Push** - Let the server drive the git commands once verification passes
-7. **Release** - Record the release details before closing out the task
-
-## 🚀 Installation
-
-### 1. Install Dependencies
-
-```bash
-npm install
-```
-
-### 2. Configure in Windsurf/Claude Desktop
-
-Point your MCP client to the server entry point. Replace `<PROJECT_ROOT>` with the absolute path to this repository on your machine.
-
-#### macOS
-
-- **Windsurf** (`~/Library/Application Support/Windsurf/config.json`):
-
-```json
-{
-  "mcpServers": {
-    "dev-workflow": {
-      "command": "node",
-      "args": ["<PROJECT_ROOT>/index.js"]
-    }
-  }
-}
-```
-
-- **Claude Desktop** (`~/Library/Application Support/Claude/claude_desktop_config.json`):
-
-```json
-{
-  "mcpServers": {
-    "dev-workflow": {
-      "command": "node",
-      "args": ["<PROJECT_ROOT>/index.js"]
-    }
-  }
-}
-```
-
-#### Windows
-
-- **Windsurf** (`%APPDATA%\Windsurf\config.json`):
-
-```json
-{
-  "mcpServers": {
+# Development Workflow MCP Server
+
+An MCP (Model Context Protocol) server that helps enforce development discipline and workflow best practices. This server acts as your coding conscience, reminding you to follow proper development workflows.
+
+## 🎯 Purpose
+
+This MCP server guides you through a disciplined development workflow:
+
+1. **Start Conscious** - Be clear about what you're coding
+2. **Fix/Implement** - Write your code
+3. **Create Tests** - Always test your changes
+4. **Run Tests** - Tests must pass (GREEN)
+5. **Document** - Update documentation
+6. **Commit & Push** - Let the server drive the git commands once verification passes
+7. **Release** - Record the release details before closing out the task
+
+## 🚀 Installation
+
+### 1. Install Dependencies
+
+```bash
+npm install
+```
+
+### 2. Configure in Windsurf/Claude Desktop
+
+Point your MCP client to the server entry point. Replace `<PROJECT_ROOT>` with the absolute path to this repository on your machine.
+
+#### macOS
+
+- **Windsurf** (`~/Library/Application Support/Windsurf/config.json`):
+
+```json
+{
+  "mcpServers": {
+    "dev-workflow": {
+      "command": "node",
+      "args": ["<PROJECT_ROOT>/index.js"]
+    }
+  }
+}
+```
+
+- **Claude Desktop** (`~/Library/Application Support/Claude/claude_desktop_config.json`):
+
+```json
+{
+  "mcpServers": {
+    "dev-workflow": {
+      "command": "node",
+      "args": ["<PROJECT_ROOT>/index.js"]
+    }
+  }
+}
+```
+
+#### Windows
+
+- **Windsurf** (`%APPDATA%\Windsurf\config.json`):
+
+```json
+{
+  "mcpServers": {
     "dev-workflow": {
       "command": "node",
       "args": ["<PROJECT_ROOT>\\index.js"]
@@ -158,6 +158,12 @@ Confirm that you've created the necessary tests covering your change. Required b
 
 **Parameters:** _none_
 
+### `skip_tests`
+Record an explicit justification when automated tests aren't feasible. Marks testing as satisfied so you can proceed with documentation and verification, while flagging the task for manual QA.
+
+**Parameters:**
+- `reason` (string, required): Why automated tests were skipped
+
 ### `run_tests`
 Record test results. **NEVER commit if tests fail!** Only proceed if all tests are green.
 
@@ -204,6 +210,12 @@ Mark the task as complete after successful commit & push. Resets workflow for ne
 **Parameters:**
 - `commitMessage` (string, required): The commit message used
 
+### `drop_task`
+Abandon the current task without completing the workflow. Preserves an audit entry with context, then resets the state so you can start fresh.
+
+**Parameters:**
+- `reason` (string, optional): Additional detail about why the task was dropped
+
 ### `get_workflow_status`
 Get current workflow status and what needs to be done next.
 
@@ -249,31 +261,36 @@ Here's how you'd use this MCP server in a typical coding session:
    ```
    - If tests fail, the server will **block** you from proceeding!
 
-6. **Document:**
+7. **Document:**
    ```
    "Create documentation: type=README, summary='Added user profile section to docs'"
    ```
 
-7. **Check readiness:**
+8. **Check readiness:**
    ```
    "Check if I'm ready to commit"
    ```
 
-8. **Commit & Push:**
+9. **Commit & Push:**
    ```
    "Commit and push: commitMessage='feat: add user profile page with tests and docs'"
    ```
 
-9. **Record release:**
+10. **Record release:**
    ```
    "Record release: command='npm run release', notes='v1.2.3'"
    ```
 
-10. **Complete:**
+11. **Complete:**
    ```
    "Complete the task with commit message: 'feat: add user profile page'"
    ```
 
+12. **Drop task (optional):**
+   ```
+   "Drop task: reason='Switching to a different feature'"
+   ```
+
 ## 🎯 Key Features
 
 - **Enforces discipline**: Won't let you skip steps
@@ -294,7 +311,7 @@ Here's how you'd use this MCP server in a typical coding session:
 ## 💡 Tips
 
 1. **Always start with `start_task`** - This sets your intention
-2. **Never skip tests** - The server will remind you!
+2. **Never skip tests without justification** - Use `skip_tests` only when absolutely necessary and document the reason for manual QA
 3. **Use `get_workflow_status`** - Check where you are anytime
 4. **Review history** - Learn from your past tasks
 5. **Follow the prompts** - They contain best practices

package/SECURITY.md

@@ -1,20 +1,20 @@
-# Security Policy
-
-## Supported Versions
-
-We release patches for security vulnerabilities under new minor or patch versions. Always use the latest release.
-
-## Reporting a Vulnerability
-
-If you discover a vulnerability, please email `security@programinglive.com` with:
-
-- Description of the issue
-- Steps to reproduce
-- Potential impact
-- Suggested remediation (if known)
-
-We aim to acknowledge reports within 72 hours and will keep you informed as we work on a fix. Please do not disclose the vulnerability publicly until we have released an update.
-
-## Disclosure Policy
-
-Once a fix is available, we will publish a security advisory in the repository releases and notify contributors via the README.
+# Security Policy
+
+## Supported Versions
+
+We release patches for security vulnerabilities under new minor or patch versions. Always use the latest release.
+
+## Reporting a Vulnerability
+
+If you discover a vulnerability, please email `security@programinglive.com` with:
+
+- Description of the issue
+- Steps to reproduce
+- Potential impact
+- Suggested remediation (if known)
+
+We aim to acknowledge reports within 72 hours and will keep you informed as we work on a fix. Please do not disclose the vulnerability publicly until we have released an update.
+
+## Disclosure Policy
+
+Once a fix is available, we will publish a security advisory in the repository releases and notify contributors via the README.

package/commitlint.config.js

@@ -1,3 +1,3 @@
-export default {
-  extends: ["@commitlint/config-conventional"],
-};
+export default {
+  extends: ["@commitlint/config-conventional"],
+};