القائمة
Follow Resource-Adda branching and PR process. Use when starting new work, creating pull requests, reviewing code, merging to main, or resolving merge conflicts.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
RESTful API patterns, request/response formatting, authentication flows, versioning for Resource-Adda. Use when designing API endpoints, planning request bodies, structuring error responses, or implementing authentication.
Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.
Express server scaffolding, plugin architecture, middleware patterns for Resource-Adda. Use when starting backend development, adding middleware, troubleshooting server startup, or creating new plugin modules.
Transforms vague prompts into optimized Claude Code prompts. Adds verification, specific context, constraints, and proper phasing. Invoke with /best-practices.
GitHub Actions workflows, testing automation, deployment triggers for Resource-Adda. Use when setting up CI/CD, automating tests, configuring deployments, or managing workflow triggers.
Linting rules, architecture enforcement, code patterns, tech debt tracking for Resource-Adda. Use when enforcing code conventions, managing tech debt, refactoring, or scaling code patterns.
| name | git-workflow |
| description | Follow Resource-Adda branching and PR process. Use when starting new work, creating pull requests, reviewing code, merging to main, or resolving merge conflicts. |
<type>/<issue>-<description>
git checkout -b feature/123-enrollment-api
git checkout -b fix/456-login-crash
git checkout -b chore/789-update-deps
# Types: feature, fix, chore, docs, test, perf, refactor
Conventional Commits: <type>(<scope>): <subject>
git commit -m "feat(api): add vendor assignment endpoint"
git commit -m "fix(auth): handle expired token gracefully"
git commit -m "docs: update API standards guide"
Types: feat, fix, chore, docs, refactor, perf, test
git fetch origin
git rebase origin/main
# If conflicts: edit files → git add . → git rebase --continue
git push origin feature/123-task
gh pr create --title "feat: add enrollment" --body "Closes #123"
# PR Checklist:
# - [ ] pnpm lint passes
# - [ ] pnpm -C apps/<module> test -- --run passes
# - [ ] pnpm build succeeds
# - [ ] Docs updated if needed
Squash merge for clean history:
gh pr merge --squash 123
# Auto-deletes feature branch
git checkout -b feature/<issue>-<desc> # Create branch
git commit -m "type: message" # Commit
git push origin feature/<issue>-<desc> # Push
git fetch && git rebase origin/main # Update
| Issue | Solution |
|---|---|
| Merge conflict | Edit conflicted files, git add ., git rebase --continue |
| Committed to main | git revert <hash> — never force-push main |
| Need to reset | git reset --hard origin/main (loses local changes) |