Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

repo-exploration

Estrelas0

Forks0

Atualizado13 de abril de 2026 às 06:08

Use before any implementation to understand the codebase structure, existing patterns, dependency graph, and project conventions.

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

screenleon

screenleon/CV-generate

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	repo-exploration
description	Use before any implementation to understand the codebase structure, existing patterns, dependency graph, and project conventions.

Repo Exploration

Use this skill to build a mental model of the codebase before making changes.

Required steps

1. Structural discovery

List the top-level directory structure.
Identify the module map: where handlers, services, repositories, models, and tests live.
Read ARCHITECTURE.md, CONTRIBUTING.md, or equivalent docs if they exist.

2. Pattern identification

Read at least one existing file in each layer you will modify and note:

Naming convention (files, functions, variables, types)
Error handling pattern (custom error types? wrapped errors? error codes?)
Logging pattern (structured? which library?)
Test convention (table-driven? test fixtures? mocks or fakes?)
Import organization (stdlib first? grouped? aliased?)

3. Dependency graph

Before cross-file changes:

Trace imports from the file you will change.
Identify shared types, interfaces, and constants.
Check for circular dependency risks.

4. Constraint check

Read docs/operating-rules.md → Project-specific constraints section.
Read DECISIONS.md if it exists.
Do not introduce patterns that contradict recorded decisions.

Output

After discovery, produce a brief summary:

Modules involved: [list]
Existing patterns: [key observations]
Constraints: [project-specific rules that apply]
Files to read before coding: [list]

Use this skill when

Starting work on an unfamiliar module
The task touches more than 2 files
You are unsure about the project's conventions
A previous attempt produced code that did not match the project style

Mais deste repositório

mesmo repositório

application-implementation

screenleon/CV-generate

Use for general product implementation work that is not primarily backend architecture, pure integration wiring, or screenshot-driven design-to-code.

2026-04-130

backend-change-planning

screenleon/CV-generate

Use when backend work requires contract-first thinking, schema changes, permission checks, side-effect analysis, or test planning.

2026-04-130

demand-triage

screenleon/CV-generate

Use immediately after codebase discovery to classify task scale and determine which workflow steps are required vs. optional.

2026-04-130

design-to-code

screenleon/CV-generate

Use when the user provides screenshots, mockups, or design assets and wants implementation that stays visually close to the source.

2026-04-130

documentation-architecture

screenleon/CV-generate

Use when the main deliverable is maintainable documentation such as repository rules, onboarding guides, runbooks, ADRs, or architecture notes.

2026-04-130

error-recovery

screenleon/CV-generate

Use when encountering compile errors, test failures, runtime exceptions, or unexpected behavior during implementation.

2026-04-130

name	repo-exploration
description	Use before any implementation to understand the codebase structure, existing patterns, dependency graph, and project conventions.

Repo Exploration

Use this skill to build a mental model of the codebase before making changes.

Required steps

1. Structural discovery

List the top-level directory structure.
Identify the module map: where handlers, services, repositories, models, and tests live.
Read ARCHITECTURE.md, CONTRIBUTING.md, or equivalent docs if they exist.

2. Pattern identification

Read at least one existing file in each layer you will modify and note:

Naming convention (files, functions, variables, types)
Error handling pattern (custom error types? wrapped errors? error codes?)
Logging pattern (structured? which library?)
Test convention (table-driven? test fixtures? mocks or fakes?)
Import organization (stdlib first? grouped? aliased?)

3. Dependency graph

Before cross-file changes:

Trace imports from the file you will change.
Identify shared types, interfaces, and constants.
Check for circular dependency risks.

4. Constraint check

Read docs/operating-rules.md → Project-specific constraints section.
Read DECISIONS.md if it exists.
Do not introduce patterns that contradict recorded decisions.

Output

After discovery, produce a brief summary:

Modules involved: [list]
Existing patterns: [key observations]
Constraints: [project-specific rules that apply]
Files to read before coding: [list]

Use this skill when

Starting work on an unfamiliar module
The task touches more than 2 files
You are unsure about the project's conventions
A previous attempt produced code that did not match the project style