debugsk 0.0.2 → 0.0.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "debugsk",
-  "version": "0.0.2",
+  "version": "0.0.3",
   "description": "Debug investigation CLI: server + Codex skill management for hypothesis-driven workflows.",
   "bin": {
     "debugsk": "dist/cli.js"
@@ -11,6 +11,15 @@
     "dist",
     "skills"
   ],
+  "scripts": {
+    "build": "tsup",
+    "dev": "tsup --watch",
+    "typecheck": "tsc --noEmit",
+    "lint": "eslint .",
+    "format": "prettier --check .",
+    "format:write": "prettier --write .",
+    "test": "vitest run"
+  },
   "engines": {
     "node": ">=18"
   },
@@ -33,14 +42,5 @@
     "tsx": "^4.19.2",
     "typescript": "^5.6.3",
     "vitest": "^3.0.4"
-  },
-  "scripts": {
-    "build": "tsup",
-    "dev": "tsup --watch",
-    "typecheck": "tsc --noEmit",
-    "lint": "eslint .",
-    "format": "prettier --check .",
-    "format:write": "prettier --write .",
-    "test": "vitest run"
   }
-}
+}

package/skills/code-debug-skill/SKILL.md

@@ -14,7 +14,9 @@ description: Standardized, hypothesis-driven debug investigation workflow for un
   - required instrumentation (what to measure or log).
 - Prefer decisive signals over narratives. Do not ask for reproduction without a plan to capture evidence.
 - Narrow with comparisons (fail vs pass) and a binary-search style approach when possible.
-- Make the smallest change that increases observability. Avoid speculative fixes.
+- Add debug instrumentation generously to capture decisive signals in a single reproduction run.
+  - Assume each reproduction is costly; instrument enough to narrow root cause without requiring additional runs.
+- Never fix code speculatively. Confirm root cause with evidence before any production code change.
 
 ## Tool selection (what to use)
 - Primary tool for new instrumentation: local HTTP ingest logger.
@@ -66,6 +68,7 @@ description: Standardized, hypothesis-driven debug investigation workflow for un
 ## User interaction rules
 - When reproduction is required, provide exact steps, expected signals, and required artifacts.
 - If reproduction is not possible, pivot to existing logs, metrics, traces, config diffs, or safe probes.
+- After embedding debug code, explicitly ask the user whether to use a tunneling setup (e.g., ngrok/Cloudflare Tunnel) for external or mobile access; do not assume.
 
 ## Cleanup policy
 - When the user confirms the issue is resolved or the investigation is closed, stop the debug server and delete all investigation logs (e.g., `.logs/`).
@@ -73,7 +76,7 @@ description: Standardized, hypothesis-driven debug investigation workflow for un
 - If deletion could affect unrelated files, confirm the exact paths before removal.
 
 ## Reporting format
-Use the template in `assets/report-template.md`.
+Use the template in `assets/report-template.md`. Headings are bilingual (English / Japanese); write content in the user's language.
 
 ## References
 - Use `references/logging-schema.md` when adding or validating instrumentation.

package/skills/code-debug-skill/assets/report-template.md

@@ -1,19 +1,19 @@
-# Investigation Summary
-- Impact:
-- Confidence:
+# Investigation Summary / 調査概要
+- Impact / 影響:
+- Confidence / 確信度:
 
-# Facts (observed)
+# Facts (observed) / 事実（観測結果）
 
-# Hypotheses
+# Hypotheses / 仮説
 
-# Instrumentation Plan
+# Instrumentation Plan / 計装計画
 
-# Reproduction Checklist
+# Reproduction Checklist / 再現手順
 
-# Findings (log-backed)
+# Findings (log-backed) / 発見事項（ログ根拠あり）
 
-# Root Cause (if confirmed)
+# Root Cause (if confirmed) / 根本原因（確定時）
 
-# Next Actions (if not confirmed)
+# Next Actions (if not confirmed) / 次のアクション（未確定時）
 
-# Fix Plan + Tests
+# Fix Plan + Tests / 修正計画 + テスト

package/LICENSE

@@ -1,21 +0,0 @@
-MIT License
-
-Copyright (c) 2025 OSS Contributors
-
-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.