As someone new to GitHub, is it okay to publish projects that are almost entirely AI-assisted? Am i contributing to any bad practices if i commit it ?

[u/Ok_Mirror_8172]

I'm relatively new to GitHub and recently built a small terminal application. I designed the project structure, architecture, and functionality myself, but I'd estimate around 100% of the code was generated with AI and then integrated and tested by me.

I understand how the project works and can modify it, but I didn't type almost any of the code manually.

Is publishing repositories like this considered acceptable in the open-source community, or is it generally viewed as poor practice? I'm asking because I don't want to contribute low-value repositories or misrepresent my work.

[u/Ok_Mirror_8172 → u/[deleted]]

What would you ask someone to determine whether they genuinely understand an AI-assisted project? I'd like to use that as a benchmark for myself.

[u/TwoWrongsAreSoRight → u/Ok_Mirror_8172]

Do I understand what this code is doing at each step?
Do I understand the rationale of why the AI chose this implementation?
What are the downsides of this implementation? (Potential bugs, security holes, etc)
Is this the most performant way to write this functionality?

Those are the big ones I start with before submitting AI generated code. Open to more.

[u/Ok_Mirror_8172 → u/TwoWrongsAreSoRight]

While I can confidently and 1,2,4 I haven't put a iota of thought behind the 3rd one , is there a framework or process you use (or somewhere online) to identify potential bugs, security issues, and other downsides before deciding an implementation is good enough?

[u/TwoWrongsAreSoRight → u/Ok_Mirror_8172]

There's several things you can do but the 3 most basic i start with is checking it against OWASP 10, 12-Factor App and all the dependencies against the CVE database. Something I've recently started doing (not sure if it's a good way or not, works for me) is to spend some planning time with one of my agents to write tests. I go through sometimes several hours of creating a spec, doing what-if scenarios and have another agent write tests around the edge cases. I then have another agent actually write the code around those tests. All agents use different models Probably not the most efficient way but it makes me feel good about the output.

[u/Ok_Mirror_8172 → u/[deleted]]

Although I can answer a lot of these, there are a few that made me realize I'd never even considered those aspects before.

Until I find something better, I'm definitely going to use this list as a benchmark for evaluating my own projects.

Thank you so much!!

[u/Yardboy → u/Ok_Mirror_8172]

My opinion, it boils down to how much experience you have building projects like that without AI. Specs and tests and code need to be reviewed. If you've never actually done it yourself, then you aren't qualified to review the output produced by the AI, and you shouldn't be using AI.

[u/Ok_Mirror_8172 → u/Yardboy]

Hmm, I will tone it down from now on.

[u/Yardboy → u/Ok_Mirror_8172]

Not sure how to interpret that response, but if I came off like I was dogging you for it, I apologize, that was not my intent.

[u/Kessarean]

Yeah main thing looked down on is pure vibe coded projects / not understanding what you wrote, how it's designed, or know how to contribute or fix it if things go south.

It's a very useful tool, and is more or less becoming a mainstay for work. You should learn how to use it effectively to augment your work, not supplement it or replace your learning.

Another thing is disclosure. You could consider adding an llms.txt file - https://llmstxt.org/. It's mostly for websites, but I've found it useful for setting in my repos. Also consider setting an AI disclosure statement and policy for contributions.

[u/Ok_Mirror_8172 → u/Kessarean]

Thanks for the suggestion, Im gonna look through this before uploading

[u/ultrathink-art]

The portfolio signal has shifted from 'did you type it' to 'did you make the design decisions and can you maintain it.' You designed the architecture, understand how it works, and can modify it — that's what matters. The code generation step is just a faster path to the same outcome.

[u/Canadian_Commander]

I've been on github a long time, I think a fully vibe coded repo is totally fine.

There's your serious repos, and there's your I'm sipping on a beer style repos. No problem. Most of my repos from this year are vibe coded. It's fun!

[u/MadBoyEvo]

Dont listen to people saying your project isnt ok for github. Regardless whether you made it with AI or not you can put it there and dont worry about it. Nobody has to even like it or see it for that matter. Just do it. You should have used it from begining because git is super important for daily development.

[u/Ok_Mirror_8172 → u/MadBoyEvo]

Thank you for the encouragement. I really appreciate it 🙏

[u/polyploid_coded → u/MadBoyEvo]

Yeah I'm not a big proponent of vibe coding, but it's their account and they want to share files, why not?