القائمة
Watch running terminal processes for crashes and stack traces. When an error appears, navigate to the failing file and line, diagnose, and fix it automatically.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Generate or edit images using the OpenAI Image API (gpt-image-2). Use when the user asks to generate, create, draw, render, illustrate, mock up, or edit an image, icon, logo, mockup, illustration, OG image, blog hero, marketing asset, or similar visual. Also use when the user supplies a reference image and asks to modify, restyle, or remix it. Triggers on: "generate an image", "create an image", "make a picture of", "edit this image", "restyle this", "make a mockup of", "draw a", "render a", "illustration of".
When the same multi-step workflow repeats in Cursor (user corrections or agent redos), capture it as a new SKILL.md under .cursor/skills/ so future sessions load it automatically.
After navigating and interacting in Cursor's built-in browser, use browser_network_requests to audit every fetch/XHR for failures, slowness, duplicate calls, and suspicious payloads. Use for API-heavy pages and after backend or client networking changes.
When GitHub Actions fails, fetch failing job logs and assign each failing job to a separate subagent that fixes its slice of the problem in parallel. Use for multi-job CI failures where jobs are independent.
Run four parallel read-only subagents that each review the same diff from a different lens — security, performance, correctness, and readability — then merge findings into one report. Use before merging large or risky PRs.
Execute a user flow step-by-step in Cursor's built-in browser while documenting each action, then emit a Playwright test that replays the same flow using stable selectors derived from the accessibility tree.
| name | monitoring-terminal-errors |
| description | Watch running terminal processes for crashes and stack traces. When an error appears, navigate to the failing file and line, diagnose, and fix it automatically. |
| user-invocable | true |
Continuously watch a running process (dev server, test runner, build) for errors and fix them as they appear.
List terminal files and find the one running the target process:
head -n 10 <terminals_folder>/*.txt
Look for terminals running dev servers (npm run dev, pnpm dev, python manage.py runserver, etc.).
Read the full terminal file content. Search for error patterns:
at <function> (<file>:<line>:<col>)Error:, TypeError:, ReferenceError:, ENOENT, ECONNREFUSEDTraceback (most recent call last): followed by File "<path>", line <n>Unhandled Runtime Error, Error: ..., Module not foundERROR in, Failed to compile, SyntaxError[vite] Internal server error:error TS\d+:From the stack trace, extract:
For Node.js: at functionName (/path/to/file.ts:42:10)
For Python: File "/path/to/file.py", line 42, in function_name
If the server is still showing errors after the fix, repeat from step 2. Stop when:
exit_code in the terminal file footer — if present, the process has crashed entirely and needs a restart