@colin4k1024/tsp 2.5.2 → 2.5.3

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.
Files changed (36) hide show
  1. package/bin/lib/install-surface.js +5 -0
  2. package/hooks/harness-statusline.js +34 -11
  3. package/manifests/install-modules.json +98 -31
  4. package/package.json +2 -1
  5. package/scripts/__pycache__/__init__.cpython-311.pyc +0 -0
  6. package/scripts/__pycache__/build_platform_artifacts.cpython-311.pyc +0 -0
  7. package/scripts/__pycache__/install_platform.cpython-311.pyc +0 -0
  8. package/scripts/__pycache__/langfuse_trace.cpython-311.pyc +0 -0
  9. package/scripts/__pycache__/query_audit_logs.cpython-311.pyc +0 -0
  10. package/scripts/__pycache__/scan_leaked_keys.cpython-311.pyc +0 -0
  11. package/scripts/__pycache__/team_skills_platform.cpython-311.pyc +0 -0
  12. package/scripts/__pycache__/team_skills_platform.cpython-313.pyc +0 -0
  13. package/scripts/__pycache__/validate_library.cpython-311.pyc +0 -0
  14. package/scripts/__pycache__/validate_workflow_state.cpython-311.pyc +0 -0
  15. package/scripts/evolution/__pycache__/__init__.cpython-311.pyc +0 -0
  16. package/scripts/evolution/__pycache__/store.cpython-311.pyc +0 -0
  17. package/scripts/hooks/__pycache__/__init__.cpython-311.pyc +0 -0
  18. package/scripts/hooks/__pycache__/mcp_health_check.cpython-311.pyc +0 -0
  19. package/scripts/hooks/__pycache__/observe.cpython-311.pyc +0 -0
  20. package/scripts/hooks/__pycache__/session_end.cpython-311.pyc +0 -0
  21. package/scripts/hooks/__pycache__/session_start.cpython-311.pyc +0 -0
  22. package/scripts/hooks/suggest-compact.js +41 -0
  23. package/scripts/lib/__pycache__/audit_logger.cpython-311.pyc +0 -0
  24. package/scripts/lib/__pycache__/audit_query.cpython-311.pyc +0 -0
  25. package/scripts/lib/__pycache__/hook_contract.cpython-311.pyc +0 -0
  26. package/scripts/lib/__pycache__/memory_store.cpython-311.pyc +0 -0
  27. package/scripts/lib/__pycache__/utils.cpython-311.pyc +0 -0
  28. package/scripts/lib/install/request.js +1 -1
  29. package/scripts/lib/install-manifests.js +9 -1
  30. package/scripts/lib/install-targets/cangming-home.js +143 -0
  31. package/scripts/lib/install-targets/codewhale-home.js +187 -0
  32. package/scripts/lib/install-targets/registry.js +5 -1
  33. package/scripts/lib/transcript-usage.js +183 -0
  34. package/scripts/test-cangming-install.js +105 -0
  35. package/skills/goframe-v2/examples/practices/quick-demo/manifest/config/config.yaml +14 -14
  36. package/skills/repo-scan/SKILL.md +63 -63
@@ -1,22 +1,22 @@
1
- ---
2
- name: repo-scan
3
- description: Cross-stack source code asset audit — classifies every file, detects embedded third-party libraries, and delivers actionable four-level verdicts per module with interactive HTML reports.
4
- origin: community
5
- ---
6
-
7
- # repo-scan
8
-
9
- > Every ecosystem has its own dependency manager, but no tool looks across C++, Android, iOS, and Web to tell you: how much code is actually yours, what's third-party, and what's dead weight.
10
-
11
- ## When to Use
12
-
13
- - Taking over a large legacy codebase and need a structural overview
14
- - Before major refactoring — identify what's core, what's duplicate, what's dead
15
- - Auditing third-party dependencies embedded directly in source (not declared in package managers)
16
- - Preparing architecture decision records for monorepo reorganization
17
-
18
- ## Installation
19
-
1
+ ---
2
+ name: repo-scan
3
+ description: Cross-stack source code asset audit — classifies every file, detects embedded third-party libraries, and delivers actionable four-level verdicts per module with interactive HTML reports.
4
+ origin: community
5
+ ---
6
+
7
+ # repo-scan
8
+
9
+ > Every ecosystem has its own dependency manager, but no tool looks across C++, Android, iOS, and Web to tell you: how much code is actually yours, what's third-party, and what's dead weight.
10
+
11
+ ## When to Use
12
+
13
+ - Taking over a large legacy codebase and need a structural overview
14
+ - Before major refactoring — identify what's core, what's duplicate, what's dead
15
+ - Auditing third-party dependencies embedded directly in source (not declared in package managers)
16
+ - Preparing architecture decision records for monorepo reorganization
17
+
18
+ ## Installation
19
+
20
20
  ```bash
21
21
  # Fetch only the pinned commit for reproducibility
22
22
  mkdir -p ~/.claude/skills/repo-scan
@@ -27,52 +27,52 @@ git fetch --depth 1 origin 2742664
27
27
  git checkout --detach FETCH_HEAD
28
28
  cp -r . ~/.claude/skills/repo-scan
29
29
  ```
