🗿 Makefile Rocks

"What if every command you've ever needed was just a make it away?"

curl -fsSL instll.sh/inem/rocks | bash

Non-destructive. Just adds two files to your current folder.

Welcome to a new paradigm in developer experience. This isn't just another tool—it's a movement toward effortless automation, collective knowledge sharing, and the elimination of context switching.

🎯 The Problem We're Solving

Picture this: You're deep in flow, building something amazing. Then you need to deploy. Or run tests. Or check the database. Suddenly you're:

• 🤔 Googling commands you've used 100 times before
• 📋 Copy-pasting from old projects or documentation
• 🔄 Context switching between your IDE, terminal, and browser
• 😤 Losing momentum while figuring out project-specific tooling

Every broken command is a broken flow state.

💡 The Solution: Collective Command Intelligence

What if the entire developer community shared a living, breathing repository of commands? What if failing fast became succeeding faster?

make deploy # ❌ Command not found
make it # ✨ Magic happens - command appears
make deploy # ✅ Now it works perfectly

This is make-driven development: where your tools adapt to you, not the other way around.

🚀 Quick Start: From Zero to Hero in 30 Seconds

# 1. Initialize the magic
curl -fsSL instll.sh/inem/rocks | bash
# 2. Try any command (it will fail)
make deploy
# 3. Watch the magic happen
make it
# 4. Now it works!
make deploy

That's it. You now have access to hundreds of battle-tested commands.

🏗️ Core Philosophy: The Three Pillars

1. Fail Fast, Succeed Faster

Every failed command is an opportunity. When make deploy doesn't exist, make it finds it, installs it, and you're back to building.

2. Collective Intelligence

Why should everyone figure out Docker deployment separately? One person writes make deploy, everyone benefits.

3. Zero Context Switching

Stay in your terminal. Stay in your flow. Let the tools adapt to your rhythm.

🎪 The Magic Behind the Curtain

Intelligent Command Discovery

make unknown-command
# Target 'unknown-command' not found. Try: make it
make it
# 💥 Failed command: make unknown-command# 📥 Fetching latest makefiles...# 🔍 Searching for 'unknown-command' command...# ✅ Found 'unknown-command' command in: make-docker# 📝 Adding to local Makefile...

Smart Module System

make rock git # Download git commands module
make rock rails # Download rails commands module
make rock docker # Download docker commands module

Commands are organized in rocks (modules) that you can pick and mix:

• 🔧 make-git: Git workflows (push, pull, branch, merge-to)
• 🚂 make-rails: Rails development (console, test, migrate)
• 🐳 make-docker: Container operations (build, run, deploy)
• 📦 make-instll: Package installation (instll user/package)
• 🔮 make-engine: The core system (auto-installed)

Intelligent Merging

When you run make rock git twice:

⚠️ make-git.mk exists, will add new commands in 9s...
Press Ctrl+C to cancel
🔍 Adding new commands...
➕ Adding command: branch-reset
➕ Adding command: uncommit
✅ Added 2 new commands to make-git.mk

Your customizations are preserved. Only new commands are added.

🧠 Learning Through Usage

This system teaches you by doing:

Universal Variables

Every project gets smart defaults:

make info
# EMAIL: your@email.com# GITHUB_USER: yourusername# GIT_REPO: yourusername/yourproject# REGISTRY: ghcr.io/yourusername/yourproject# IMAGE_NAME: yourusername-yourproject

Battle-Tested Patterns

# Git workflows
make develop # Switch to develop branch
make main # Switch to main branch
make push # Push current branch
make pull!# Force pull with rebase# Docker patterns
make build # Build with auto-detected registry
make run # Run with proper port mapping
make logs # Follow container logs# Rails conventions
make c # Rails console (no autocomplete)
make test# Run test suite
make migrate # Run pending migrations

Progressive Enhancement

Start simple, grow complex:

# Beginner: Just works
make deploy
# Intermediate: Understand the pattern
make build push deploy
# Advanced: Customize for your needs
REGISTRY=my-registry.com make deploy

🌟 Real-World Usage Stories

The Onboarding Experience

# New team member, first day
git clone company/awesome-project
cd awesome-project
# They try the obvious thing
make test# ❌ Target 'test' not found. Try: make it
make it
# ✅ Found 'test' command in: make-rails# 📝 Added to local Makefile
make test# 🎉 Tests are running!

Zero documentation needed. The system teaches itself.

The Context Switch Killer

# You're coding, need to deploy quickly
make deploy
# Works instantly - no googling, no copy-pasting# Need to check logs?
make logs
# Streaming immediately# Quick database check?
make console
# You're in, ready to debug

Flow state preserved. Momentum maintained.

The Knowledge Multiplier

# You discover a better way to do something
vim rocks/make-rails
# Add your improved command
git push
# Now everyone on every project benefits

Individual learning becomes collective wisdom.

🔧 Advanced Patterns

Project-Specific Customization

# Your local Makefileinclude make-*.mk
# Override defaultsREGISTRY = my-private-registry.com
# Add project-specific commandssetup:
make migrate
make seed
make testdeploy-staging:
ENVIRONMENT=staging make deploy

Smart Error Handling

make rock nonexistent
# ❌ Failed to download make-nonexistent (not found in rocks/)
make it!# Execute immediately after finding# 🚀 Executing command: deploy# [command runs immediately]

