Skip to content

docs: add AI-assisted contributions guidelines#1968

Open
notorious-d-e-v wants to merge 1 commit intox402-foundation:mainfrom
notorious-d-e-v:docs/ai-assisted-contributions
Open

docs: add AI-assisted contributions guidelines#1968
notorious-d-e-v wants to merge 1 commit intox402-foundation:mainfrom
notorious-d-e-v:docs/ai-assisted-contributions

Conversation

@notorious-d-e-v
Copy link
Copy Markdown
Contributor

@notorious-d-e-v notorious-d-e-v commented Apr 9, 2026

Summary

  • Add AI-assisted contributions section to CONTRIBUTING.md
  • Include sample system prompt for AI coding agents

Motivation

x402 has no guidance on AI-generated contributions. Batch-submitted PRs, inflated descriptions for trivial changes, and unreviewed machine output are already showing up. This sets a quality bar: review before requesting review, strip filler, verify payment logic against specs, disclose AI usage.

Adapted from Neovim's approach, with x402-specific additions around payment/signature correctness and a practical agent prompt.

AI disclosure

This PR was prepared with Claude Code and reviewed by a human before submission.

Test plan

  • Review guidelines for clarity and tone
  • Verify sample prompt covers x402-specific concerns
  • Confirm section integrates with existing CONTRIBUTING.md structure

Set expectations for AI-generated contributions: require human review
before requesting PR review, remove verbosity and redundancy, verify
payment/signing correctness against specs, and disclose significant AI
usage. Include a sample system prompt for AI coding agents (Claude Code,
Codex, Cursor) that aligns agent output with x402 contribution standards.

Inspired by Neovim's AI-assisted work guidelines, adapted for x402's
security-sensitive payment infrastructure context.
@phdargen phdargen self-assigned this Apr 9, 2026
@ryanRfox
Copy link
Copy Markdown
Contributor

ryanRfox commented Apr 9, 2026

Fully support. I've hit many spec related gaps trying to implement full stack solutions for arbitrary token support using permit2 so adding "verify against the spec" should help smooth out some of the rough edges within the TS SDK and force lazy AI agents to try harder. I've got a number of small changes PRed but each one addresses a real challenge I face within the SDK and I want others to enjoy a better DX as a result. When I hit a blocker, I try to understand the spec first and the intention behind it. Then I look for the most targeted change available without introducing technical debt.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants