Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/openshift/console --skill test명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
Review changes to the OpenShift Console plugin API for compliance with contribution guidelines, styleguide, and proper documentation in changelogs. Provides a detailed report of findings and compliance score.
Audit all Claude Code skills for stale references, broken paths, and deprecated tool names
Migrate a Cypress test file (.cy.ts) or Gherkin feature file (.feature) to Playwright following Console's architecture. This is the ONLY skill for Cypress-to-Playwright conversion work, you can perform full migration, analysis-only (--analyze), or dry-run (--dry-run) modes.
| name | test |
| description | Run tests (frontend, backend, unit, or all) |
| argument-hint | [frontend|backend|unit <name>|all] |
Run tests based on the arguments provided:
$ARGUMENTS contains "frontend", run ./test-frontend.sh$ARGUMENTS contains "backend", run ./test-backend.sh$ARGUMENTS contains "unit", run cd frontend && yarn test and pass any additional arguments after "unit"$ARGUMENTS contains "all", run ./test-frontend.sh first (to generate i18n files), then run ./test-backend.shNote: When running all tests, the frontend tests must run first because they generate i18n localization files. If the backend tests run in parallel during i18n generation, the backend vendor check will detect these generated files as git changes and fail.
Examples:
/test or /test all - Run all tests/test frontend - Run frontend tests only/test backend - Run backend tests only/test unit - Run Jest unit tests/test unit MyComponent - Run Jest unit tests matching "MyComponent"/test frontend backend - Run both frontend and backend testsReport the results from the test suite(s). If any tests fail, troubleshoot the failures and fix them.
SOC 직업 분류 기준
