Find code by asking what it does. A CLI for coding agents that uses Jev to discover relevant files and source context.
TypeScript ai-sdkclaude-codeclicode-searchcodexcoding-agentscontext-retrievaldeveloper-toolsjevsemantic-searchtypescriptvercel-ai-gateway
Sync skills from dzhng/skills@e370d6a
David Zhang58fe9410474c
diff --git a/.agents/skills/audit-agents/assets/example-agents.md b/.agents/skills/audit-agents/assets/example-agents.mdindex 1d5e62e..6b7da71 100644--- a/.agents/skills/audit-agents/assets/example-agents.md+++ b/.agents/skills/audit-agents/assets/example-agents.md@@ -28,7 +28,7 @@ Write the test first. Before changing behaviour or fixing a bug, invoke <skill:A change that shouldn't alter behaviour (a refactor, a performance change) must leave the output unchanged, or be a named decision.-A failure you see is yours to fix, whether or not your change caused it. Don't hand back a codebase with failures in it; leave it better than you found it.+A failure you see is yours to fix, whether or not your change caused it. Fix an unrelated failure in its own commit.Never loosen a requirement to make a check pass. A narrow pass proves a narrow claim: say what you verified, what you assumed and what is unfinished.diff --git a/.agents/skills/refactor-clean/SKILL.md b/.agents/skills/refactor-clean/SKILL.mdindex be6fc70..6979f53 100644--- a/.agents/skills/refactor-clean/SKILL.md+++ b/.agents/skills/refactor-clean/SKILL.md@@ -1,6 +1,6 @@---name: refactor-clean-description: Refactor cleanly instead of layering sediment. Use for rename requests, stale or misleading names, changed scope, or when a change reveals duplicated concepts, local adapters, obsolete owners, redundant inputs or guards, compatibility wrappers, parallel abstractions, an over-large module that has accreted many responsibilities, or "just tack this on" pressure in any code area.+description: Refactor cleanly instead of layering sediment. Use for rename requests, stale or misleading names, legacy leftovers, changed scope, or when a change reveals duplicated concepts, local adapters, obsolete owners, redundant inputs or guards, compatibility wrappers, parallel abstractions, an over-large module that has accreted many responsibilities, or "just tack this on" pressure in any code area.---# Clean Refactoring@@ -24,8 +24,8 @@ module into the several owners it was hiding.state machine, data contract, renderer phase, API shape, UI state, or testoracle.3. Find every current owner and consumer. Treat wrappers, aliases, pass-local- constants, copied structs, and "temporary" branches as sediment until proven- otherwise.+ constants, copied structs, migration comments and "temporary" branches as+ sediment until proven otherwise.4. Run a deletion pass before relaxing checks or making inputs optional. For eachinput, flag, guard, fallback, and adapter in the affected path, ask what requiredbehavior breaks if it disappears. Trace its writers, transport, readers,