You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+20-5Lines changed: 20 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,15 +47,30 @@ When working on spec-kit:
47
47
48
48
## AI contributions in Spec Kit
49
49
50
-
We leverage AI and AI agents for help with this project and value contributions that also use AI to detect issues and improve Spec Kit.
50
+
We welcome and encourage the use of AI tools to help improve Spec Kit! Many valuable contributions have been enhanced with AI assistance for code generation, issue detection, and feature definition.
51
51
52
-
However, to help the team focus on important issues and features, we will close issues and PRs that are **low-effort AI-generated changes**. This includes changes or reports that have not been tested, clearly had no human input, and that aren't aligned with the overall project.
52
+
### What we're looking for
53
53
54
-
If you are submitting an AI generated issue or pull request, please include **concrete test cases**, **scenarios**, and an outline of the **end-to-end developer experience** with your suggested change that were **written by you**. If someone can easily spot that a contribution is entirely AI-generated without your input, you have more work to do.
54
+
When submitting AI-assisted contributions, please ensure they include:
55
55
56
-
In practice, this means that you need to understand the changes that you're requesting and be able to explain why the change is necessary within the Spec Kit scope.
56
+
-**Human understanding and testing** - You've personally tested the changes and understand what they do
57
+
-**Clear rationale** - You can explain why the change is needed and how it fits within Spec Kit's goals
58
+
-**Concrete evidence** - Include test cases, scenarios, or examples that demonstrate the improvement
59
+
-**Your own analysis** - Share your thoughts on the end-to-end developer experience
57
60
58
-
If you are identified as submitting a large number of AI-generated changes that fall in the category above, the team might, at their discretion, block your account from further contributing to Spec Kit.
61
+
### What we'll close
62
+
63
+
We reserve the right to close contributions that appear to be:
64
+
65
+
- Untested changes submitted without verification
66
+
- Generic suggestions that don't address specific Spec Kit needs
67
+
- Bulk submissions that show no human review or understanding
68
+
69
+
### Guidelines for success
70
+
71
+
The key is demonstrating that you understand and have validated your proposed changes. If a maintainer can easily tell that a contribution was generated entirely by AI without human input or testing, it likely needs more work before submission.
72
+
73
+
Contributors who consistently submit low-effort AI-generated changes may be restricted from further contributions at the maintainers' discretion.
0 commit comments