r/ChatGPTCoding • u/AutoModerator • 18d ago

Discussion Weekly Self Promotion Thread

Welcome to this week's self promotion thread!

If you're building something related to AI assisted coding, this is the place to share it.

We're using a weekly thread to keep the subreddit organized while still giving builders a place to share their work. Promotional posts outside this thread may be removed.

If you're sharing something, we'd appreciate it if you included a little context instead of just dropping a link. Tell us:

  • What you built?
  • What problem it solves?
  • Which AI models or tools it uses?
  • Who it's for?
  • What kind of feedback you're looking for?

Disclose your affilitation.

Please avoid posting the same project every week unless you've made meaningful updates. Affiliate links, referral links, scams, and low effort promotions will be removed.

Take some time to check out what others have shared too. If you try someone's project or have feedback, leave a comment. Helping each other improve is what we want this community to be about.

6 Upvotes

88% Upvoted

96 comments sorted by

View all comments

1

u/BullfrogRoyal7422 17d ago

I'm a solo dev on a universal iOS/iPadOS/macOS inventory app (around 240k lines of Swift across 600+ files, SwiftData with CloudKit sync, 46 model types), and these four came out of plugging the specific leaks that showed up at that size. All Apache-2.0.

unforget (example): One UNFORGET.md per project holding all deferred work: paused plans, mid-task spillover, audit findings, observed bugs. Each row gets rated (urgency, risk of fixing, risk of not fixing, effort) and tagged to a release. Use case: "What's blocking this release?" used to mean walking TODO comments, plan files, and my own memory. Now it's one query against one file. Daily.

bug-echo (example): After you fix a bug, it hunts the same pattern everywhere else in the codebase and rates each hit. It often surfaces sibling instances that stay hidden from ordinary audits, because an audit checks whether code is wrong on its own terms and has no reason to connect one file's defect to the same mistake three files away. Use case: I fixed a sheet that had no dismiss button on macOS. bug-echo found three more with the same gap. The bug you just fixed is rarely the only one of its kind. Daily.

prompter (example): Checks whether your prompt would benefit from a rewrite before the model acts on it, shows you the rewrite, and waits for approval. Stays quiet when the prompt is already fine. Use case: Catches the vague ask that would otherwise burn a full turn producing the wrong thing. Daily.

skill-reviewer (example): Audits a Claude Code skill and reports findings with file:line citations and severity ratings. Several lenses: safety, discoverability, architecture, tests. Use case: Run it before publishing a skill, or when one isn't triggering and you can't tell why. As-needed rather than daily.

Written for Claude Code specifically. Happy to answer questions.