feat: add PR attribution and document Claude Code setup

[scottschreckengaust]

Summary

• Adds attribution.pr to .claude/settings.json so Claude Code automatically appends the required contributor statement to PR descriptions, preventing CI failures from the contributorStatement check
• Adds a note in CONTRIBUTING.md pointing Claude Code users to the Development Guide
• Documents the attribution.pr setting in the Claude Code Setup section of the Development Guide

Test plan

• Create a PR using Claude Code and verify the description includes both the Claude Code attribution and the contributor statement
• Verify the contributorStatement CI check passes on this PR

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the project license.

[theagenticguy]

Do we expect the agent plugins for aws to have plugins/skills/agents etc. that enhance the development of the marketplace itself? would be good to capture what a user "job to be done" would look like in terms of contribution to the repo vs. using the plugins separate from the repo itself.

[scottschreckengaust]

Do we expect the agent plugins for aws to have plugins/skills/agents etc. that enhance the development of the marketplace itself? would be good to capture what a user "job to be done" would look like in terms of contribution to the repo vs. using the plugins separate from the repo itself.

Agreed and removed for a future state if necessary. Only keeping the contribution statement for the pull request validation GitHub Workflow.

[theagenticguy]

Do we expect the agent plugins for aws to have plugins/skills/agents etc. that enhance the development of the marketplace itself? would be good to capture what a user "job to be done" would look like in terms of contribution to the repo vs. using the plugins separate from the repo itself.

Agreed and removed for a future state if necessary. Only keeping the contribution statement for the pull request validation GitHub Workflow.

One more thing (sorry for the churn!). Should we indicate in the readme or CONTRIBUTING docs anywhere? e.g. if you use Claude Code to contribute, we have .claude folder ?

[scottschreckengaust]

Do we expect the agent plugins for aws to have plugins/skills/agents etc. that enhance the development of the marketplace itself? would be good to capture what a user "job to be done" would look like in terms of contribution to the repo vs. using the plugins separate from the repo itself.

Agreed and removed for a future state if necessary. Only keeping the contribution statement for the pull request validation GitHub Workflow.

One more thing (sorry for the churn!). Should we indicate in the readme or CONTRIBUTING docs anywhere? e.g. if you use Claude Code to contribute, we have .claude folder ?

Good call. The Development Guide already has a "Claude Code Setup" section (line 20) that covers marketplace registration and the .claude/settings.json plugin configuration. We could add a brief note there about attribution.pr auto-including the contributor statement, but I'd keep it minimal since the setting is transparent — contributors don't need to do anything for it to work.

For the CONTRIBUTING.md, I'd suggest keeping it tool-agnostic (it currently is) and letting the Development Guide be the Claude Code-specific onboarding doc. We can add a one-liner to CONTRIBUTING.md pointing Claude Code users to the dev guide if that feels useful. Happy to do either as a follow-up.

[scottschreckengaust]

@theagenticguy Added the doc updates in this PR:

• CONTRIBUTING.md now points Claude Code users to the Claude Code Setup section in the Development Guide
• Development Guide documents the attribution.pr setting that auto-includes the contributor statement in Claude Code PRs