summaryrefslogtreecommitdiff
path: root/content/en/article/generated-code-policy.md
diff options
context:
space:
mode:
authoreltrac <hi@eltr.ac>2026-09-02 13:43:24 +0800
committereltrac <hi@eltr.ac>2026-09-02 19:28:57 +0800
commit4b168f4174865066ba436e747707eae8a6603e1e (patch)
tree82809afbb1f4f2e4afa15fe630359a9ea7acb810 /content/en/article/generated-code-policy.md
parente4dc746025b98ccc8a14268aa39c0d69f91e6770 (diff)
[draft] new
[draft] add inside java episode link
Diffstat (limited to 'content/en/article/generated-code-policy.md')
-rw-r--r--content/en/article/generated-code-policy.md23
1 files changed, 23 insertions, 0 deletions
diff --git a/content/en/article/generated-code-policy.md b/content/en/article/generated-code-policy.md
new file mode 100644
index 00000000..3f4fd9ff
--- /dev/null
+++ b/content/en/article/generated-code-policy.md
@@ -0,0 +1,23 @@
++++
+title = 'Generated Code Policy for my projects'
+subtitle = ''
+slug = ''
+tags = []
+categories = ''
+date = 2026-09-02T13:28:39+08:00
+draft = true
+toc = true
++++
+
+I've been looking closely at some of my Mac apps, and I noticed how [SuperCMD](https://github.com/SuperCmdLabs/SuperCmd) haven't fixed their homebrew cask issue even though somemone created a [Pull Request](https://github.com/SuperCmdLabs/homebrew-supercmd/pull/3) months ago. Warnings pop up everytime I run `brew update` and it annoys me. I looked through the repository, and could not help but notice how much *contribution* Claude had made and that they lack an LLM policy. Well, I'd rather not have TypeScript written by Claude running on my laptop.
+
+The alternative I found is [vicinae](https://github.com/vicinaehq/vicinae). For a QT project, it looks pretty good. In `CONTRIBUTING.md`, they said:
+
+> AI generated code is treated the same as regular code. As such, all the aforementioned rules apply.
+>
+> AI is not a substitute for properly understanding and testing your code: don't be lazy. Lazy AI PRs that do not respect the guidelines will be rejected. In particular, keep your pull request's description as concise as possible: no maintainer will read your novel.
+>
+> If your contribution was mostly AI generated, it's considered good practice to indicate what model or tool you used for that.
+
+It seems to tolerate heavy use of LLM with some mild restrictions, but fair enough.
+