Sign In

dev-like

Package Overview
Dependencies
Maintainers
1
Versions
7
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

dev-like - npm Package Compare versions

Comparing version
0.3.0
to
0.3.1
+2
-2
bin/cli.mjs
#!/usr/bin/env node
// dev-like CLI — thin, deterministic plumbing. The agent skill does the smart work.
//
// v0.2: resolve + install from the registry. No telemetry, no postinstall, no network
// beyond raw.githubusercontent.com. See DESIGN.md §3.4.
// Resolve + install from the registry. No telemetry, no postinstall, no network
// beyond raw.githubusercontent.com.

@@ -7,0 +7,0 @@ import { parseArgs } from 'node:util';

{
"name": "dev-like",
"version": "0.3.0",
"version": "0.3.1",
"description": "Profile a shop's engineering culture from public sources and install develop-like-<target> agent skills. /dev-like Every",

@@ -36,9 +36,14 @@ "keywords": [

},
"workspaces": [
"docs",
"."
],
"scripts": {
"validate": "node scripts/validate.mjs",
"eval:paired": "node evals/paired/run.mjs",
"test": "node --test tests/*.test.mjs",
"test": "node --test tests/*.test.mjs && bun test tests/*.test.ts",
"prepublishOnly": "bun run validate && bun run test",
"version-changesets": "changeset version",
"publish-changesets": "changeset publish"
"publish-changesets": "changeset publish",
"alias-release": "bun run .github/scripts/alias-release.ts"
},

@@ -45,0 +50,0 @@ "devDependencies": {

# dev-like
[![npm](https://img.shields.io/npm/v/dev-like)](https://www.npmjs.com/package/dev-like)
[![CI](https://github.com/marcusrbrown/dev-like/actions/workflows/ci.yaml/badge.svg)](https://github.com/marcusrbrown/dev-like/actions/workflows/ci.yaml)
[![Link Check](https://github.com/marcusrbrown/dev-like/actions/workflows/link-check.yaml/badge.svg)](https://github.com/marcusrbrown/dev-like/actions/workflows/link-check.yaml)
> Steal the workflow, not the code. `/dev-like Every` and your agent develops like the

@@ -16,3 +20,3 @@ > shops you admire — with receipts.

```bash
# Universal (55 harnesses — Claude Code, Codex, Cursor, Copilot, Gemini CLI, ...)
# Universal — symlinks into every detected harness (Claude Code, Codex, Cursor, Copilot, ...)
npx skills add marcusrbrown/dev-like

@@ -24,4 +28,4 @@

# CLI (cached registry installs)
npx dev-like every
# CLI — install a cached profile's skill directly, no LLM needed
npx dev-like oxide
```

@@ -37,2 +41,18 @@

What changes? Same prompt, before and after — see the
[dry-run transcript](docs/demo/every-dryrun-2026-07-11.md): a generic senior-engineer review
becomes one that runs on the shop's actual operating model, every point traceable to a cited
source.
## Registry
| Slug | Kind | Consent tier | Skill |
|------|------|--------------|-------|
| [`every`](registry/every/) | org | self-published | [develop-like-every](registry/every/skill/develop-like-every/) |
| [`oxide`](registry/oxide/) | org | self-published | [develop-like-oxide](registry/oxide/skill/develop-like-oxide/) |
| [`theo`](registry/theo/) | person | stated | generated on demand |
Want a shop profiled? [Request it](https://github.com/marcusrbrown/dev-like/issues/new?template=profile-request.yml)
— or run `/dev-like <target>` and PR the result back.
## How it works

@@ -57,11 +77,15 @@

```bash
node scripts/validate.mjs # frontmatter + registry schema + index sync
node --test tests/
bun install
bun run validate # frontmatter + registry schema + index sync
bun run test # generator, CLI install, link-collection suites
```
See [DESIGN.md](DESIGN.md) for architecture and [CONTRIBUTING.md](CONTRIBUTING.md) for
adding registry profiles.
Plain node works too (`node scripts/validate.mjs`, `node --test tests/`) — the package has
zero runtime dependencies. Provenance links are re-checked weekly in CI; trigger evals and the
paired workflow eval live in [evals/](evals/).
See [CONTRIBUTING.md](CONTRIBUTING.md) for adding registry profiles.
## License
MIT

@@ -31,2 +31,2 @@ # Harness support

Per-harness compiled variants (Impeccable-style build step) are deliberately deferred until
telemetry shows demand — see DESIGN.md §4.
repeated user requests justify the added complexity.