DEDUPEDWhat do you want to do?
4 use cases
-
Scan a Kotlin change for known footguns before merge
Run a 32-pattern scanner over the lines your branch adds and review each flagged trap.
View prompt
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.
-
Review a Compose screen against UI and state traps
Have an agent check a Compose screen against the visuals, screens and state trap indexes.
View prompt
Using the installed kotlin-footguns skills, review <path to screen file> against the compose-visuals-footguns and compose-screens-footguns indexes. Expected output: a list of matched trap files with the line in the screen that triggers each one. Verify that each cited trap file exists and that its trigger description matches the code you point to.
-
Audit desktop packaging, signing and CI config
Check a desktop JVM build for packaging, code-signing and CI traps before a release.
View prompt
Using the desktop-and-build-footguns skill from kotlin-footguns, audit the build and CI files at <project path>. Expected output: a table of matched traps with file and line, and a verification result for each. Verify that every verification command you run is one the trap file lists, and that you did not invent any new command.
-
Check a Room migration against data-layer traps
Have an agent review schema changes and migration SQL against the data-layer trap index.
View prompt
Using the data-layer-footguns skill from kotlin-footguns, review the Room migration in <migration file path> and its schema diff. Expected output: each matched migration trap with the SQL line that triggers it and the verification result. Verify that each verification command you run appears verbatim in the matched trap file.
How to use Kotlin Footguns
- Check you have what it needs: 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.
- Open maxrave-dev/kotlin-footguns on GitHub and read the README and license.
- Install the skills into your project with
npx skills@latest add maxrave-dev/kotlin-footguns, selecting the footgun-scan skill. (inferred, check the README) - From the repository root, run
python3 .claude/skills/footgun-scan/scripts/scan.py --base origin/main --fail. - Read each likely hit and open the trap file it names to confirm or dismiss it.
- Read each look hit as a place to inspect, not a verdict.
These steps come from our top use case, Scan a Kotlin change for known footguns before merge, which also has a copy-paste agent prompt.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeKotlin Footguns alternatives · Best AI repos for Software and DevOps
About this repo
- Who it is forKotlin and Compose Multiplatform developers, and the coding agents they run, who want known pitfalls checked before a change ships.
- Why it is hot
- LanguagePython
- Sourcegithub.com/maxrave-dev/kotlin-footguns · Back to Hot repos
Requirements
- 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
Maintain Kotlin Footguns? Add the Featured on Deduped badge
Paste this into your README:
[](https://dedupedai.com/use-cases/maxrave-dev-kotlin-footguns/?ref=badge)
Questions about Kotlin Footguns
What is Kotlin Footguns?
A set of agent skills and a scanner that flag 228 known failure modes in Kotlin, Compose Multiplatform and desktop JVM code, drawn from a production music app. It is an open-source project on GitHub: https://github.com/maxrave-dev/kotlin-footguns.
Who is Kotlin Footguns for?
Kotlin and Compose Multiplatform developers, and the coding agents they run, who want known pitfalls checked before a change ships.
What can I do with Kotlin Footguns?
4 use cases so far, for example: Scan a Kotlin change for known footguns before merge; Review a Compose screen against UI and state traps; Audit desktop packaging, signing and CI config. Each has steps and a copy-paste agent prompt.
What do I need to run Kotlin Footguns?
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.
What are alternatives to Kotlin Footguns?
Other hot AI repos in Software and DevOps: Harness2, iFixAi, Orca, Diagram Design, AI Memory.
Is Kotlin Footguns safe to run?
Deduped does not own, audit or vouch for it. Read the README and license, run it on your own systems first and review every command before you run it.