[fullsend-ai-coder]

Add a CONTRIBUTING.md at the repo root so newcomers know how to propose changes. Covers: repo intro, fork/branch workflow off main, PR description requirements, and issue linking expectations. Kept to 26 lines of plain Markdown with no extra tooling or CI changes.

---

Closes #2

Post-script verification

• Branch is not main/master (agent/2-add-contributing-md)
• Secret scan passed (gitleaks — 37bda0b301fdc95c7f176ac83fec201262684a6f..HEAD)
• Pre-commit hooks passed (authoritative run on runner)
• Tests ran inside sandbox

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 10:08 PM UTC · Completed 10:11 PM UTC

Commit: 0dbd196 · View workflow run →

[fullsend-ai-review]

Review — ✅ Approve

PR: #3 — docs(#2): add CONTRIBUTING.md with PR expectations
Author: fullsend-ai-coder[bot] · Branch: agent/2-add-contributing-md → main
Scope: 1 file added · +26 lines

Summary

This PR adds a new CONTRIBUTING.md to the repository root, providing newcomers with concise guidance on proposing changes and PR expectations. The content is well-structured Markdown covering repo purpose, fork/branch workflow, PR description requirements, and issue-linking conventions.

Dimension assessment

Dimension	Result
Correctness	✅ Documentation only — no logic, no build artifacts, no tests required
Security	✅ No executable content, no secrets, no configuration changes
Intent & coherence	✅ Directly addresses issue #2 acceptance criteria — appropriately scoped single-file addition
Style & conventions	✅ Clean Markdown, consistent heading hierarchy, concise prose
Documentation currency	✅ New file; does not make existing docs stale
Cross-repo contracts	✅ N/A — no APIs, schemas, or interfaces affected

Acceptance criteria verification (issue #2)

• ✅ Short intro identifying repo as the rhdh-parasol playground
• ✅ Fork-or-branch workflow off main
• ✅ PR description requirement (what changed and why)
• ✅ Issue linking expectation (Closes #123 example)
• ✅ No other files changed
• ✅ Under ~40 lines (26 lines)
• ✅ Markdown only, no tooling or CI changes

Injection defense

PR body, commit messages, and file content were inspected for instruction-like patterns — none found.

No findings at or above the reporting threshold.

---

Labels: PR adds contributor documentation