c84c56bfbd
Comprehensive documentation on AI code attribution and disclosure: - New guide: guide/ai-traceability.md (~640 lines) - LLVM "Human-in-the-Loop" policy (Assisted-by trailer) - Ghostty mandatory disclosure pattern - Fedora contributor accountability framework - git-ai tool documentation - PromptPwnd security vulnerability - Four-level disclosure spectrum - Implementation guides (solo, team, enterprise) - Templates: examples/config/ - CONTRIBUTING-ai-disclosure.md - PULL_REQUEST_TEMPLATE-ai.md - Cross-references added to: - ultimate-guide.md (after Co-Authored-By section) - learning-with-ai.md (after Vibe Coding Trap) - security-hardening.md (See Also) - guide/README.md (table of contents) - reference.yaml: 14 new entries for AI traceability topics Source: Vibe coding needs git blame (Piotr Migdał, Jan 2026) + Perplexity research on LLVM, Ghostty, Fedora policies Co-Authored-By: Claude <noreply@anthropic.com>
1.4 KiB
1.4 KiB
Pull Request Template with AI Disclosure
Save as
.github/PULL_REQUEST_TEMPLATE.mdin your repository
Description
Type of Change
- Bug fix (non-breaking change that fixes an issue)
- New feature (non-breaking change that adds functionality)
- Breaking change (fix or feature that would cause existing functionality to not work as expected)
- Documentation update
- Refactoring (no functional changes)
AI Assistance
- No AI tools were used for this contribution
- AI was used for research/understanding only (no generated code)
- AI generated some code (please specify below)
- AI generated most of the code (please specify below)
AI Tool(s) Used:
What AI Helped With:
Checklist
- I have reviewed all AI-generated code and understand it
- I can answer questions about this code during review
- My code follows the project's style guidelines
- I have added tests that prove my fix/feature works
- New and existing tests pass locally
- I have updated documentation if needed