Skip to content

Latest commit

 

History

History
45 lines (31 loc) · 1.55 KB

File metadata and controls

45 lines (31 loc) · 1.55 KB

PayRam MCP Server

Read SOUL.md for PayRam's core philosophy, voice, and design principles.

MCP server for AI-assisted PayRam integration.

Git Conventions

  • Do NOT add Co-Authored-By trailers
  • Use conventional prefixes: feat:, fix:, refactor:, docs:, chore:
  • Describe the "why", not the "what"
  • Never commit .env, credentials, or API keys

Hotfix Process

  1. Branch from main: git checkout -b hotfix/<description> origin/main
  2. Apply fix → run /simplify → build & test
  3. Commit with fix: prefix
  4. Raise PR from the same branch to both main and develop

PR Instructions

Every PR must follow these steps:

  1. Assign PR to self
  2. Add reviewers: sam6230i, aryaman-payram, gulshanweb3
  3. Add PR to the PayRam project board: gh project item-add 3 --owner PayRam --url <PR_URL>
  4. If the develop PR has merge conflicts, merge origin/develop into the branch and resolve

Do NOT cherry-pick or create separate branches for develop. One branch, two PRs.

PR Review Follow-Up

After creating a PR, schedule a task to check for reviews after 15 minutes and address any comments:

Create a scheduled task (fireAt: 15 minutes from now) with prompt:
"Check PR reviews on PayRam/payram-mcp#<number> (and #<number> if two PRs).
Read all review comments, fix valid issues, push commits, and
reply to resolved comments. For nitpick/style suggestions, use
judgement — fix if reasonable, otherwise reply explaining why not."