'does' 검색 결과

지정한 커밋이나 브랜치를 기준으로 코드 변경을 검토합니다. 문서화된 개발 규칙 준수와 요구 사항 구현을 별도로 확인하고 두 관점의 지적 사항을 나누어 보고합니다.

• 브랜치나 PR의 변경 검토
• 지정 커밋이나 태그 이후 변경 확인
• 문서화된 개발 규칙과 대조

아직 없는 기능을 조사와 계획부터 테스트 우선 구현, 검토, 커밋까지 진행합니다. 단계별로 ECC 에이전트에 작업을 나누고 계획 승인과 커밋 전 확인을 거칩니다.

• 아직 구현되지 않은 기능 추가
• 테스트를 먼저 작성하는 새 기능 개발
• 인증 기능의 보안 검토

Add Storybook to a project that does not have it configured, choosing the installation tag based on the latest stable version. Then use the separate setup skill to configure Storybook for the project.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding Storybook to a project for the first time
• Choosing an installation tag based on the stable release
• Continuing from installation to project-specific setup

Explain tips shown in senpi or omo by checking the installed tip list, user settings, and implementation code. Learn what a feature actually does, why a tip appears, and which tips your setup can show.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Understand a Tip: line shown during a session
• Check which tips your settings allow
• Explore how model fallback guidance works

Organize existing ChatGPT Pages and Spaces around the work readers need to do. The skill reviews page structure, moves pages, consolidates duplicate content, and improves navigation while preserving distinct requirements, historical context, and relevant layout details.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Organizing too many top-level Pages
• Consolidating duplicate task lists
• Separating active work from dated notes and reference material

Provide Jarvis with a static catalog of system voices through the included voice_source.json file. This skill supplies reference data only; it does not provide a workflow for choosing voices, handling voice requests, or creating widgets.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Supply Jarvis with its system voice catalog
• Check the catalog file included with the skill
• Determine whether the skill includes a voice-selection workflow

Add a new exchange integration to CCXT using TypeScript and established exchange templates. Follow guidance for unified methods, data conversion, authentication, sandbox settings, recorded API test data, documentation, and checks across generated language implementations.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Add an exchange that CCXT does not yet support
• Convert exchange responses into CCXT's common data format
• Record real API responses for regression tests

Find and read documents, code, papers, and notes stored in OpenViking. The skill chooses a search method, uses directory summaries to locate relevant files, and cites resource addresses so readers can open the supporting material.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking requirements in a saved design document
• Finding files by an error message or exact term
• Locating relevant passages in stored papers and notes

Find relevant past execution experience in OpenViking before starting a task. Check when each experience applies and when it does not, then load suitable guidance while giving current facts, policies, and tool results priority.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find past experience relevant to a new task
• Exclude guidance that does not fit current conditions
• Recheck past guidance against current tool results

Guides HTTP integration with the agentmemory server for saving and searching knowledge. It explains authentication, request conventions, and endpoint references, including how to connect systems that do not support MCP, the agent tool connection protocol.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Saving and searching knowledge over HTTP
• Connecting a host that does not support MCP
• Checking authentication and response conventions

Coordinate compliance work across multiple standards and regulations. Use a company profile to identify relevant frameworks, map shared controls, prepare mock audits, and build a unified evidence checklist showing where documents can be reused.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Starting a compliance program across multiple frameworks
• Planning an annual audit calendar
• Preparing for a certification audit

Explore relationships between functions and files using a prebuilt code graph, a map of code dependencies. Trace bugs, inspect callers and execution paths, and assess the impact of refactoring or proposed changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Explore callers and dependencies in unfamiliar code
• Trace a bug across multiple files
• Assess the impact of renaming or removing code

Add business knowledge missing from a Wren project's database definitions. Compare source documents with existing context, then add explanations, rules, SQL examples, and proposed metrics through guided questions or an automatic mode with an audit report.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Documenting status codes, units, and NULL meanings
• Adding business knowledge from handbooks and glossaries
• Defining aggregation metrics such as ARR or DAU

Compare internal AI policies with saved assessments, vendor reviews, and proposed uses. Identify missing or conflicting commitments, draft policy wording, and suggest when updates and use case records need attention.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing policy gaps against approved AI practices
• Checking a proposed AI use before launch
• Drafting policy updates with clear priorities

