HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
nlothian
Vibe-Prolog
Python2025–2026
nlothian / Vibe-Prolog

Vibe-Prolog

Vibe 🎶 Coding 💻 Prolog 🐪

2Distinct people
11Mentions
1Explicit recommenders
56GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Vibe 🎶 Coding 💻 Prolog 🐪

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

Wait, you think I'm coding this by hand! That is amazing. I love it! I don't remember when which part happened, but I've been gradually moving over to the tools in…

nl used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

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, 11:20:21 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 week11 dated mentions

Observed mentions: 2025-11-19 15:24:52 UTC to 2026-01-12 10:38:13 UTC. Weeks start Monday, UTC.

012342025-11-17 00:00:00 UTC to 2025-11-24 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 commentsNov 172025-11-24 00:00:00 UTC to 2025-12-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2025-12-01 00:00:00 UTC to 2025-12-08 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-12-08 00:00:00 UTC to 2025-12-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-15 00:00:00 UTC to 2025-12-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsDec 152025-12-22 00:00:00 UTC to 2025-12-29 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-12-29 00:00:00 UTC to 2026-01-05 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-01-05 00:00:00 UTC to 2026-01-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-12 00:00:00 UTC to 2026-01-19 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJan 12

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
Nov 172025-11-17 00:00:00 UTC2025-11-24 00:00:00 UTC413
Nov 242025-11-24 00:00:00 UTC2025-12-01 00:00:00 UTC303
Dec 12025-12-01 00:00:00 UTC2025-12-08 00:00:00 UTC101
Dec 82025-12-08 00:00:00 UTC2025-12-15 00:00:00 UTC000
Dec 152025-12-15 00:00:00 UTC2025-12-22 00:00:00 UTC000
Dec 222025-12-22 00:00:00 UTC2025-12-29 00:00:00 UTC101
Dec 292025-12-29 00:00:00 UTC2026-01-05 00:00:00 UTC101
Jan 52026-01-05 00:00:00 UTC2026-01-12 00:00:00 UTC000
Jan 122026-01-12 00:00:00 UTC2026-01-19 00:00:00 UTC101

What Hacker News says

3 sources
nl·Nov 25, 2025Recommendation phrase
Wait, you think I'm coding this by hand! That is amazing. I love it! I don't remember when which part happened, but I've been gradually moving over to the tools in https://github.com/nlothian/Vibe-Prolog/tree/main/ai-tools for most of the development. Most of the coding itself there is done with kilocode. Most of the early conversations don't seem to be available in Claude code now (is there a way to see complete history?), but here's a typical session: > can this interpreter pass command line arguments to the prolog program? [no] > add these as missing to @FEATURES.md [done] > use `gh issue` to create an issue to address this. > - Explain comprehensively what needs to be done > - Note that new test cases must be created > - Note that @FEATURES.md needs updating > Do not provide estimates That raised: https://github.com/nlothian/Vibe-Prol
Read the rest
og/issues/75 Here's the PR for that: https://github.com/nlothian/Vibe-Prolog/pull/92/files That PR was generated using my fix-issue-with-kilocode command. The source code for that is all in here: https://github.com/nlothian/Vibe-Prolog/tree/main/ai-tools. The code reviews were done with Codex and Gemini, and responded to using my address_pr_comments command in that same directory.
In Show HN: Vibe Prolog
> I do not think that [0] was vibe coded. Vibe coding something does not mean that everything is vibe coded ... The author claims in the project README.md[0]: I was working on something else and as a side effect accidently vibe coded a prolog interpretor on my phone over the weekend. And has yet to show any evidence of "vibe coding", to the point where I chose one of many commits challenging this position. So there are two reasonable explanations: A) There is no way to show prompts used when "vibe coding". B) This claim of "vibe coding" a Prolog is disingenuous. Which do you think is the case? 0 - https://github.com/nlothian/Vibe-Prolog
In Show HN: Vibe Prolog

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.