惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

J
Java Code Geeks
Google DeepMind News
Google DeepMind News
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
小众软件
小众软件
Blog — PlanetScale
Blog — PlanetScale
腾讯CDC
A
About on SuperTechFans
Vercel News
Vercel News
I
InfoQ
阮一峰的网络日志
阮一峰的网络日志
月光博客
月光博客
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
人人都是产品经理
人人都是产品经理
S
SegmentFault 最新的问题
V
Visual Studio Blog
T
Tailwind CSS Blog
大猫的无限游戏
大猫的无限游戏
M
MIT News - Artificial intelligence
博客园 - 【当耐特】
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
Microsoft Azure Blog
Microsoft Azure Blog
Apple Machine Learning Research
Apple Machine Learning Research
GbyAI
GbyAI
美团技术团队

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
I Built a Local Registry for My CLI Tools
Alucard · 2026-05-20 · via DEV Community

I Built a Local Registry for My CLI Tools

Over time, my development machine became full of small commands.

Some were global npm packages.

Some were pnpm tools.

Some were shell scripts.

Some were internal tools.

Some were small automation commands created for AI-assisted coding workflows.

The problem was not installation.

The problem was memory.

I kept asking myself:

  • What does this command do?
  • Where is the repository?
  • Who maintains it?
  • How do I use it?
  • Is it still active?
  • Why did I add it?

So I built a small CLI tool called tool-manage.

GitHub:
https://github.com/AlucPro/tool-manage

npm:
https://www.npmjs.com/package/@alucpro/tool-manage

What it does

tool-manage gives local commands a sqlite-backed registry.

It can:

  • register a command from PATH
  • save metadata
  • store help output
  • import JSON specs
  • generate starter JSON templates
  • update records
  • soft-delete old commands

Example

tm --add pnpm
tm --show pnpm
tm --update pnpm

tm --generate sync-notes
tm --add ./sync-notes.json

tm --remove old-script

Enter fullscreen mode Exit fullscreen mode

Why not just use npm global list?

Because I do not only want to know what is installed.

I want to know what each command means in my workflow.

Package managers are good at installing things.
They are not designed to preserve the context around local commands, private scripts, or internal tools.

Why JSON specs?

Some tools do not expose good package metadata.

Some are just shell scripts.

Some are internal commands.

For those cases, tool-manage can generate a starter JSON file:

tm --generate sync-notes

Enter fullscreen mode Exit fullscreen mode

Then I can complete the description and import it later.

AI-assisted workflow

One use case I care about is AI-assisted coding.

When an AI assistant creates or explains a script, I can ask it to generate a tool-manage JSON spec for that command.

Then I can import it:

tm --add ./generated-command.json

Enter fullscreen mode Exit fullscreen mode

This makes small tools easier to remember and reuse.

What this tool is not

It is not a package manager.

It is not a version manager.

It does not replace npm, pnpm, nvm, volta, or mise.

It is just a memory layer for the commands already living on your machine.

Feedback welcome

I am still refining the workflow.

If you maintain many small scripts, internal tools, or local CLI commands, I would like to know how you currently manage them.