general-coding-tools-mcp 1.0.8 → 1.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -1,8 +1,93 @@
1
- # MCP server
1
+ # General Coding Tools MCP
2
2
 
3
- This directory is the General Coding Tools MCP server. The [root README](../README.md) describes each skill and subagent and how to use the server.
3
+ MCP server that exposes **skills** and **subagents** for general coding workflows. Add it in Cursor, Claude Desktop, or any MCP client to get structured guidance for debugging, audits, planning, testing, docs, research, and verification.
4
4
 
5
- **Build:** `npm install && npm run build`
5
+ ## Setup
6
+
7
+ ```json
8
+ {
9
+ "mcpServers": {
10
+ "general-coding-tools-mcp": {
11
+ "command": "npx",
12
+ "args": ["-y", "general-coding-tools-mcp"]
13
+ }
14
+ }
15
+ }
16
+ ```
17
+
18
+ If you use a local clone instead of npm, point `command` to `node` and `args` to the path to `dist/index.js`.
19
+
20
+ ---
21
+
22
+ ## Skills
23
+
24
+ Structured processes and checklists the model can follow when you ask for that kind of help.
25
+
26
+ | Skill | What it does |
27
+ |-------|----------------|
28
+ | **systematic-debugging** | Guides root-cause analysis: reproduce, isolate, hypothesize, verify, fix. Use when something is broken or you're investigating a failure. |
29
+ | **correctness-audit** | Reviews code for correctness bugs, uncaught edge cases, and scalability issues (logic, null/async, types, resources, N+1, etc.). |
30
+ | **security-audit** | Audits against OWASP Top 10, API Security Top 10, CWE, GDPR, PCI-DSS. Cites standards and gives concrete fixes. |
31
+ | **best-practices-audit** | Audits against DRY, SOLID, KISS, YAGNI, Clean Code, and similar. |
32
+ | **feature-planning** | Plans a feature before coding: context, requirements, design (behavior, data, API, state), implementation steps, and quality/risk. |
33
+ | **test-deno** | Writes and reviews Deno integration tests for Supabase Edge Functions. Enforces sanitizers, assertions, mocking, HTTP testing, and environment isolation. |
34
+ | **test-frontend** | Writes and reviews React tests using Vitest and React Testing Library. Enforces RTL query priority, Vitest mocking, Zustand/TanStack Query testing. |
35
+ | **test-pgtap** | Writes and reviews pgTAP database tests for Supabase SQL migrations. Enforces transaction isolation, plan counts, assertion selection, RLS verification. |
36
+ | **migration-audit** | Audits PL/pgSQL migration files for NULL traps, race conditions (TOCTOU), missing constraints, error handling gaps, JSONB pitfalls, volatility mismarks, financial safety, and security (SECURITY DEFINER, search_path, REVOKE/GRANT). |
37
+ | **ui-audit** | Audits React/Tailwind UI for WCAG 2.2 accessibility violations and structural anti-patterns (component duplication, separation of concerns). |
38
+
39
+ Each skill can be fetched with the `get_skill` tool or applied with the `apply_skill` tool (pass your request as `message_to_skill`).
40
+
41
+ ---
42
+
43
+ ## Subagents
44
+
45
+ Focused agents for specific tasks. Use `get_subagent` or `apply_subagent` (pass your request as `message_to_subagent`) to launch them.
46
+
47
+ | Subagent | What it does |
48
+ |----------|----------------|
49
+ | **deep-research** | Deep research and literature review. Uses web/Exa and AlphaXiv (when available). Synthesizes answers with pros/cons and sources. |
50
+ | **update-docs** | Keeps project documentation in sync with the code — architecture, setup, deploy, contributing, README, docstrings. |
51
+ | **verifier** | Checks that completed work matches what was claimed. Verifies deliverables exist and work, flags unstated changes. |
52
+
53
+ ---
54
+
55
+ ## Recommended Workflow
56
+
57
+ **For every new code addition:**
58
+
59
+ 1. **Plan first** — use `feature-planning` before writing any code
60
+ 2. **Audit correctness** — use `correctness-audit` on the implementation
61
+ 3. **Audit migrations** — use `migration-audit` on any SQL migration files (PL/pgSQL functions, DDL)
62
+ 4. **Audit security** — use `security-audit` if the change touches auth, payments, APIs, or user data
63
+ 5. **Audit best practices** — use `best-practices-audit` as a final pass
64
+
65
+ **Always get a second opinion:** have a second agent verify audit findings, OR dispatch the audit as a subagent and have the main agent review the results. This catches false positives and ensures nothing is missed.
66
+
67
+ ---
68
+
69
+ ## Tools
70
+
71
+ | Tool | Purpose |
72
+ |------|---------|
73
+ | `list_skills` | List all available skills |
74
+ | `list_subagents` | List all available subagents |
75
+ | `get_skill` | Fetch the full content of a skill |
76
+ | `get_subagent` | Fetch the full content of a subagent |
77
+ | `apply_skill` | Apply a skill to a user request |
78
+ | `apply_subagent` | Apply a subagent to a user request |
79
+
80
+ **Resources:** URIs like `general-coding-tools-mcp://skill/systematic-debugging` and `general-coding-tools-mcp://subagent/deep-research` for direct reads.
81
+
82
+ ---
83
+
84
+ ## Development
85
+
86
+ **Build:** `npm install && npm run build`
6
87
  **Run:** `npm start` or `node dist/index.js`
7
88
 
8
89
  Content lives in `skills/` and `subagents/` and is bundled into `dist/content.json` at build time.
90
+
91
+ ## License
92
+
93
+ MIT.