npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@tdwhere/do-it-opencode

v0.16.0

Published

OpenCode adapter for do-it workflow hooks, skills, and agents

Readme

do-it OpenCode plugin

OpenCode adapter for the do-it workflow kernel: bootstrap guidance, advisory write-quality and verification bridges, and bundled skills.

Install

OpenCode discovers plugins via the "plugin" array in opencode.json (project) or ~/.config/opencode/opencode.json (global), or from .opencode/plugins/ / ~/.config/opencode/plugins/. Package names in the array are auto-installed by Bun at startup. See opencode.ai/docs/plugins.

npm package

Use this path after npm view @tdwhere/[email protected] version succeeds:

opencode plugin @tdwhere/do-it-opencode -g
# or add "@tdwhere/do-it-opencode" to the plugin array and let Bun install it

The package is published independently from the root CLI package. Its npm metadata requires Node ^22.22.2 || ^24.15.0 || >=26.0.0, matching the @opencode-ai/plugin dependency chain; OpenCode itself installs plugins with Bun.

Global vendored fallback

For checkout development or registry outages, install a vendored copy into OpenCode's own config home — do not point "plugin" at a do-it git checkout (that couples the live host to a mutable worktree).

From the do-it repo root:

npm run install:opencode-global

This builds the plugin, copies it to ~/.config/opencode/vendor/do-it-opencode, links it as @tdwhere/do-it-opencode via ~/.config/opencode/package.json, and sets:

{
  "$schema": "https://opencode.ai/config.json",
  "plugin": ["@tdwhere/do-it-opencode"],
  "permission": {
    "skill": "allow"
  }
}

Restart OpenCode after install. Override the config home with OPENCODE_CONFIG_DIR when needed.

Equivalent manual shape (same as Cursor's "real copy under the host home"):

npm run build:opencode-plugin
# copy plugins/do-it-opencode → ~/.config/opencode/vendor/do-it-opencode
# add package.json dependency: "@tdwhere/do-it-opencode": "file:./vendor/do-it-opencode"
# register "@tdwhere/do-it-opencode" in opencode.json (not a /path/to/clone/...)

opencode plugin <module> -g is the host CLI for npm modules. A tarball still sitting inside the do-it checkout will write a checkout path into opencode.json — move the tarball under the config home (or use npm run install:opencode-global) instead.

Dev checkout path (optional)

For plugin development only, an absolute path to plugins/do-it-opencode in a local clone works. Prefer the global vendor install for daily use.

See opencode.json.template for the package-name starter config.

Session state

Set OPENCODE_DATA (or rely on <project>/.opencode) so hook session state aligns with bash hooks under $OPENCODE_DATA/sessions/<session_id>/.

Tool mapping

| do-it intent | OpenCode surface | Plugin hook | | --- | --- | --- | | Classify prompt / tier | router.sh on each user message + bootstrap guidance | chat.message, experimental.chat.messages.transform | | Grill nudge | Heavy or explicit only; advisory | chat.messagegrill-prompt.sh | | Load skill | host skill tool + config.skills.paths | config | | Read / inspect | host read / file tools | — | | Edit source | edit / write / multiedit | no pre-edit plan gate | | Post-edit quality | same edit tools | tool.execute.afterwrite-quality-lint.sh (advisory) | | Done / ready claim | session completion | session.idleverification-gate.sh (soft reminder when evidence is available) | | Verify commands | terminal / exec | — (skill: do-it-verify) | | Skip hooks | user text / /do-it-skip | bootstrap documents tokens; bash hooks honor flags |

OpenCode tool ids are normalized to Claude-style names before invoking bash hooks (editEdit, writeWrite, multieditMultiEdit).

Hook bridge payload

Spawned hooks receive JSON on stdin:

{
  "session_id": "<sessionID>",
  "cwd": "<workspace directory>",
  "tool_name": "Edit",
  "file_path": "/path/to/file",
  "transcript_path": "",
  "tool_input": { "file_path": "..." }
}

Build

From the do-it repo root:

npm run build:opencode-plugin

Copies skills/do-it, dist/claude/agents, selected hooks/*.sh (+ lib/, data/), and compiles src/dist/.

Verify:

npm run test-opencode

Related