context-tracker-mcp1.0 1.0.11 → 1.0.13
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.
|
@@ -0,0 +1,13 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Code organization and structure improvement
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
Organize and structure code for better maintainability. Focus on:
|
|
6
|
+
|
|
7
|
+
1. **File Organization** - Group related files together
|
|
8
|
+
2. **Naming Conventions** - Consistent naming across project
|
|
9
|
+
3. **Code Structure** - Clear separation of concerns
|
|
10
|
+
4. **Module Organization** - Proper exports and imports
|
|
11
|
+
5. **Folder Structure** - Logical directory hierarchy
|
|
12
|
+
|
|
13
|
+
Remove duplicate code, consolidate similar functionality, and ensure consistent patterns throughout the codebase.
|
|
@@ -0,0 +1,26 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Run and execute test suites
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
Execute test suites and analyze results. This workflow will:
|
|
6
|
+
|
|
7
|
+
1. **Run Tests** - Execute all test files or specific test suites
|
|
8
|
+
2. **Watch Mode** - Run tests in watch mode for continuous testing
|
|
9
|
+
3. **Coverage Report** - Generate and analyze test coverage
|
|
10
|
+
4. **CI Mode** - Run tests for continuous integration pipelines
|
|
11
|
+
5. **Debug Tests** - Run specific tests with debugging enabled
|
|
12
|
+
|
|
13
|
+
## Available Commands
|
|
14
|
+
|
|
15
|
+
- `npm test` - Run all tests
|
|
16
|
+
- `npm run test:watch` - Watch mode
|
|
17
|
+
- `npm run test:coverage` - Generate coverage report
|
|
18
|
+
- `npm run test:ci` - CI mode with reports
|
|
19
|
+
|
|
20
|
+
## Test Results Analysis
|
|
21
|
+
|
|
22
|
+
After running tests, analyze:
|
|
23
|
+
- Pass/fail rate
|
|
24
|
+
- Slow tests identification
|
|
25
|
+
- Flaky tests detection
|
|
26
|
+
- Coverage gaps
|
|
@@ -10,4 +10,4 @@ Generate comprehensive unit tests for the provided code. Include:
|
|
|
10
10
|
4. **Integration tests** - How components work together
|
|
11
11
|
|
|
12
12
|
Use the testing framework appropriate for the language (Jest for JS, pytest for Python, etc.)
|
|
13
|
-
Cover at least
|
|
13
|
+
Cover at least 85% of code paths.
|