npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

superdocs-app-cli

v1.0.2

Published

Edit markdown and text files with SuperDocs AI from your terminal.

Readme

superdocs-app-cli

Edit markdown and text files with SuperDocs from your terminal.

SuperDocs is an AI document editing service. This CLI sends a file, stdin, or Git diff to SuperDocs with your instruction, then writes the edited result back to disk or stdout.

30-Second Start

Install:

npm install -g superdocs-app-cli

Authenticate:

superdocs auth login
superdocs auth status

Edit a file:

superdocs edit ./proposal.md --prompt "Make this clearer and more concise"

Use stdin:

cat ./notes.md | superdocs edit --prompt "Turn these notes into a polished summary"

Use it with Git:

git diff | superdocs edit --prompt "Write release notes for these changes"

That is the main loop: provide text, describe the edit, get improved text back.

Common Examples

Edit a markdown file in place:

superdocs edit ./README.md --prompt "Fix typos and improve clarity"

Edit a text file:

superdocs edit ./meeting-notes.txt --prompt "Turn this into clean meeting minutes"

Write the result to a new file:

superdocs edit ./draft.md --output ./draft.edited.md --prompt "Make this more persuasive"

Preview the diff without changing the file:

superdocs edit ./proposal.md --dry-run --prompt "Tighten the language"

Pipe text in and print the result:

echo "hello wrold" | superdocs edit --prompt "Fix spelling"

Save stdin output to a file:

cat ./rough.md | superdocs edit --output ./clean.md --prompt "Clean this up"

Summarize staged Git changes:

git diff --staged | superdocs edit --prompt "Summarize this PR"

Review current Git changes:

git diff | superdocs edit --prompt "Review these changes and call out risks"

Include repository context in the request. --git adds the repository root, current branch, and changed-file list to the instruction sent to SuperDocs:

superdocs edit ./CHANGELOG.md --git --prompt "Summarise the work on this branch"

Authentication

Interactive login:

superdocs auth login

Non-interactive login:

superdocs auth login --api-key "$SUPERDOCS_API_KEY"

Check your setup:

superdocs auth status

Log out:

superdocs auth logout

Credentials are stored in a global credentials.json file:

  • Windows: %APPDATA%/SuperDocs/credentials.json
  • macOS: ~/Library/Application Support/SuperDocs/credentials.json
  • Linux: ~/.config/SuperDocs/credentials.json

The CLI also accepts SUPERDOCS_API_KEY or --api-key as temporary overrides.

The credentials file is restricted to your account: mode 0600 on macOS and Linux, and an explicit ACL on Windows. superdocs auth login warns if it cannot apply those permissions.

Configuration

Use superdocs config for non-secret defaults. These are stored separately from credentials.

superdocs config set default-model pro
superdocs config set response-mode compact
superdocs config set output-format markdown
superdocs config set timeout 600
superdocs config set verbose false

Read config:

superdocs config get default-model
superdocs config list

Supported keys:

| Key | Values | | --------------- | ----------------------------- | | default-model | core, turbo, pro, max | | response-mode | compact, full | | output-format | markdown, txt | | timeout | Positive seconds | | verbose | true, false |

Command-line flags override saved config.

Shell Completion

Install completion:

superdocs completion install bash
superdocs completion install zsh
superdocs completion install fish

Or print a completion script:

eval "$(superdocs completion bash)"
superdocs completion zsh > ~/.zsh/completions/_superdocs
superdocs completion fish > ~/.config/fish/completions/superdocs.fish

Command Reference

| Command | Description | | -------------------------------------- | ----------------------------------- | | superdocs auth login | Sign in to SuperDocs | | superdocs auth status | Check connection and sign-in status | | superdocs auth logout | Sign out of SuperDocs | | superdocs status | Alias for auth status | | superdocs edit <file> | Edit a markdown or text file | | superdocs config get <key> | Show one saved preference | | superdocs config set <key> <value> | Save one preference | | superdocs config list | Show saved preferences | | superdocs completion <shell> | Print a completion script | | superdocs completion install <shell> | Install completion for a shell |

Edit Options

| Flag | Description | | -------------------------- | ------------------------------------- | | -p, --prompt <prompt> | Editing instruction | | -o, --output <file> | Write output to another path | | --format <format> | Stdin format: markdown, txt | | --model-tier <tier> | core, turbo, pro, max | | --response-mode <mode> | compact, full | | --thinking-depth <depth> | fast, balanced, deep | | --approve <mode> | all (unattended) or ask | | --no-auto-continue | Stop instead of continuing a pause | | -d, --dry-run | Print a diff without writing | | -w, --watch | Re-edit when the file changes | | --git | Send Git context with the instruction | | --timeout-seconds <n> | Max wait time | | --json | Newline-delimited JSON output | | --verbose | Debug logs |

Output Streams

stdout carries only the payload; everything else goes to stderr. That makes redirection and piping safe:

# The edited document, and nothing else, lands in clean.md
cat rough.md | superdocs edit --prompt "Clean this up" > clean.md

# A usable patch file; progress and status still print to the terminal
superdocs edit ./README.md --dry-run --prompt "Fix typos" > fixes.patch

With --json the CLI emits newline-delimited JSON - one compact object per line, each carrying a schema_version - so it can be consumed as a stream:

superdocs edit ./doc.md --prompt "Tighten this" --json | jq -c 'select(.ok != null)'

Approvals

By default superdocs edit applies changes unattended, which is what CI needs. To confirm before SuperDocs continues a large edit, run it interactively:

superdocs edit ./spec.md --approve ask --prompt "Restructure this document"

--no-auto-continue stops the edit at a pause instead of continuing. In a non-interactive terminal the paused job is cancelled and the command exits with an explanatory error rather than hanging or silently applying the change.

Development

npm install
npm run dev -- -- --help
npm run check
npm run lint
npm test
npm run build

License

MIT (c) SuperDocs