30
-
31
- > Review the source before installing any agent skill.
32
-
33
- ## Core Capabilities
34
-
35
- | Capability | Description |
36
- |---|---|
37
- | **Cross-stack scanning** | C/C++, Java/Android, iOS (OC/Swift), Web (TS/JS/Vue) in one pass |
38
- | **File classification** | Every file tagged as project code, third-party, or build artifact |
39
- | **Library detection** | 50+ known libraries (FFmpeg, Boost, OpenSSL…) with version extraction |
40
- | **Four-level verdicts** | Core Asset / Extract & Merge / Rebuild / Deprecate |
41
- | **HTML reports** | Interactive dark-theme pages with drill-down navigation |
42
- | **Monorepo support** | Hierarchical scanning with summary + sub-project reports |
43
-
44
- ## Analysis Depth Levels
45
-
46
- | Level | Files Read | Use Case |
47
- |---|---|---|
48
- | `fast` | 1-2 per module | Quick inventory of huge directories |
49
- | `standard` | 2-5 per module | Default audit with full dependency + architecture checks |
50
- | `deep` | 5-10 per module | Adds thread safety, memory management, API consistency |
51
- | `full` | All files | Pre-merge comprehensive review |
52
-
53
- ## How It Works
54
-
30
+
31
+ > Review the source before installing any agent skill.
32
+
33
+ ## Core Capabilities
34
+
35
+ | Capability | Description |
36
+ |---|---|
37
+ | **Cross-stack scanning** | C/C++, Java/Android, iOS (OC/Swift), Web (TS/JS/Vue) in one pass |
38
+ | **File classification** | Every file tagged as project code, third-party, or build artifact |
39
+ | **Library detection** | 50+ known libraries (FFmpeg, Boost, OpenSSL…) with version extraction |
40
+ | **Four-level verdicts** | Core Asset / Extract & Merge / Rebuild / Deprecate |
41
+ | **HTML reports** | Interactive dark-theme pages with drill-down navigation |
42
+ | **Monorepo support** | Hierarchical scanning with summary + sub-project reports |
43
+
44
+ ## Analysis Depth Levels
45
+
46
+ | Level | Files Read | Use Case |
47
+ |---|---|---|
48
+ | `fast` | 1-2 per module | Quick inventory of huge directories |
49
+ | `standard` | 2-5 per module | Default audit with full dependency + architecture checks |
50
+ | `deep` | 5-10 per module | Adds thread safety, memory management, API consistency |
51
+ | `full` | All files | Pre-merge comprehensive review |
52
+
53
+ ## How It Works
54
+
55
55
  1. **Classify the repo surface**: enumerate files, then tag each as project code, embedded third-party code, or build artifact.
56
56
  2. **Detect embedded libraries**: inspect directory names, headers, license files, and version markers to identify bundled dependencies and likely versions.
57
57
  3. **Score each module**: group files by module or subsystem, then assign one of the four verdicts based on ownership, duplication, and maintenance cost.
58
58
  4. **Highlight structural risks**: call out dead-weight artifacts, duplicated wrappers, outdated vendored code, and modules that should be extracted, rebuilt, or deprecated.
59
59
  5. **Produce the report**: return a concise summary plus the interactive HTML output with per-module drill-down so the audit can be reviewed asynchronously.
60
-
61
- ## Examples
62
-
63
- On a 50,000-file C++ monorepo:
64
- - Found FFmpeg 2.x (2015 vintage) still in production
65
- - Discovered the same SDK wrapper duplicated 3 times
66
- - Identified 636 MB of committed Debug/ipch/obj build artifacts
67
- - Classified: 3 MB project code vs 596 MB third-party
68
-
69
- ## Best Practices
70
-
71
- - Start with `standard` depth for first-time audits
72
- - Use `fast` for monorepos with 100+ modules to get a quick inventory
73
- - Run `deep` incrementally on modules flagged for refactoring
74
- - Review the cross-module analysis for duplicate detection across sub-projects
75
-
76
- ## Links
77
-
78
- - [GitHub Repository](https://github.com/haibindev/repo-scan)
60
+
61
+ ## Examples
62
+
63
+ On a 50,000-file C++ monorepo:
64
+ - Found FFmpeg 2.x (2015 vintage) still in production
65
+ - Discovered the same SDK wrapper duplicated 3 times
66
+ - Identified 636 MB of committed Debug/ipch/obj build artifacts
67
+ - Classified: 3 MB project code vs 596 MB third-party
68
+
69
+ ## Best Practices
70
+
71
+ - Start with `standard` depth for first-time audits
72
+ - Use `fast` for monorepos with 100+ modules to get a quick inventory
73
+ - Run `deep` incrementally on modules flagged for refactoring
74
+ - Review the cross-module analysis for duplicate detection across sub-projects
75
+
76
+ ## Links
77
+
78
+ - [GitHub Repository](https://github.com/haibindev/repo-scan)