adhi-jp

@adhi-jp source repo

17 skills
0 followers
6 hours ago last updated

▌
Skill Eval · adhi-jp bundle
Use when running, grading, aggregating, or reporting repository skill evals with skills/skill-eval/scripts/eval_runner.py, when verifying a with_skill/without_skill result before reporting it, or when deciding eval workspace placement, executor/grader separation, model passthrough, or metric capture for an eval run. Do not use for editing the eval suite schema or general skill creation.

0
installs
▌
Vibe Debug · adhi-jp bundle
Use when debugging or repairing existing features from rough agent-assisted coding reports, regressions, failed prior fixes, repeated "still broken" feedback, source-only debugging stalls, unobserved runtime state, tool or automation failures, environment-specific failures, runtime artifact mismatches, security boundary surprises, or fixes that feel wrong.

0
installs
▌
Vibe Coding · adhi-jp bundle
Use when the user explicitly invokes vibe-coding through a host-specific skill command, host-provided invocation signal, or direct instruction such as "use `vibe-coding`" for a coding workflow.

0
installs
▌
Vibe Commit · adhi-jp bundle
Use when the user asks to commit, stage, or "save" agent-assisted coding changes — including vague requests like "commit this", "commit please", "コミットして", or "/commit" — and the real work is deciding which files belong in the commit, excluding unwanted or generated files, splitting unrelated changes, or fixing a commit's file set, multi-line message transport, history (amend/rebase), or authorship trailers. This skill owns commit execution, message transport, and git safety.

0
installs
▌
Vibe Review · adhi-jp bundle
Use when the user asks for agent-assisted code review of a git diff, working tree, branch, base ref, git-backed plan or document change, or review/fix loop where scope triage, delegated reviewers, specification gaps, or cascade-safe fixes may matter.

0
installs
▌
Vibe Writing · adhi-jp bundle
Use when the primary task is writing, revising, reviewing, or critiquing agent-assisted coding development text, source-code comments or docstrings, README/docs, CHANGELOG/release notes, PR descriptions, UI copy, chat replies, progress updates, final summaries, or git commit messages, especially when text must be LLM-readable, meaning-preserving, format-bound, language-aware, or evidence-bound. Treat incidental wording inside another active workflow as auxiliary.

0
installs
▌
Skill Quality · adhi-jp bundle
Use when making evidence-driven quality decisions for a skill package or its evals from benchmark results, grader feedback, review comments, session-history patterns, trigger failures, or quality regressions; especially when deciding what to change, what not to change, how to update assertions, or whether to rerun skill evals.

0
installs
▌
Vibe Planning · adhi-jp bundle
Use when the user explicitly wants implementation planning before coding, asks to create or revise an implementation plan, supplies requirements with explicit approval evidence, a specification, acceptance criteria, or task list, or has inputs concrete enough to plan but not execute. Do not use for rough unapproved requirements drafting.

0
installs
▌
Vibe Brainstorm · adhi-jp bundle
Use when the user explicitly asks for vibe brainstorming, creative implementation ideas, implicit expected behavior, or convention checks, and when an implementation task is creative or convention-dependent. Do not use for obvious mechanical edits.

0
installs
▌
Vibe Orchestrate · adhi-jp bundle
Use when coordinating subagents for coding, research, repair, or review work where delegated workers may drift, stall, crash, duplicate, or edit a shared workspace and the coordinator must preserve scope, verification, and user-consent boundaries.

0
installs
▌
Vibe Plan Review · adhi-jp bundle
Use when the user asks to review, confirm, walk through, or pre-check a saved Markdown implementation plan before implementation; interactively reviews plan items one at a time and manages localized item-level decisions.

0
installs
▌
Vibe Code Research · adhi-jp bundle
Use when the user wants to understand, locate, trace, or assess existing code without changing it — questions like "how does X work", "where is Y implemented", "what would changing Z affect", architecture or data-flow mapping, dependency tracing, convention discovery, or pre-planning and pre-debugging evidence gathering. Do not use when a defect needs repair, a plan or spec artifact is requested, or an edit, commit, or diff review is the deliverable.

0
installs
▌
Vibe Goal Alignment · adhi-jp bundle
Use when the user asks to align, confirm, or correct the agent's understanding before action; when prior misinterpretation, risky ambiguity, release/version/commit intent, destructive effects, or goal disagreement could cause rework or damage.

0
installs
▌
Vibe Plan Execution · adhi-jp bundle
Use when the user asks to execute, implement, continue, or apply an existing implementation plan, specification, acceptance criteria, task plan, or prior planning output. Do not use for plan creation or coding requests with no concrete plan to bind.

0
installs
▌
Vibe Requirements Spec · adhi-jp bundle
Use when a user wants to draft, revise, save, approve, or explicitly explore requirements for a rough, ambiguous, contradictory, creative, non-technical, or underspecified coding goal before implementation planning or coding, including explicit chat-only/no-file requirements exploration.

0
installs
▌
Vibe Agent Instructions · adhi-jp bundle
Use when the user explicitly invokes this skill to create, refresh, or localize a repository's agent instruction files — AGENTS.md, CLAUDE.md, and personal local rules in AGENTS.override.md and CLAUDE.local.md — or to check that instruction-file policy against current best practice. Do not use for ordinary documentation edits, for implicit mentions of AGENTS.md, or for any request that does not explicitly invoke it.

0
installs
▌
Minecraft Modding Workbench · adhi-jp bundle
Use when building, debugging, porting, or inspecting Minecraft Java Edition mods for Fabric, NeoForge, or Architectury, including Mixins, access wideners, access transformers, mappings, registry/resource issues, NBT payloads, mod JAR inspection, remapping, version migration, dependency API source lookup, GameTest wiring, client screens, HUD rendering, or runtime logs. Also use as a side reference when another planning, execution, or review skill is active and the work depends on Minecraft API facts.

0
installs

17 published skills