بنقرة واحدة
ask
Use when user asks a question that doesn't require any action - just explanation or information
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Use when user asks a question that doesn't require any action - just explanation or information
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Given a TheRock nightly build (URL or run-id), return the rocm-systems pin_sha used in that build
Check whether a given rocm-systems commit is included in a specific TheRock nightly build
Find the first TheRock nightly build that includes a given rocm-systems commit
Reviews Pull Requests or local diffs with an 8-agent fan-out covering static analysis, dead code, code smells + quality (naming, complexity, single-responsibility, magic numbers), language rules (C++/Python/CMake), architecture, simplification, performance (hot-path classification, allocations, locks, I/O), and undefined behaviour (signed overflow, lifetime, strict aliasing, data races, sanitizer coverage; C/C++/unsafe-Rust only). Use when the user asks to "review this PR", "review the diff", "audit this branch", "/pr-review", or when staging changes before push.
Walk through a PR review interactively, one finding at a time. Generate review via pr-review, then for each issue present analysis + proposed inline comment, let user accept/edit/skip, accumulate into a PENDING GitHub review, submit at end.
Use when user wants to list, analyze, review, or summarize GitHub PR comments on a pull request number or URL
| name | ask |
| description | Use when user asks a question that doesn't require any action - just explanation or information |
Use this skill when the user is asking a question that requires explanation only, not implementation.
This skill applies when the user wants to:
Do NOT use this skill if the user wants you to:
exploration-explore-code skill)debugging-rocprof-sys skill)If action is needed, use the appropriate planning skill instead.
Quick explanation vs. deep exploration:
| User Request | Skill to Use |
|---|---|
| "How does auth work here?" (quick answer) | ask |
| "Explore the auth system so I can extract it" (structured analysis) | exploration-explore-code |
| "rocprof-sys crashes when profiling my MPI app" (debugging) | debugging-rocprof-sys |
Structure your answer clearly:
User: "How does the authentication work in this project?"
Response:
Authentication uses JWT tokens with refresh token rotation.
Flow:
- User logs in with credentials
- Server validates and returns access + refresh tokens
- Access token (15min) used for API calls
- Refresh token (7 days) used to get new access tokens
Key files:
src/auth/authService.ts- Main auth logicsrc/middleware/authMiddleware.ts- Token validationsrc/auth/tokenService.ts- Token generation/refreshWould you like me to implement any changes to the auth system?
This skill does not require:
Simply answer the question and move on.