Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

review

Estrelas3

Forks0

Atualizado23 de maio de 2026 às 07:51

Code-review specialist for the Vue SSR Starter Kit (e-xode/vue-ssr). Performs a structured, severity-categorized review of a branch, PR, or uncommitted diff against the project's documented conventions and skills. Read-only — never modifies code. Delegate to this agent whenever the user asks to review, code-review, audit a branch/PR, check changes against conventions, or wants a second opinion on a diff before merge. Returns a markdown report tagged with anomaly types (security, bug, regression, perf, i18n, convention, test-gap). Don't use for: making code changes (do it yourself or use task agents), post-task validation (→ vue-ssr-hooks + hooks agent), Claude config audit (→ claude-anthropic).

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

e-xode

e-xode/vue-ssr

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

Explorador de arquivos

2 arquivos

SKILL.md

readonly

name

review

description

Review

Read-only structured code review against project conventions.

Severity rubric

Level	Meaning	Action
🔴 Critique	Bug, security issue, data loss risk	Must fix before merge
🟠 Important	Convention violation, potential regression	Should fix
🟡 Medium	Suboptimal pattern, missing edge case	Consider fixing
🟢 Minor	Style, naming, minor improvement	Optional
ℹ️ Info	Observation, question, suggestion	No action required

Anomaly types

security, bug, regression, perf, a11y, i18n, convention, test-gap, docs-gap, typo

Procedure

Confirm scope — branch diff, PR diff, or uncommitted changes
Inventory the diff — git diff --stat, --name-only, full content
Review against conventions — check CLAUDE.md rules, relevant skills
Classify findings — severity + anomaly type + file:line + evidence
Output report — sorted by severity (🔴 → ℹ️), then by file

Conventions to check

No code comments (CLAUDE.md rule)
SCSS externalized (separate .scss file)
i18n mandatory (no hardcoded text)
SCSS variables (no hardcoded colors/spacings)
ObjectId validation (parseObjectId before queries)
catch blocks (console.error, never empty)
Composition API only (script setup)
Shared factorization (no duplication)

Output format

## Code Review — [scope description]

### 🔴 Critique (N)

- **[file:line]** [anomaly-type] Description. Evidence: `code snippet`.

### 🟠 Important (N)

...

### Summary

| Severity | Count |
| -------- | ----- |
| 🔴       | N     |
| 🟠       | N     |
| 🟡       | N     |
| 🟢       | N     |
| ℹ️       | N     |

**Recommendation:** merge as-is / fix critique+important / request changes

Hard constraints

Never modify code
Never run lint/build/test
Every finding must cite a source (CLAUDE.md rule, skill, or objective concern)
No subjective taste opinions

Mais deste repositório

mesmo repositório

vue-ssr-architecture

e-xode/vue-ssr

Architecture reference for the Vue SSR Starter Kit (e-xode/vue-ssr): Vue 3.5+ + Vite 7 + Express 5 + MongoDB 7 + Vuetify 4 + Pinia + Vue Router with locale-prefixed routing. Covers file structure, SSR lifecycle (entry-server/entry-client/renderToString), locale routing system (useLocalePath, /:locale(en|fr)/), layout system (public/minimal/app), shared utilities inventory (apiFetch, parseObjectId, dbHelpers, email, security), API endpoint patterns (setupXRoute), view/component naming, Vuetify gotchas, and environment variables. Trigger on any architecture question, file placement, new feature scaffolding, routing, SSR, or shared utility usage. Don't use for: auth flow details (→ vue-ssr-auth), Docker/CI deployment (→ vue-ssr-deployment), post-task validation (→ vue-ssr-hooks), UI/UX design (→ design agent).

2026-07-183

vue-ssr-hooks

e-xode/vue-ssr

Post-task validation system for the Vue SSR Starter Kit: the hooks agent runs a format → lint → build → test battery via the single `npm run validate` orchestrator, on user opt-in only. Covers the opt-in trigger (never automatic), the validate.mjs orchestrator (parallel stages, prettier/eslint --cache, git-digest sentinel skip), the short-circuit table (skip validation for non-code files, build only on .vue/.js), the dormant settings._json hooks, and the subagent validation blocker. Trigger on: validation failures, understanding why lint/build/test ran or didn't run, modifying the validation pipeline. Don't use for: app code architecture (→ vue-ssr-architecture), auth (→ vue-ssr-auth), deployment (→ vue-ssr-deployment), Claude config governance (→ claude-anthropic).

2026-07-183

brand-art-direction

e-xode/vue-ssr

Material Design 3 / Vuetify 4 art-direction charter for the Vue SSR Starter Kit (e-xode/vue-ssr): the opinionated, screenshot-verifiable brand-identity layer above design-scss and design-ux. Defines the clean-minimal direction (single indigo brand accent, neutral-gray chrome, bordered flat MD3 surfaces, 8px rhythm, restraint over decoration) as DECIDABLE screenshot-checkable systems: quiet surface rhythm, canonical hover/elevation per component archetype with sibling consistency, palette roles, decorative restraint, and an evidence-based pre-delivery checklist graded by the visual-qa agent. Trigger on ANY visual/finition or polish work on rendered views: card hovers, surface backgrounds, elevation, accent usage, hero/CTA styling. Load BEFORE design-scss/design-ux when styling views. Don't use for: SCSS token/mixin mechanics (→ design-scss), UX methodology (→ design-ux), Vuetify component API (→ vuetify-components), design routing (→ vue-ssr-design), marketing copy (→ content-strategy).

