Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

review-skills

Estrelas8

Forks35

Atualizado3 de abril de 2026 às 13:53

Review project AI skills for duplication, stale references, mistakes, and structural issues. Use when the user asks to review skills, audit skills, check for duplicate skills, or verify skill quality.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

openshift

openshift/lightspeed-console

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Analistas de garantia de qualidade de software e testadoresInformática e Matemática·SOC 15-1253

SKILL.md

readonly

name	review-skills
description	Review project AI skills for duplication, stale references, mistakes, and structural issues. Use when the user asks to review skills, audit skills, check for duplicate skills, or verify skill quality.

Review Skills

Read every SKILL.md under .cursor/skills/ (and any files they reference). Check for:

Structural issues — missing/malformed frontmatter, referenced supporting files that don't exist.
Duplication — skills that overlap significantly or could be merged.
Stale references — file paths, npm scripts, branch names, or source symbols that no longer exist in the repo. Verify each against the actual codebase.
Mistakes — typos, incorrect commands, contradictions between skills.
Consistency — shared steps (e.g. lint/i18n/build) described differently, inconsistent terminology for the same concept.

Report

Group findings by skill. Use 🔴 error / 🟡 warning / 🟢 suggestion. Omit clean skills. End with: Reviewed N skills. M have issues.

Mais deste repositório

mesmo repositório

test

openshift/lightspeed-console

Run end-to-end tests filtered by tag. Use when the user asks to run tests, run Playwright, or test a specific feature tag like @core or @attach.

2026-06-018

unused-exports

openshift/lightspeed-console

Find exported symbols that are never imported by another file. Use when the user says "check exports", "unused exports" or asks to clean up exports.

2026-05-158

code-review

openshift/lightspeed-console

Review a pull request for code quality, correctness, and project conventions. Use when the user asks to review a PR, code review, or examine changes on a branch. Accepts a GitHub PR URL, PR number, or local branch name.

2026-04-208

rebase

openshift/lightspeed-console

Rebase the current branch onto its base branch, resolve all conflicts, and verify lint, i18n, and build pass. Use when the user asks to rebase, update, or sync a branch with its upstream base.

2026-04-208

backport

openshift/lightspeed-console

Backport commits or PRs from main to a release branch. Use when the user asks to backport, cherry-pick, or port changes between branches, or when resolving conflicts from a cherry-pick onto a release branch.

2026-04-108

release

openshift/lightspeed-console

Bump the project version across all release branches and commit the changes. Use when the user asks to do a release or update the version on all branches.

2026-04-108

name	review-skills
description	Review project AI skills for duplication, stale references, mistakes, and structural issues. Use when the user asks to review skills, audit skills, check for duplicate skills, or verify skill quality.

Review Skills

Read every SKILL.md under .cursor/skills/ (and any files they reference). Check for:

Structural issues — missing/malformed frontmatter, referenced supporting files that don't exist.
Duplication — skills that overlap significantly or could be merged.
Stale references — file paths, npm scripts, branch names, or source symbols that no longer exist in the repo. Verify each against the actual codebase.
Mistakes — typos, incorrect commands, contradictions between skills.
Consistency — shared steps (e.g. lint/i18n/build) described differently, inconsistent terminology for the same concept.

Report

Group findings by skill. Use 🔴 error / 🟡 warning / 🟢 suggestion. Omit clean skills. End with: Reviewed N skills. M have issues.