MCPcopy Index your code
hub / github.com/darrikonn/cheat

github.com/darrikonn/cheat @v1.1.1

Chat with this repo
repository ↗ · DeepWiki ↗ · release v1.1.1 ↗ · + Follow
44 symbols 161 edges 19 files 31 documented · 70% updated 3y agov1.1.1 · 2020-01-08★ 71
What it actually does AI analysis from the code graph — generated when you open this
loading…
README
<img src="https://user-images.githubusercontent.com/5694851/70360689-1fafa100-1877-11ea-8c2a-92386220ae63.png" alt="Icon"/>


cheat is a command line cheat manager, 

where you can create and manage your personal cheatsheet




gif







Installation

Pre-built packages for Windows, macOS, and Linux are found on the releases page.

Managed packages are in: * Homebrew (MacOs) bash brew tap darrikonn/formulae brew install darrikonn/formulae/cheat * Scoop (Windows) powerline scoop bucket add app https://github.com/darrikonn/cheat.git scoop install cheat * Other (Linux distros) bash curl -s https://raw.githubusercontent.com/darrikonn/cheat/master/install.sh | bash -s -- -b /usr/local/bin

Getting started

Run cheat --help to see possible commands.

Here are some to get you started: - Run cheat to list all your cheats.

  • Run cheat some.*regex to fetch cheats matching your regex.

  • Run cheat some.*regex add to add a new cheat.

API

Check out the api.

Configuring

The location of your cheat data and your configuration will depend on these environment variables (in this order): 1. CHEAT_HOME: determines where your cheatsheet.db and cheat.yaml file will live 2. XDG_CONFIG_HOME: a fallback if $CHEAT_HOME is not set 3. HOME: a fallback if $XDG_CONFIG_HOME is not set. If $HOME is used; all cheat files will be transformed to a dotfile, i.e.~/.cheatsheet.db and ~/.cheat.yaml.

Editor

When adding/editing a cheat, you'll be prompted to edit the cheat's description in your preferred editor. You can set your desired editor in the $CHEAT_HOME/cheat.yaml config file:

editor: nvim

If no editor config is specified, the editor will fallback to your EDITOR environment variable. If that can't be found, the default selected editor will be vi.

Tags

A neat way to search your cheats, is by describing them with tags.

my summary
tags: [awesome, golang]

my description

That way, you can simply search your cheats by tags, resulting in group like option for your cheats.

cheat 'tags: \[.*golang.*\]'

Core symbols most depended-on inside this repo

CheatException
called by 31
cli/exceptions/cheat_exception.go
Render
called by 16
cli/utils/render.go
ResolvePath
called by 6
cli/utils/filesystem.go
createUsageTemplate
called by 6
cli/cmd/root.go
Check
called by 5
cli/utils/root.go
GetCheatByName
called by 5
cli/db/query.go
FileExists
called by 4
cli/utils/filesystem.go
GetFirstLine
called by 3
cli/utils/strings.go

Shape

Function 37
Struct 4
Method 3

Languages

Go100%

Modules by API surface

cli/cmd/root.go7 symbols
cli/utils/filesystem.go5 symbols
cli/utils/root.go4 symbols
cli/exceptions/cheat_exception.go4 symbols
cli/db/mutate.go4 symbols
cli/utils/strings.go3 symbols
cli/exceptions/abort.go3 symbols
cli/utils/render.go2 symbols
cli/db/root.go2 symbols
cli/db/query.go2 symbols
cli/root.go1 symbols
cli/models/cheat.go1 symbols

For agents

$ claude mcp add cheat \
  -- python -m otcore.mcp_server <graph>

⬇ download graph artifact