Investigate unfamiliar codebases before fixing bugs, adding features, or refactoring. Follow relevant code paths, plan focused changes, and verify results, while recording useful discoveries in .notebook/ so later sessions can build on earlier investigation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigate and fix bugs in unfamiliar code
• Add features following existing project conventions
• Trace and document authentication or other flows

Helps users get started with Onchain OS, find OKX.AI role registration guidance, or reach support resources. It identifies the purpose of a question and routes it to the appropriate guide.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Getting started with Onchain OS
• Finding OKX.AI role registration guidance
• Finding support for bugs, complaints, or feedback

Compare a competitor's estimated search rankings with your Search Console data. Find missing keywords and terms where you trail, then get page suggestions and a prioritized action list based on search volume and product relevance.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find content topics covered by competitors
• Identify existing pages that need improvement
• Prioritize keywords by volume and product relevance

How to work in a Personal CRM project (the `entity-vault` starter pack, GBrain-compatible): a typed-entity vault of people, companies, meetings, and concepts, each a dossier with a rewritable summary plus an append-only timeline. Read when the project has these folders, OR when asked to capture notes about a person or company, log a meeting, prep for an upcoming meeting, or answer who someone is and what was last said. Carries the dossier convention and entity-extraction behaviors so that guidance does not live inside template bodies or folder descriptions. Complements the platform `open-knowledge` skill; does not replace it.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

How to work in a Worldbuilding project (the `worldbuilding` starter pack): a fiction encyclopedia of characters, settings, themes, factions, and lore. Read when the project has these folders, OR when asked to add a character, setting, faction, or piece of lore, or to check the world for internal consistency. Carries the auto-stub and consistency behaviors so that guidance does not live inside template bodies or folder descriptions. Complements the platform `open-knowledge` skill; does not replace it.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

How to work in a Writing Pipeline project (the `writing-pipeline` starter pack): a three-stage drafting flow, ideas → drafts → published. Read when the project has these folders, OR when asked to capture an idea, start or revise a draft, review a piece before it ships, or publish it. Carries the stage flow and review behaviors so that guidance does not live inside template bodies or folder descriptions. Complements the platform `open-knowledge` skill; does not replace it.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

How to work in a Software Lifecycle project (the `software-lifecycle` starter pack): proposals → decisions → specs → postmortems, plus guides. Read when the project has these folders, or when asked how this project is organized. Carries the doc lifecycle, status flows, and per-folder agent behaviors so that guidance does not live inside template bodies or folder descriptions. The five workflows — frame a proposal, write a spec, record a decision, write a postmortem, review a design — each ship as their own sibling skill in this pack. Complements the platform `open-knowledge` skill; does not replace it.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

How to work in a Knowledge Base project (the `knowledge-base` starter pack). Read when the project has the three-layer source-grounded layout — `external-sources/` → `research/` → `articles/` — or when asked how this project is organized. Carries the layer model, per-folder rules, status flows, and log discipline so this guidance does NOT live inside template bodies or log.md. The three procedures live elsewhere: ingest in the platform `open-knowledge` skill, research and consolidate as their own sibling skills in this pack. Complements the platform `open-knowledge` skill; does not replace it.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill to queue maintainer-accepted microsoft/apm issues (`status/accepted`) and fan them out through an isolated pool (default 2) of autopilot-issue-delivery-worker sessions. Any accepted type is eligible. Advisory `triage/recommended` is not authorization. Does not triage. Does not review PRs. Works in a local session, Copilot App automation, Cloud Agent, Remote Agent, or Agentic Workflow.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill whenever a pull request is opened, reopened, or synchronized in microsoft/apm to assess whether and how the documentation corpus must change to stay truthful with the proposed code change. Activate even when the PR title or body says nothing about docs -- the skill must run on every PR to detect silent drift between code and docs. Classifies impact as no-change, in-place edit (one to a few paragraphs), or structural change (new page or TOC reshape), then orchestrates a CDO + doc-writer + python-architect + editorial-owner + growth-hacker loop to produce a patch-ready advisory. Does NOT review code quality, security, or test coverage. Does NOT auto-merge or auto-push doc edits.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.