Read SOUL.md for PayRam's core philosophy, voice, and design principles.
MCP server for AI-assisted PayRam integration.
- Do NOT add
Co-Authored-Bytrailers - Use conventional prefixes:
feat:,fix:,refactor:,docs:,chore: - Describe the "why", not the "what"
- Never commit
.env, credentials, or API keys
- Branch from
main:git checkout -b hotfix/<description> origin/main - Apply fix → run
/simplify→ build & test - Commit with
fix:prefix - Raise PR from the same branch to both
mainanddevelop
Every PR must follow these steps:
- Assign PR to self
- Add reviewers: sam6230i, aryaman-payram, gulshanweb3
- Add PR to the PayRam project board:
gh project item-add 3 --owner PayRam --url <PR_URL> - If the develop PR has merge conflicts, merge
origin/developinto the branch and resolve
Do NOT cherry-pick or create separate branches for develop. One branch, two PRs.
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."