Integration with Modern Workflow

# Works with your existing tools
make build # Builds Docker image
make test# Runs your test suite
make deploy # Deploys to configured environment# Composes beautifully
make build test deploy

🌍 The Bigger Picture: Developer Experience Revolution

This isn't just about commands. It's about removing friction from the creative process:

Before Makefiles

Idea → Google → StackOverflow → Copy-paste → Debug → Modify → Finally works

After Makefiles

Idea → make it → Works

The Network Effect

• Individual: You save time and stay in flow
• Team: Shared knowledge, consistent workflows
• Community: Battle-tested patterns, continuous improvement
• Industry: Elevated baseline for developer experience

🚀 Installation & Getting Started

One-Line Setup

curl -fsSL instll.sh/inem/rocks | bash

This creates:

• ✅ Makefile with include make-*.mk
• ✅ make-engine.mk with core functionality
• ✅ Smart defaults for your project
• ✅ Automatic configuration of rocks.source

First Commands to Try

make info # See your project variables
make rock git # Add git commands
make rock rails # Add rails commands (if applicable)
make deploy # Let it fail, then...
make it # Watch the magic

🏗️ How It Works: Personal Rocks Collections

This repository isn't just a tool—it's a personal command collection system. Here's how it works:

The Fork-as-Personal-Base Concept

When you fork this repository, you're creating your own personal command library:

• 🎯 Customization: Add your own make-commands to rocks/
• 🏢 Team Sharing: Share your collection with your team
• 🔄 Evolution: Your commands evolve with your workflow
• 📦 Distribution: Others can use your commands via instll.sh/YOUR_USERNAME/rocks/init

How the System Determines Your Source

The system automatically determines where to fetch commands from using rocks.source:

1. First run: init.sh tries to detect your GitHub username via gh CLI
2. Auto-configuration: Sets git config --global rocks.source YOUR_USERNAME/rocks
3. Command execution: make it and make rock use this source
4. Manual override: You can always set it manually

🍴 Forking This Repository

Step-by-Step Guide

1. Fork on GitHub

   • Click "Fork" button on this repository
   • You now have github.com/YOUR_USERNAME/rocks

2. Clone Your Fork

   git clone https://github.com/YOUR_USERNAME/rocks
   cd rocks

3. Configure Your Source

   git config --global rocks.source YOUR_USERNAME/rocks

4. Customize Your Collection

   • Add your own make-files to rocks/
   • Modify existing commands
   • Create team-specific modules

5. Use in Projects

   # Others can now use your collection:
   curl -fsSL instll.sh/YOUR_USERNAME/rocks/init | bash

Example Workflow

# Alice forks and customizes
git clone https://github.com/alice/rocks
cd rocks
git config --global rocks.source alice/rocks
# Alice adds her custom commandsecho"deploy-staging:	docker build -t myapp:staging .	docker push myapp:staging">> rocks/make-deploy
# Alice commits and pushes
git add rocks/make-deploy
git commit -m "Add staging deployment"
git push
# Bob uses Alice's collection
curl -fsSL instll.sh/alice/rocks/init | bash
make deploy-staging # Now available!

🛠️ Creating Your Own Rocks

Adding New Commands

Simply add new .mk files to the rocks/ directory:

# Create a new moduleecho"deploy:	docker build -t \$(IMAGE_NAME) .	docker push \$(REGISTRY):\$(IMAGE_TAG)"> rocks/make-deploy
# Commit and push
git add rocks/make-deploy
git commit -m "Add deployment commands"
git push

Team Collaboration

• Shared Fork: Team maintains one fork with shared commands
• Individual Forks: Each developer has personal + team commands
• Hybrid: Use make rock alice/docker to get specific person's commands

Use Cases

• Personal Productivity: Your own shortcuts and workflows
• Project-Specific: Commands unique to your project
• Team Standards: Shared deployment, testing, and development commands
• Learning: Experiment with new tools and patterns

🤝 Contributing: Join the Movement

Adding Commands

# 1. Fork the repository# 2. Add commands to appropriate rocks/make-* file# 3. Submit PR# Example: Adding to rocks/make-git
troubleshoot:
git log --oneline -10
git status
git diff --stat

Creating New Modules

# Create rocks/make-kubernetes
build-manifests:
kustomize build .> manifests.yaml
deploy-k8s:
kubectl apply -f manifests.yaml

Philosophy Guidelines

• Commands should be memorable (make deploy, not make deploy-to-production-with-rollback)
• Embrace convention over configuration (smart defaults)
• Optimize for flow state (no prompts, no confirmations in common paths)
• Make it teachable (commands should be self-explanatory)

🔮 Future Vision

Imagine a world where:

• ✨ Every project has instant, discoverable commands
• 🧠 Collective intelligence eliminates repetitive learning
• 🌊 Flow state is the default developer experience
• 🚀 Automation is effortless and shareable

This is just the beginning. Make was created in 1976. It's time for an upgrade.

📚 Learn More

• 🏠 Live Demo - See it in action
• 🗿 Rock Collection - Browse available modules
• 💬 Discussions - Share patterns and ideas
• 🐛 Issues - Report bugs or request features

---

"The best tools are invisible. They get out of your way and let you create."

Join the revolution. Make commands, not barriers.

curl -fsSL instll.sh/inem/rocks | bash

---

😤 Built by annoyed developers — for annoyed developers.