cli.fail

Practice makes fewer incidents.

Eleven tiny incidents. Fewer future facepalms. Work through Git, npm, Docker, and shell mistakes at your own pace. Each scenario includes the reason behind the fix and a link to the official documentation. Practice rounds never change your daily score or local streak.

  1. 01

    The lockfile drift ↗

    Fix npm ci when intended dependency changes leave package.json and its lockfile out of sync.

    npm
  2. 02

    My changes vanished. Allegedly. ↗

    Understand why git diff is empty after staging, and inspect the patch ready for the next commit.

    Git
  3. 03

    The repository has left the chat. ↗

    Run Git against a repository in another directory without changing the current shell directory.

    Git
  4. 04

    A little less committed. ↗

    Unstage an accidentally added tracked file while keeping its edits on disk.

    Git
  5. 05

    Start was more of a suggestion. ↗

    Find the scripts a package actually defines after npm reports a missing start script.

    npm
  6. 06

    npm would like a word with your flag. ↗

    Pass a port flag through npm to a trusted local Vite development script.

    npm / Vite
  7. 07

    It exited. It has notes. ↗

    Inspect the last 50 log lines of an exited Docker Compose service without restarting it.

    Docker
  8. 08

    Indentation: the deployment strategy. ↗

    Validate Docker Compose configuration quietly before starting any containers.

    Docker
  9. 09

    One folder. Two arguments. ↗

    Quote a directory name containing spaces so Bash passes it as a single argument.

    Bash
  10. 10

    The text thinks it’s a flag. ↗

    Search for text beginning with a dash without treating that text as a grep option.

    GNU grep
  11. 11

    The shell already opened your mail. ↗

    Quote a find name pattern so the shell does not expand it before a recursive search.

    Bash / GNU find