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
+30Lines changed: 30 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,12 +47,40 @@ When working on spec-kit:
47
47
48
48
## AI contributions in Spec Kit
49
49
50
+
> [!IMPORTANT]
51
+
>
52
+
> If you are using **any kind of AI assistance** to contribute to Spec Kit,
53
+
> it must be disclosed in the pull request or issue.
54
+
50
55
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
56
57
+
That being said, if you are using any kind of AI assistance (e.g., agents, ChatGPT) while contributing to Spec Kit,
58
+
**this must be disclosed in the pull request or issue**, along with the extent to which AI assistance was used (e.g., documentation comments vs. code generation).
59
+
60
+
If your PR responses or comments are being generated by an AI, disclose that as well.
61
+
62
+
As an exception, trivial spacing or typo fixes don't need to be disclosed, so long as the changes are limited to small parts of the code or short phrases.
63
+
64
+
An example disclosure:
65
+
66
+
> This PR was written primarily by GitHub Copilot.
67
+
68
+
Or a more detailed disclosure:
69
+
70
+
> I consulted ChatGPT to understand the codebase but the solution
71
+
> was fully authored manually by myself.
72
+
73
+
Failure to disclose this is first and foremost rude to the human operators on the other end of the pull request, but it also makes it difficult to
74
+
determine how much scrutiny to apply to the contribution.
75
+
76
+
In a perfect world, AI assistance would produce equal or higher quality work than any human. That isn't the world we live in today, and in most cases
77
+
where human supervision or expertise is not in the loop, it's generating code that cannot be reasonably maintained or evolved.
78
+
52
79
### What we're looking for
53
80
54
81
When submitting AI-assisted contributions, please ensure they include:
55
82
83
+
-**Clear disclosure of AI use** - You are transparent about AI use and degree to which you're using it for the contribution
56
84
-**Human understanding and testing** - You've personally tested the changes and understand what they do
57
85
-**Clear rationale** - You can explain why the change is needed and how it fits within Spec Kit's goals
58
86
-**Concrete evidence** - Include test cases, scenarios, or examples that demonstrate the improvement
@@ -72,6 +100,8 @@ The key is demonstrating that you understand and have validated your proposed ch
72
100
73
101
Contributors who consistently submit low-effort AI-generated changes may be restricted from further contributions at the maintainers' discretion.
74
102
103
+
Please be respectful to maintainers and disclose AI assistance.
104
+
75
105
## Resources
76
106
77
107
-[Spec-Driven Development Methodology](./spec-driven.md)
0 commit comments