HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
tgalal
promptcmd
Rust2026–2026
tgalal / promptcmd

promptcmd

GenAI prompts as runnable programs

2Distinct people
14Mentions
0Explicit recommenders
48GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

GenAI prompts as runnable programs

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 8:59:02 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week14 dated mentions

Observed mentions: 2026-01-21 13:46:46 UTC to 2026-03-19 14:41:30 UTC. Weeks start Monday, UTC.

02468102026-01-19 00:00:00 UTC to 2026-01-26 00:00:00 UTC (exclusive): 2 mentions; 2 submissions, 0 commentsJan 192026-01-26 00:00:00 UTC to 2026-02-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-02 00:00:00 UTC to 2026-02-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-09 00:00:00 UTC to 2026-02-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-16 00:00:00 UTC to 2026-02-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsFeb 162026-02-23 00:00:00 UTC to 2026-03-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-02 00:00:00 UTC to 2026-03-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-09 00:00:00 UTC to 2026-03-16 00:00:00 UTC (exclusive): 9 mentions; 8 submissions, 1 comments2026-03-16 00:00:00 UTC to 2026-03-23 00:00:00 UTC (exclusive): 3 mentions; 3 submissions, 0 commentsMar 16

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jan 192026-01-19 00:00:00 UTC2026-01-26 00:00:00 UTC220
Jan 262026-01-26 00:00:00 UTC2026-02-02 00:00:00 UTC000
Feb 22026-02-02 00:00:00 UTC2026-02-09 00:00:00 UTC000
Feb 92026-02-09 00:00:00 UTC2026-02-16 00:00:00 UTC000
Feb 162026-02-16 00:00:00 UTC2026-02-23 00:00:00 UTC000
Feb 232026-02-23 00:00:00 UTC2026-03-02 00:00:00 UTC000
Mar 22026-03-02 00:00:00 UTC2026-03-09 00:00:00 UTC000
Mar 92026-03-09 00:00:00 UTC2026-03-16 00:00:00 UTC981
Mar 162026-03-16 00:00:00 UTC2026-03-23 00:00:00 UTC330

What Hacker News says

2 sources
tgalal·Jan 22, 2026Submission

Show HN: Bashme_a_script_that", generate and cache bash scripts via promptcmd

This is an example tool I created using my tool (promptcmd) for turning prompts into "native-looking" executables: Usage: bashme_a_script_that [OPTIONS] <query>... Prompt inputs: --stdin accept stdin input <query>... positional query. Can be spaced and with/without quotes It makes use of caching responses: if I review the generated script and it looks good (or incomprehensible and I'm in YOLO mood), I run the command again and pipe directly into bash. It'll use the reviewed response instead of generating a new one. Would love to get feedback or ideas for promptcmd: Github: https://github.com/tgalal/promptcmd/ Documentation: https://docs.promptcmd.sh/ Examples: https://promptcmd.sh/lib/
1 points · Open discussion
tgalal·Jan 21, 2026Submission

Show HN: GenAI Prompts as "Native" Programs

Lately I've seen several projects for templating and executing prompts. However they all go along the lines of $ executor prompt_file_or_name which didn't exactly fit my "taste". I figured one could use the same trick like busybox, where you can detect if your binary is being executed via a different name (symlink). The symlink name is treated as the promptname, and arguments are generated from a schema defined in the prompt template. So now instead of: # Using https://github.com/chr15m/runprompt echo '{"words": 300, "text": "some long text"}' | ./runprompt summarize.prompt # Or using https://github.com/simonw/llm echo "some long text" | llm -t summarize -p words 300 You get: echo "some long text" | summarize --words 300 And of course with documented arguments and so on: summarize --help Usage: summarize [OPTIONS] --
Read the rest
words <words> --text <text> Prompt inputs: --words <words> Maximum number of words --text <text> The text to summarize, defaults to stdin That was the starting point, then things escalated and suddenly there is load balancing, caching, execution via shebang and other (IMO) neat features :). Happy to get feedback and ideas. Github: https://github.com/tgalal/promptcmd/ Documentation: https://docs.promptcmd.sh/ Examples: https://promptcmd.sh/lib/
1 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.