القائمة
Turn a report into something reproducible, or say precisely what is missing.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
استنادا إلى تصنيف SOC المهني
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/vstorm-co/agenticos --skill bug-report-triageيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
عرض SKILL.md
| name | Bug report triage |
| description | Turn a report into something reproducible, or say precisely what is missing. |
| category | qa |
An unreproducible bug is not fixed, it is closed. The job is reproducibility.
Exact steps in order · what happened · what was expected · environment, version and browser · frequency — always, sometimes, once · when it started and what changed then · does it happen for other users or other tenants.
Bug — it does not do what it says. Regression — it used to work; find the version. Missing feature — it never worked; say so plainly rather than accepting it as a bug. Works as designed — and the design surprised somebody, which is worth its own ticket.
Not from how annoyed the reporter is. Say the reasoning so it can be argued with.
Either a numbered reproduction, or a specific list of what is still needed. "Can you provide more information" produces nothing.
Close for inactivity without saying what was missing, or merge two reports because the symptoms look alike.
Work with messaging-channel bots — Telegram, Slack or Mattermost. Register a bot, route inbound messages through an agent, choose webhook vs polling, handle an @slug mention, or add a new channel adapter. Use when wiring chat into a messaging platform or debugging bot delivery, identity linking or "the bot answered as itself".
Change the agent spec — add or remove a field, rename one, tighten a rule, bump SPEC_VERSION, change publish-time validation, or touch YAML export/import. Use whenever editing app/agents/spec.py or anything that reads a stored spec. Every published agent and every client git repository holds a copy of this format, so a change that only works forwards breaks agents nobody touched.
Work with MCP servers — connect one, add an entry to the server catalog, debug "the agent cannot see my MCP tools" or a failing OAuth flow, or change how connections are probed, prefixed or filtered. Use when the ask involves an external SaaS tool (GitHub, Linear, Notion, Slack, Stripe, Postgres…) and before writing a capability that would just be an API client for one.