tarangdeep-goel-by
- 20 skills
- 0 followers
- 15 hours ago last updated
- ▌ Warm · tarangdeep-goel-byRefresh project intelligence mid-session. Use when context feels stale, after switching branches, or after pulling changes.
- ▌ Stats · tarangdeep-goel-by bundleCost and usage observability for Claude Code sessions. Shows token usage, cost, and task metrics.
- ▌ Drawio · tarangdeep-goel-byAlways use when user asks to create, generate, draw, or design a diagram, flowchart, architecture diagram, ER diagram, sequence diagram, class diagram, network diagram, mockup, wireframe, or UI sketch, or mentions draw.io, drawio, drawoi, .drawio files, or diagram export to PNG/SVG/PDF.
- ▌ Memory · tarangdeep-goel-by bundleMemory corpus quality rollup. /memory health reports capture/approval/utilization/hook-health; /memory review proposes harness tweaks.
- ▌ Recall · tarangdeep-goel-by bundleSearch past Claude Code sessions, notes, and daily entries from the local vault. Use when the user says 'recall X', 'where were we', 'what did we do about X', 'remember working on X', 'look up past work on X', or wants to resume/catch up on prior sessions. Supports temporal, topic, graph, and analysis lens modes (retro, decisions, gaps, patterns, context).
- ▌ Reflect · tarangdeep-goel-by bundleReview and apply detected learnings from past sessions. Shows corrections, decisions, and discoveries detected by the learning loop.
- ▌ Done Gate · tarangdeep-goel-by bundleThe completion gate. Use RIGHT BEFORE claiming work is done/fixed/passing/working — run the proof command, read the output, only claim with fresh evidence. Distinct from /verify (which drives the app to confirm runtime behavior); done-gate gates the 'done' CLAIM itself. Fires last in the dev workflow, after the work + /code-review.
- ▌ Humanizer · tarangdeep-goel-by bundleRemove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, passive voice, negative parallelisms, and filler phrases.
- ▌ Vault Push · tarangdeep-goel-bySession-end persistence. Writes a per-session handoff and updates the project's PROJECT_LOG / README / PROJECT_ARC + research links so the next /recall can resume exactly where this session left off. Use at the end of every session, or when the user says /vault push.
- ▌ Task Triage · tarangdeep-goel-byUse when starting any new task, feature request, bugfix, enhancement, or refactoring to determine the appropriate level of process before doing any work.
- ▌ Vault Audit · tarangdeep-goel-byAudit the workflow and vault health. Use when the user says /vault audit to check if skills are being invoked and pushes are happening.
- ▌ Infra Health · tarangdeep-goel-by bundleTelemetry on the Claude Code harness itself — how hooks, skills, subagents, and daily jobs are performing. Use for: "infra health", "how is the infra performing", "hook telemetry", "which skills am I using", "are any hooks failing", "infra stats". All telemetry is LOCAL (stays on this machine under ~/vault/logs/). Distinct from /stats (which is cost/token usage).
- ▌ Review Merge · tarangdeep-goel-byReview a PR AND merge it if it passes — find the current branch's PR, assess it against a quality rubric (correctness/tests/clean/style/scope), then `gh pr merge --squash --delete-branch`. Use when the user says /review-merge, 'review and merge this PR', 'ship this PR', or asks to merge a pull request. Distinct from /review (review-only, no merge) — review-merge is the merge moment. Use `--no-merge` for review-only.
- ▌ Workflow Engine · tarangdeep-goel-by bundleUse at the start of every conversation and before every task, implementation, debugging session, or completion claim. This skill governs which other skills must be invoked. You MUST check this skill before doing any work.
- ▌ Debug Escalation · tarangdeep-goel-by bundleUse when encountering any bug, test failure, unexpected behavior, or error during development, before proposing or attempting fixes.
- ▌ Export · tarangdeep-goel-byExport internal vault notes as clean, shareable markdown files. Strips frontmatter, wikilinks, internal cross-references, and vault-only sections. Use when the user says "export", "share this spec", "clean up for sharing", "make this shareable", "external version", "strip internals", or needs to attach a spec to a ticket.
- ▌ Scribe · tarangdeep-goel-byCapture and refine text into polished Obsidian notes. Use when the user dumps raw text, quick thoughts, ideas, to-dos, or unstructured information. Triggers: "save this", "jot this down", "quick note", "write this", "note this", "capture this", or when the user pastes messy unformatted text that needs to become a proper note.
- ▌ Sorter · tarangdeep-goel-byTriage Daily captures and sort notes into their proper vault locations. Use when the user says "process daily", "triage", "sort my notes", "clean up daily", "file my notes", or when Daily folders have accumulated notes that need classification and filing.
- ▌ Compiler · tarangdeep-goel-bySynthesize raw supporting docs into structured research notes. Use when the user says "compile", "synthesize", "digest docs", "process supporting docs", "build wiki", "what do my docs say about", or when a project's supporting_docs/ has unprocessed files. Also triggered as an optional step during /wrap-up.
- ▌ Transcriber · tarangdeep-goel-byProcess meeting transcriptions and recordings into structured notes. Use when the user says "transcribe", "meeting notes from", "process this transcript", "summarize the call", "here's what we discussed", or pastes a raw meeting transcript.