القائمة
Generate a PR/MR description after the review passes. Use after /review confirms the code is ready to merge. Reads context/templates.md for the required format.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Build the project and verify it compiles cleanly. Use after making changes to confirm nothing is broken before running tests. Reads the build command from context/build.md.
Auto-configure .github/copilot-instructions.md and context/ knowledge docs for a new project. Use when setting up Brain Bootstrap in a new repository. Discovers the codebase, fills in templates, and writes project-specific configuration.
Save session state before context gets full or before ending. Writes current task state, branch, and loaded docs to context/tasks/todo.md so the next session can resume cleanly.
Clean workspace — build artifacts, dependencies, caches, Docker volumes, or temp files. Accepts arguments like build, deps, all, cache, docker, tasks, reinstall.
Load all relevant context/ knowledge files for a domain area. Use at session start or when switching to a new topic. Accepts a domain keyword like api, database, auth, build, security.
Query the database — list schemas, tables, describe a table, or run SQL. Accepts arguments like schemas, tables, describe <table>, or raw SQL.
| name | mr |
| description | Generate a PR/MR description after the review passes. Use after /review confirms the code is ready to merge. Reads context/templates.md for the required format. |
Generate a structured pull request description.
/review MUST pass (verdict: PASS, confidence ≥ 95) before generating a PR description# Confirm tests pass
# (use the test command from context/build.md)
If tests fail: STOP. Fix before generating the PR description.
Read context/templates.md — the required PR/MR format for this project.
git --no-pager diff main...HEAD --stat | head -50
git --no-pager log main...HEAD --oneline | head -20
If a ticket number is referenced, extract the requirements from it.
Use the template from context/templates.md. If no template exists, use this default:
## What
<One paragraph: what does this change do and why?>
## Why
<One paragraph: what problem does this solve? Link to ticket.>
## How
<Bullet list: key implementation decisions and approach>
## Testing
<What was tested? How? Test commands run + results>
## Checklist
- [ ] Tests pass
- [ ] No new warnings
- [ ] Documentation updated (if applicable)
- [ ] Breaking changes documented (if applicable)
Show the PR description and proposed git push command. Wait for confirmation before pushing.