1.6천건 · 관련도순
Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Core module implementation for claude-flow v3. Implements DDD domains, clean architecture patterns, dependency injection, and modular TypeScript codebase with comprehensive testing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create or revise the SDD Composy technical specification (tasks/prd-SLUG/techspec.md) from the approved PRD, resolved stories, and mapped codebase, with DEC/RISK and TU/TI/E2E traceability and a human gate. Use when the product contracts are approved and architecture is needed — 'criar a spec técnica', 'techspec do prd-SLUG', 'design the solution for…'. Do NOT use to change product scope, before PRD and stories approval, or for design notes outside SDD.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Produce a deterministic, read-only evidence map of the repository for SDD Composy (languages, manifests, commands, modules, boundaries, staleness) and publish the context bundle only on request. Use before a PRD or TechSpec, or when the map is stale — 'mapear o repositório', 'atualizar o contexto do código', 'what does this codebase look like for SDD'. Do NOT use for architecture decisions, code review, or repository exploration without an SDD workspace.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user wants to set up pwdev-feat in a project — 'inicializar o pwdev-feat', 'configurar o feat', 'init feat workspace' — choosing language, model profile and the optional audit trail, and creating the .planning/feat/ workspace. Do NOT use to analyze the codebase (feat-map), to write the project instructions file (feat-setup) or to create plans.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks for the state of pwdev-feat plans — 'status do feat', 'quais planos estão pendentes', 'show feature status' — listing pending, complete, with-caveats, failed and resumable plans plus codebase-context health. Read-only. Do NOT use to execute (feat-exec) or query the audit trail (feat-audit).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user wants the project instructions file generated or updated from the detected stack and conventions — 'gerar o arquivo de instruções do projeto', 'criar convenções do projeto', 'setup governance', 'gerar AGENTS'. Writes the shared instructions file read by Claude Code, Codex, Hermes and OpenCode. Do NOT use to analyze the codebase in depth (feat-map) or to initialize the workspace (feat-init).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a repository has no PWDEV Power workspace yet, when resuming one, when the codebase map needs refreshing, or when the setup should be checked
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write type-safe TypeScript code with strict mode enabled, comprehensive type definitions, proper error handling, and elimination of any types. Use when enabling TypeScript strict mode, adding types to existing JavaScript, fixing type errors, creating type definitions, using utility types, implementing type guards, avoiding any types, creating generic types, or ensuring complete type safety across the codebase.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Establish and enforce coding standards, best practices, and architectural patterns across the codebase using linters, formatters, and code review processes. Use when setting up ESLint/Prettier, configuring linting rules, creating code style guides, implementing pre-commit hooks, establishing naming conventions, enforcing TypeScript strict mode, maintaining consistency, conducting architecture reviews, or defining team coding standards.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Code quality dashboard. Wraps existing project tools (type checker, linter, test runner, dead code detector, shell linter), computes a weighted composite 0-10 score, and tracks trends over time. Use when: "health check", "code quality", "how healthy is the codebase", "run all checks", "quality score". (gstack)
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate comprehensive technical documentation for developers taking over an AEM Edge Delivery Services project. Analyzes codebase structure, custom implementations, design tokens, and produces a complete developer guide.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, or `zoom-out` — or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Harvest every `ponytail:` comment in the codebase into a debt ledger, so the deliberate shortcuts and deferrals ponytail leaves behind get tracked instead of rotting into "later means never". Use when the user says "ponytail debt", "/ponytail-debt", "what did ponytail defer", "list the shortcuts", "ponytail ledger", or "what did we mark to do later". One-shot report, changes nothing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive onboarding process for new developers. Use when helping someone get set up with a codebase, configuring development environments, or creating onboarding documentation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Remove AI-generated code slop and improve code quality. Use when you need to clean up AI-written code, remove unnecessary defensive patterns, eliminate inconsistent comments, or align code style with the rest of the codebase.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Multi-agent exploration and task delegation for complex areas of interest. Use when you need to deeply explore a codebase area, gather information from multiple perspectives, or delegate parallel research tasks for comprehensive analysis.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Read all suggested PR changes and apply them directly to the codebase. Use when you have PR review comments to address, suggested changes to implement, or feedback to incorporate into your code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Initialize AGENTS.md documentation for a codebase. Use when setting up a new repository for AI coding assistants, creating project documentation for Claude Code or Cursor, or improving existing AGENTS.md files.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Bootstrap full agent infrastructure for an existing, already-coded project without modifying a single line of source code. Surveys the repo, infers conventions from manifests, README, git history, and source samples, then generates the missing AGENTS.md, docs/architecture.md, docs/product-soul.md, ADR backfill, and seeded docs/memory/ files. Asks the user only about gaps the repo cannot reveal. Load when the user asks to "retroactive project setup", "backfill agent infrastructure", "bootstrap agents for this existing repo", "onboard agents to a legacy codebase", "set up agents without touching code", or "fill in missing agent context for this project".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate a tailored AGENTS.md for any new project by interviewing the user about their skill gaps, project goals, and tech context. Load when the user asks to set up a project, initialize agents, create an AGENTS.md, bootstrap a repo, onboard agents to a codebase, or says "set up this project for agents". Also triggers on "write an AGENTS.md for this project", "configure agents for my repo", "project bootstrap", "agent onboarding", or when the user starts a new project and needs agent-ready configuration. Re-run when new context arrives (PRD written, stack changes, team changes) to update the AGENTS.md.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Map symbol dependencies, callers, and blast radius before editing code. Load when the user asks what depends on a symbol, what breaks if they change something, blast radius of a change, reverse dependencies, or which tests cover a function. Also triggers on "who calls this", "impact of changing", "dependency map", "what uses this", "find callers", or before any non-trivial edit when safe-change is not yet active. Pairs with codebase-understanding for broad architecture; this skill is symbol-scoped and edit-gated.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.