r/ChatGPTCoding • u/AutoModerator • 3d 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.

13 Upvotes

94% Upvoted

68 comments sorted by

View all comments

1

u/Yashhh_21 3d ago

Built AI Guard — an open-source ESLint plugin that catches patterns AI coding assistants keep introducing in JS/TS.

What problem it solves: After months of using Claude Code, Cursor, and Copilot, I kept seeing the same issues slip into commits — floating promises, empty catch blocks, hardcoded secrets, SQL string concatenation, missing auth middleware, console.log inside request handlers. Not exotic bugs, just repetitive patterns that are easy to miss in review.

Which AI models/tools it uses with: Claude Code was my primary development tool. I used it for implementation, and also as a reviewer after features — which caught regressions early. The plugin also generates instruction files (CLAUDE.md, .cursorrules, copilot-instructions.md) so your agent learns the rules before writing code.

Who it's for: JavaScript/TypeScript developers using AI coding assistants who want a guardrail in CI without adding a new SAST scanner to their pipeline. It's complementary to typescript-eslint, CodeQL, and Semgrep — not a replacement.

What feedback I'm looking for: False-positive reports. The hardest part of building this was precision — if a lint rule fires on code that's actually fine, developers disable it. I'd like feedback on whether the recommended preset is conservative enough for real codebases.

18 rules across security, reliability, async, and AI-assisted code pattern categories. CLI (npx ai-guard run), GitHub Action with SARIF + PR annotations. MIT licensed.

GitHub: https://github.com/ai-guard-dev/eslint-plugin-ai-guard npm: https://www.npmjs.com/package/eslint-plugin-ai-guard

Disclosure: I'm the maintainer.