2026-06-063

content-strategy

e-xode/vue-ssr

Editorial method and content operations for the Vue SSR Starter Kit (e-xode/vue-ssr): the how-to-produce layer on top of the marketing-content facts, for content that markets the open-source kit. Covers the editorial workflow (research, propose, draft FR+EN, verify, optimize), operational tone and voice (Avoid/Prefer, no arrow character, bilingual discipline), per-channel playbooks (LinkedIn posts and long-form articles, landing/contact page copy via i18n, the GitHub/npm README storefront), audience personas and angles, the content inventory glossary (anti-duplication, follow-up radar), the editorial backlog, and the daily growth/SEO advisory playbook. Trigger when writing or improving a LinkedIn post or article, page marketing copy, README/storefront copy, brainstorming content ideas, or asking what to do today for content/SEO. Don't use for: canonical product/stack/feature facts (→ marketing-content), i18n key placement (→ translate), meta/JSON-LD/sitemap (→ seo), visuals or layout (→ design).

2026-06-063

marketing-content

e-xode/vue-ssr

Marketing and product-knowledge FACTS for the Vue SSR Starter Kit (e-xode/vue-ssr): the source of truth for acquisition content that markets the open-source kit itself. Covers the canonical content rules (bilingual FR+EN, humble tone, concrete numbers, never the → arrow character), where assets live (src/assets/linkedin/, page copy via i18n, the GitHub/npm storefront), and product facts: what the kit is (Vue 3.5 + Vite + Express 5 + MongoDB 7 + Vuetify 4 SSR boilerplate with auth, i18n, admin), its stack/version snapshot (authoritative source = package.json), feature inventory, and differentiator (a curated Claude Code agent/skill fleet). Trigger when you need the facts behind acquisition content: what the kit is, its features, stack, positioning, audience, license, repo/npm location, or asset locations. Don't use for: the editorial method, tone/voice, inventory/backlog and writing workflow (→ content-strategy), i18n keys (→ translate), page meta/structured data (→ seo), visual/layout design (→ design).

2026-06-063

marketing-strategy

e-xode/vue-ssr

Pure-marketing strategy for the Vue SSR Starter Kit (e-xode/vue-ssr): the strategic layer above the content factory, for marketing the open-source MIT kit. Owns global strategy, the no-price monetization model (the kit is free; success = developer adoption that funnels inbound to E-XODE services), campaign planning, channel and social strategy (LinkedIn, GitHub, dev.to, Reddit r/vuejs, npm), positioning and ICP, competitive analysis, and growth/funnel thinking (stars, installs, forks). Decisions persist as references (positioning, pricing, campaigns, gtm, competitive) and are handed to the content agent. Trigger when defining strategy, the monetization stance, planning a campaign, choosing channels, analysing competitors, or reasoning about the adoption funnel. Don't use for: writing the actual posts/articles/README/page copy (→ content agent + content-strategy), product facts (→ marketing-content), i18n keys (→ translate), meta/JSON-LD/sitemap (→ seo), code (→ vue/server), visuals (→ design).

2026-06-063

name

review

description

Review

Read-only structured code review against project conventions.

Severity rubric

Level	Meaning	Action
🔴 Critique	Bug, security issue, data loss risk	Must fix before merge
🟠 Important	Convention violation, potential regression	Should fix
🟡 Medium	Suboptimal pattern, missing edge case	Consider fixing
🟢 Minor	Style, naming, minor improvement	Optional
ℹ️ Info	Observation, question, suggestion	No action required

Anomaly types

security, bug, regression, perf, a11y, i18n, convention, test-gap, docs-gap, typo

Procedure

Confirm scope — branch diff, PR diff, or uncommitted changes
Inventory the diff — git diff --stat, --name-only, full content
Review against conventions — check CLAUDE.md rules, relevant skills
Classify findings — severity + anomaly type + file:line + evidence
Output report — sorted by severity (🔴 → ℹ️), then by file

Conventions to check

No code comments (CLAUDE.md rule)
SCSS externalized (separate .scss file)
i18n mandatory (no hardcoded text)
SCSS variables (no hardcoded colors/spacings)
ObjectId validation (parseObjectId before queries)
catch blocks (console.error, never empty)
Composition API only (script setup)
Shared factorization (no duplication)

Output format

## Code Review — [scope description]

### 🔴 Critique (N)

- **[file:line]** [anomaly-type] Description. Evidence: `code snippet`.

### 🟠 Important (N)

...

### Summary

| Severity | Count |
| -------- | ----- |
| 🔴       | N     |
| 🟠       | N     |
| 🟡       | N     |
| 🟢       | N     |
| ℹ️       | N     |

**Recommendation:** merge as-is / fix critique+important / request changes

Hard constraints

Never modify code
Never run lint/build/test
Every finding must cite a source (CLAUDE.md rule, skill, or objective concern)
No subjective taste opinions