feat: add ts-node-debugger skill for the codebase-aware TypeScript/Node.js debugging#18
Closed
KrishnaMuddi wants to merge 2 commits intomainfrom
Closed
feat: add ts-node-debugger skill for the codebase-aware TypeScript/Node.js debugging#18KrishnaMuddi wants to merge 2 commits intomainfrom
KrishnaMuddi wants to merge 2 commits intomainfrom
Conversation
…ypescript project
Skill Evaluator — Tier 1 Results✅ All checks passed
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ts-node-debugger
Codebase-aware TypeScript/Node.js debugging skill. On first use per repo,
the agent reads key project files and generates
.claude/project-context.md.Commit that file once — every teammate gets project-aware debugging from
their next
git pull, no per-developer setup needed.Category
💻 Coding & Engineering
Codebase aware skill where Fixes match the project's actual patterns - if the codebase uses
Result<T>, fixes useResult<T>. If it uses throws, fixes use throws. File and line references come from files the LLM actually read, never invented.What it covers
TS2xxxcodes)Token efficiency
Only
SKILL.mdis always in context.Three reference files loaded on demand:
references/discovery.md- first run per repo onlyreferences/env-checklist.md- env/config bugs onlyreferences/patterns.md- when writing fixesDemo video link
https://drive.google.com/file/d/1Yp3sFRq714h2ErVI0_zcwT2q_T-7xW3g/view?usp=sharing