Ask HN: How are you attributing your AI usage when developing software?

4•hartleybrody•5mo ago

I have started a convention of prefixing a commit message with "prompt:" for commits that are entirely AI generated (which I have read through and approved) and then I make my own manual changes and iterations in subsequent commits.

I feel like this is a reasonable attempt at disclosure, but it also seems like it's lacking. I usually include a summary, not the entire prompt (how would I included tool use?) I don't say which models or "agent" was used (cursor sidebar chat vs calude code, etc). Not sure if this matters though?

How have you been managing this in your own workflows?

Comments

not_your_vase•5mo ago

I don't think it's any different than attributing the compiler or the text editor. I don't do either of those, and I also don't attribute LLM generated code.

throwaway019254•5mo ago

Completely agree.

That’s why I always prefix my commit messages with “IntelliJ:”.

hartleybrody•5mo ago

Is IntelliJ generating source code that gets committed to your codebase?

Seems completely different. See also, this discussion:

https://news.ycombinator.com/item?id=44976568

ailabs_hq•5mo ago

Do we need to unless you want to indemnify yourself

mikewarot•5mo ago

At the top of my README.md

IMPORTANT: This is almost entirely written by ChatGPT 5, not me

kamphey•5mo ago

I don't think it matters much. Sometimes I do consulting where I'm coding at the same time as the client is there with me. There's lots of little questions and tons of testing involved as I do coding in Google Apps Script in Google Sheets. And I'll quickly say "oh I think ChatGPT can figure this out faster than me" and just prompt it at the same time. Then copy paste and edit and figure out if it's right code for that part.

Not only do they not care, they think it's pretty cool that I can essentially save them an hour here or there.

How were the NIST ECDSA curve parameters generated? (2023)

AI, networks and Mechanical Turks (2025)

Goto Considered Awesome [video]

Show HN: I Built a Free AI LinkedIn Carousel Generator

Implementing Auto Tiling with Just 5 Tiles

Open Challange (Get all Universities involved

Apple Tried to Tamper Proof AirTag 2 Speakers – I Broke It [video]

Show HN: Vibe as a Code / VaaC – new approach to vibe coding

Show HN: More beautiful and usable Hacker News

Toledo Derailment Rescue [video]

War Department Cuts Ties with Harvard University

Show HN: LocalGPT – A local-first AI assistant in Rust with persistent memory

A Bid-Based NFT Advertising Grid

AI readability score for your documentation

NASA Study: Non-Biologic Processes Don't Explain Mars Organics

I inhaled traffic fumes to find out where air pollution goes in my body

X said it would give $1M to a user who had previously shared racist posts

155M US land parcel boundaries

Private Inference

Font Rendering from First Principles

Show HN: Seedance 2.0 AI video generator for creators and ecommerce

Wally: A fun, reliable voice assistant in the shape of a penguin

Rewriting Pycparser with the Help of an LLM

Lobsters Vibecoding Challenge

E-Commerce vs. Social Commerce

Avoiding Modern C++ – Anton Mikhailov [video]

Show HN: AegisMind–AI system with 12 brain regions modeled on human neuroscience

Zig – Package Management Workflow Enhancements

AI-powered text correction for macOS

AppSecMaster – Learn Application Security with hands on challenges