All authors
Claude Skills by aahlijia
github.com/aahlijia8 skills0 installs3 views
- Dekko DaemonStart dekko's background daemon before a session that will run many bare `dekko` CLI commands via Bash (not the MCP tools) against a large or medium repo. Trigger when you're about to run several dekko CLI invocations in a row on the same repo — a long refactor loop, a batch of query/search/outline calls, or a hook/script context — and want to avoid each one reparsing map.json from scratch.Votes: 0GitHub stars: 5
- Dekko NotesRead and write dekko's symbol-anchored notes in any repo with a .dekko/ directory. Trigger every time you pull a symbol's context (query_symbol, get_context_pack, dekko query/context), right after a non-obvious change, and right after any rename/move/signature edit (to sweep orphaned notes). Notes are durable, committed annotations keyed by symbol id — they carry rationale grep/Read cannot show.Votes: 0GitHub stars: 5
- Dekko OrientUse dekko's tools instead of grep/Read whenever a repo has a .dekko/ directory — not just at session start. Trigger before any Grep/Glob/Read of a source file, before a `grep`/`rg`/`find`/`cat` in Bash, and on any "find/locate/understand this symbol," "what does this file/dir contain," "who calls this," "what will this change break," or "which tests should I run" impulse. dekko has already parsed and indexed the repo; grepping or reading whole files re-does work dekko already did, at higher t...Votes: 0GitHub stars: 5
- Dekko Review ContextGive a code-review or PR-description flow a structural head start before reading a diff line by line. Trigger when the user asks for a PR description, a pre-merge summary, or invokes a code-review flow (`/code-review`, `/review`, or an equivalent) against a diff in a repo with a `.dekko/` directory.Votes: 0GitHub stars: 5
- Dekko VerifySanity-check a suspiciously low or zero call-graph result from dekko (get_callers, get_callees, find_usages, impacted_tests, unused) before concluding "no callers" or "dead code," or a heritage/throws-provenance result (query supertypes, query subtypes, query throws) that labels something (external) when you expect it to be in-repo. Trigger whenever such a result looks surprising given the symbol's apparent importance, before deleting/renaming a symbol based on a zero-caller result, when the ...Votes: 0GitHub stars: 5
- Dekko DebugWork a stack trace, exception, or error report from dekko's map instead of reading each frame's file. Trigger when given a traceback, an exception type or message, a failing test's error, or a question like "why does X raise", "who handles this error", "how does control get from A to B", or "where is this env var read", in a repo with a `.dekko/` directory. dekko has the raise sites, catch clauses, call paths and getenv reads indexed; the trace names the frames, the map explains them.Votes: 0GitHub stars: 5
- Dekko DelegateBrief a subagent with dekko's map before dispatching it into a repo that has a `.dekko/` directory. Trigger before any Agent/Task tool call, Workflow `agent()`, teammate message, or scripted `claude -p` run that will explore, review, implement, or test in such a repo. A subagent starts with an empty context and no session-start orientation, so without a brief it re-explores from scratch with grep and whole-file reads; one budgeted dekko digest in the prompt replaces that, and telling it the t...Votes: 0GitHub stars: 5
- Dekko RefactorList every site a rename, move, or signature change must touch before editing, then prove nothing was missed after. Trigger when about to rename a function, method, class or type, rename or move a file or module, change a parameter list or return type, move a symbol between files, or remove a symbol, in a repo with a `.dekko/` directory; and again after those edits, before running tests. dekko's call graph has the exact call sites, type annotations, implementors and import lines, so this repl...Votes: 0GitHub stars: 5