القائمة
Use this skill when unskipping a test that was previously skipped.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/ChromeDevTools/devtools-frontend --skill fixing-skipped-testsيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
عرض SKILL.md
| name | fixing-skipped-tests |
| description | Use this skill when unskipping a test that was previously skipped. |
This skill outlines the workflow for fixing skipped tests in the DevTools codebase, typically given a Chromium bug link (e.g., crbug.com/1234567).
Extract the Bug ID
crbug.com/<bugid>. Extract the <bugid> from the link.Create a Branch
fixed-<bugid>.devtools-version-control skill to create and switch branches appropriately.Search for the Skipped Tests
test/TestExpectations file for the <bugid> to find skipped tests..skip in the code, but rather by having a [ Skip ] expectation in test/TestExpectations.Iterative Fix Process
[ Skip ] expectation for one of the tests associated with the bug in test/TestExpectations (or change it to [ Pass Failure ] if you are investigating flakiness).npm run test path/to/foo.test.ts:test_name) using the guidelines from the devtools-verification skill. If you are dealing with flaky tests, you can use the --repeat=x flag (e.g. npm run test -- --repeat=20 path/to/foo.test.ts:test_name) to run the test multiple times to reproduce the flakiness. This flag works for both E2E and unit tests.[crbug.com/<bugid>] prefix from the test name string in the code if it is present.// TODO(crbug...): Flaky).test/TestExpectations, and verifying until all are passing.Verify Full Build
Interacts with the public Gerrit Code Review platform using depot_tools' gerrit_client.py. Use this skill when asked to query public CLs, retrieve published review comments, inspect formatted patches or complete file revisions, add patchset comments, vote on review labels, submit changes, or abandon/restore public CLs. Do not use this skill for Google-internal attention set updates or internal AI-assisted code reviews (CRUAS), which are unsupported by the public API.
Refactor user-facing UIStrings and localization comments in a DevTools module folder according to UX writing guidelines (child task of b/40799900). Use when simplifying wording, checking sentence case, or improving L10n comments in UIStrings for a specific folder or issue. Don’t use for general code changes or non-UIStrings files.
Triage and analyze Chromium/DevTools LUCI build results and trybot failures, including high-level builder status, compile errors, and detailed test failures. Use this to inspect trybot buildbucket (bb) results for a patchset overview or to query ResultDB directly for comprehensive, actionable information about specific test regressions and infrastructure issues.
استنادا إلى تصنيف SOC المهني
