Contributors lack a guided workflow for forking, branching, and submitting PRs

[yasmoradi]

Problem

Contributors who have forked bitfoundation/bitplatform frequently make mistakes when submitting changes:

• Issues are written around the solution rather than the problem, making triage harder
• Wrong or missing labels are applied to Issues
• Branches are created from the wrong base (e.g. origin/main instead of upstream/develop)
• Pull Requests are opened without a reference to the related Issue, so they are not automatically linked or closed on merge
• The This closes #<issue-number> convention is not followed consistently

There is currently no in-editor guidance that walks a contributor through the full process in the correct order.

Expected Behaviour

A contributor using GitHub Copilot in VS Code should be able to invoke a single agent skill and be guided — step by step — through:

1. Syncing their fork with upstream
2. Writing a focused, problem-first Issue with the correct label
3. Creating a branch on origin from upstream/develop
4. Implementing the change following project coding conventions
5. Opening a PR that references the Issue with This closes #<issue-number> in both the title and the description

Actual Behaviour / Current State

No such agent skill exists. Contributors must read multiple documents and piece together the workflow manually, which leads to the inconsistencies described above.

Additional Context

• Related docs already in the repo: CONTRIBUTING.md, .github/GITHUB_PROCESS.md
• Target file location: .github/agents/contribute-to-bitplatform.agent.md