Skip to content
Hush

AI Prompts

These prompts are designed for the current Hush model:

  • .hush/manifest.encrypted
  • .hush/files/**.encrypted
  • hush bootstrap
  • hush config
  • hush migrate --from v2 [--cleanup] only when the repo is still legacy

Quick start prompt

I want to use Hush for AI-native secrets management in this project. Please:


1. Check if sops and age are installed
2. Install @chriscode/hush as a dev dependency
3. Run `npx @chriscode/hush bootstrap`
4. Show me the resulting `.hush/manifest.encrypted` and `.hush/files/**.encrypted` layout with `npx @chriscode/hush config show`
5. Help me add the first secrets with `npx @chriscode/hush set`
6. Verify with `npx @chriscode/hush inspect` and `npx @chriscode/hush config active-identity`


IMPORTANT:
- Do not teach or create `hush.yaml`
- Do not use `hush init` or `hush encrypt`
- If this repo is still legacy v2, stop bootstrapping and use `npx @chriscode/hush migrate --from v2` instead

Nested repo bootstrap prompt

This git repository is nested inside a parent that has a Hush `.hush/` repo. I need a child-local Hush repository for this project. Please:


1. Run `npx @chriscode/hush bootstrap --new-repo --yes`
2. Run `npx @chriscode/hush doctor` to verify the key resolution
3. Show the resulting layout with `npx @chriscode/hush config show`


Do NOT join the parent `.hush/` repository.

Diagnostic prompt

Something is wrong with Hush key resolution or root discovery in this project. Please:


1. Run `npx @chriscode/hush doctor` to diagnose the issue
2. If the doctor reports key mismatch, run `npx @chriscode/hush keys setup`
3. Verify with `npx @chriscode/hush inspect`


If bootstrap fails, try `npx @chriscode/hush bootstrap --new-repo --yes` to force a child-local repository.

Legacy migration prompt

This repository still uses legacy Hush v2 files. Please:


1. Inventory the legacy state
2. Run `npx @chriscode/hush migrate --from v2`
3. Verify the new `.hush/` repository with `npx @chriscode/hush config show` and `npx @chriscode/hush inspect`
4. After validation, run `npx @chriscode/hush migrate --from v2 --cleanup`


Do not keep teaching `hush.yaml`, `hush init`, or `hush encrypt` as the current model after migration.

Install the Claude Code skill

Install the Hush skill for this project and verify that it teaches the current v3 workflow:


- `hush bootstrap`
- `hush config`
- `hush set`
- `hush inspect`
- `hush run -- <command>`
- `hush migrate --from v2` only for legacy repos

Common task prompts

Check what secrets exist

Use Hush to show me what secrets are configured in this project.
Use `hush inspect` and `hush config show`.
Do not read plaintext env files directly.

Add a new secret

Help me add a new secret called [SECRET_NAME].
Use `hush set` and then verify with `hush inspect`.
Do not create or edit plaintext env files.

Inspect the current repository state

Show me the current Hush v3 repository state.
Use:
- `hush config show`
- `hush config active-identity`
- `hush config show files`

Configure a monorepo target

Help me inspect and update my Hush v3 monorepo setup.
Use `hush config` to show the current targets, files, and readers.
Keep the canonical state in `.hush/manifest.encrypted` and `.hush/files/**.encrypted`.

Cursor integration

Add this to your .cursorrules file:

## Secrets Management


This project uses Hush v3.


Current model:
- `.hush/manifest.encrypted`
- `.hush/files/**.encrypted`


Use these commands:
- `npx @chriscode/hush config show`
- `npx @chriscode/hush inspect`
- `npx @chriscode/hush has <KEY>`
- `npx @chriscode/hush set <KEY>`
- `npx @chriscode/hush run -- <command>`


Legacy bridge only:
- `npx @chriscode/hush migrate --from v2`
- `npx @chriscode/hush migrate --from v2 --cleanup`


Do not teach or recreate `hush.yaml`, `hush init`, or `hush encrypt` as the current setup.

Troubleshooting prompt

Hush isn't working in this project. Please diagnose:


1. Check whether the repo already uses `.hush/`
2. Run `npx @chriscode/hush config show`
3. Run `npx @chriscode/hush inspect`
4. Verify sops and age are installed
5. If the repo is legacy v2, use `npx @chriscode/hush migrate --from v2`


Do not switch back to `hush.yaml`, `hush init`, or `hush encrypt` as the main path.