Skip to content

codavidgarcia/devkit

Repository files navigation

DevToolbox

Local development toolkit - 11 CLI tools you actually need, working together.

npm version npm downloads License: MIT

Installation

npm install -g @codavidgarcia/devtoolbox

What's included

Project Setup

  • init - Auto-setup projects (detects type, generates .gitignore, checks env, frees ports)

Environment & Ports

  • doctor - Check Node, npm, Git, internet, and detect blocked ports
  • ports - List all active ports
  • kill-port <port> - Kill process on any port

Network

  • online - Check internet connectivity (gateway, DNS, HTTP)
  • ip - Show local and public IP addresses

Security & Encoding

  • jwt <token> - Decode JWT tokens (works offline)
  • hash <text> - Generate hashes (md5, sha1, sha256, sha512)
  • encode/decode <text> - Base64 encoding

Project Files

  • gitignore <templates> - Generate .gitignore from templates

What makes this different

The commands talk to each other and learn from your usage:

# doctor detects issues and suggests fixes
$ devtoolbox doctor
✗ Port 3000 in use (node)
→ Run 'devtoolbox kill-port 3000' to fix

# kill-port learns from frequent usage
$ devtoolbox kill-port 3000
✓ Killed node (PID 1234) on port 3000
Tip: Port 3000 is frequently blocked
  → Run 'devtoolbox ports' to see all active ports

# ports shows which ones you use often
$ devtoolbox ports
Active Ports:
  3000  node     PID 1234  [COMMON]
  8080  nginx    PID 5678

[COMMON] = Frequently used in your projects

They share context (~/.devtoolbox/context.json) to remember patterns and suggest next steps.

Examples

Setup a new project:

devtoolbox init
# Detects project type, generates .gitignore, checks env, frees ports

Check your environment:

devtoolbox doctor

See all active ports:

devtoolbox ports
devtoolbox ports --common  # only common dev ports

Kill a process:

devtoolbox kill-port 3000

Decode a JWT:

devtoolbox jwt eyJhbGc...

Generate .gitignore:

devtoolbox gitignore node macos

Check connectivity:

devtoolbox online

Why?

I kept installing separate tools for these tasks. This bundles them and makes them work together through shared context (~/.devtoolbox/context.json).

Contributing

Pull requests welcome. See CONTRIBUTING.md.

License

MIT

About

Local development toolkit - CLI tools that talk to each other

Topics

Resources

License

Contributing

Stars

Watchers

Forks

Packages

No packages published