DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to scan a Kotlin change for known footguns before merge with Kotlin Footguns

Run a 32-pattern scanner over the lines your branch adds and review each flagged trap.

  • Top pick
  • Software and DevOps
  • Intermediate
  • 30 minutes
  • From the README
  • Claude Code
  • Codex
  • Cursor
  • Gemini CLI

Who it is forA Kotlin developer about to open a pull request who wants a check against known Kotlin and Compose pitfalls.

The problemCommon Kotlin, Compose and desktop JVM mistakes pass compilation and code review because they look correct on the surface.

The outcomeA list of likely and look hits tied to specific trap files, each one confirmed or dismissed before the branch merges.

What you need first

  • A Kotlin, Compose Multiplatform or desktop JVM project in a git repository
  • Claude Code, or any coding agent that reads the open agent-skills format
  • Python 3 for the footgun-scan script
  • Node.js with npx, if you use the skills CLI install

Steps

  1. Install the skills into your project with npx skills@latest add maxrave-dev/kotlin-footguns, selecting the footgun-scan skill. (inferred, check the README)
  2. From the repository root, run python3 .claude/skills/footgun-scan/scripts/scan.py --base origin/main --fail.
  3. Read each likely hit and open the trap file it names to confirm or dismiss it.
  4. Read each look hit as a place to inspect, not a verdict.
  5. Fix the confirmed hits and run the scan again until it reports nothing you need to act on.

Prompt for your agent

In the kotlin-footguns skills installed in <repo path>, run the footgun-scan script against origin/main and open the trap file for every likely hit. Expected output: each hit marked confirmed or dismissed with a one-line reason. Verify that every confirmed hit names a trap file that exists in the skill directory.

Caveat. The scanner only matches the 32 patterns it ships with, so a clean scan does not mean a change is free of the 228 traps.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page