cli-faq-shortcuts

Stop typing the same long request to your coding agent every day. This Agent Skill reads your own history, finds the asks you keep repeating, and turns each one into a short command, like /sent or /project billing. It works in Claude Code, Codex and Cursor.

• Built from what you actually typed. On one real project, a single ask had been typed 230 times in different words. You see the counts and pick which become shortcuts.
• Secrets stay out. API keys, tokens, and passwords you pasted into old prompts are replaced with [REDACTED] before your agent reads the list.
• Nothing to install but the skill. The extractor is standard-library Python: no packages, API keys, or network calls. Intent grouping happens in your coding agent.

Watch or download the 24-second video · What's new in v1.3.0

The demo illustrates the workflow with synthetic data; it is not a live agent recording.

Quick start

1. Install (macOS / Linux, needs git and Python 3.9+; on Windows see Windows):

git clone https://github.com/kishormorol/cli-faq-shortcuts ~/.agents/skills/faq-shortcuts
mkdir -p ~/.claude/skills && ln -sfn ~/.agents/skills/faq-shortcuts ~/.claude/skills/faq-shortcuts

2. Open your project in Claude Code, Codex or Cursor, in a new session.

3. Ask "what do I keep asking in this project?", or type /faq-shortcuts in Claude Code.

You'll get a table of your most repeated asks with how often you typed each. Pick the ones you want and they become shortcuts in that project.

The repo is cli-faq-shortcuts; the skill it installs is called faq-shortcuts.

If it saves you typing, please ⭐ star the repo. Stars are how other people find it.

Commands

# inside your project, in Claude Code
/faq-shortcuts                        # find your repeated asks and propose shortcuts
/faq-shortcuts --since 2026-06-01     # only look at recent history
/faq-shortcuts --source codex         # only what you asked Codex

# the extractor on its own: no agent, nothing leaves your machine
E=~/.agents/skills/faq-shortcuts/scripts/extract_asks.py
python3 "$E" .                       # matching prompts, oldest first
python3 "$E" . --since 2026-09-01 | wc -l               # how many since September
python3 "$E" . --format jsonl         # structured records for your own scripts
python3 "$E" . | awk -F'\t' 'split($3,w," ")>=4 {print tolower($3)}' \
  | sort | uniq -c | sort -rn | head                     # your most repeated exact requests

The last one counts exact repeats only, and it undercounts. On one real project, the most repeated exact request appeared 14 times. Grouped by intent, however it was worded, the top ask had been typed 230 times. That grouping is the agent's job in /faq-shortcuts.

What you get

You kept typing	You type now
"how many people signed up this week, not counting test accounts?"	/signups
"did the newsletter actually go out? did it reach everyone?"	/sent
"any update on the billing migration? what's blocked?"	/project billing
"add this CSV of new customers, skip the ones we already have"	/import new.csv

Each shortcut is a small file in your project, .claude/skills/<name>/SKILL.md, for example:

---
name: sent
description: Check whether a batch email actually reached people. Use for "did the
  newsletter go out?", "did it reach everyone?", "did X get the email?".
---
# Did it go out

Report only. Never re-send from this shortcut.

## Query
scripts/email-status.js --batch <name>   ← the script your project already has

## Traps
- A "delivered" status to a shared inbox proves nobody read it (happened 3 May).

## Report
Sent / delivered / bounced counts, then the bounced addresses. Then ask.

The shortcuts point at the scripts and queries your project already uses, and they record the mistakes already made on that path. /sent checks the send record, not the earlier message where the agent said it sent it. So a shortcut is shorter to type, and it verifies the outcome instead of trusting a previous claim. Anything that writes or sends does a dry run first and waits for your yes, so a typo stops at the preview.

This is the beginning of the README. Read the rest at the original. Read the full README ↗