'entry' 검색 결과

Turn presentation requirements, supplied documents, and completed research into one editable Markdown outline. Define the overall argument, each slide’s conclusion and evidence, and the connections between slides, then update the same outline when revisions are requested.

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

• Build a presentation outline from multiple documents
• Organize each slide’s conclusion and supporting evidence
• Revise an outline while preserving requested slide order

Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.

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

Scaffold a new SciAgent-Skills entry. Picks pipeline/toolkit/database/guide template, creates skills/{category}/{name}/SKILL.md with valid frontmatter, appends the registry.yaml entry, runs validation. Enforces name uniqueness, kebab-case, description keyword rules, schema rules from AGENTS.md. TRIGGER when user says (any language): "add a SciAgent skill", "add a skill for <X>", "create new skill", "create a SKILL.md for <X>", "scaffold a skill", "new skill entry", "register a skill", "신규 skill 추가", "스킬 만들어줘", "스킬 생성", "skill 만들어", or any request to add a new SKILL.md to this repo. ALWAYS invoke this skill BEFORE writing to skills/ or registry.yaml. DO NOT TRIGGER when: editing existing entry's content (just edit the file directly); migrating an existing entry (read AGENTS.md "Migrating from Existing Entries" first); only updating registry.yaml without creating a new SKILL.md.

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

Use when setting up, configuring, or troubleshooting Marketing Cloud Journey Builder — including entry sources, activities, decision splits, wait activities, goals, exit criteria, journey versions, test mode, or journey analytics. Triggers: 'journey builder setup', 'entry source configuration', 'decision split not routing', 'exit criteria not removing contacts', 'goal not tracking conversion', 'journey version publishing', 'journey re-entry settings', 'wait activity date field'. NOT for coding a custom activity or entry source — use apex/marketing-cloud-custom-activities. NOT for business units and sender profiles — use admin/marketing-cloud-engagement-setup.

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

Configure and operate NPSP Gift Entry: gift entry templates, batch gift entry, payment processing, donation allocation, and receipting workflows. NOT for a one-time migration of historical gift data — use data/gift-history-import. NOT for soft credits or matching gifts — use admin/soft-credits-and-matching.

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

Write, review, and improve blog posts for the Sentry engineering blog following Sentry's specific writing standards, voice, and quality bar. Use this skill whenever someone asks to write a blog post, draft a technical article, review blog content, improve a draft, write a product announcement, create an engineering deep-dive, or produce any written content destined for the Sentry blog or developer audience. Also trigger when the user mentions "blog post," "blog draft," "write-up," "announcement post," "engineering post," "deep dive," "postmortem," or asks for help with technical writing for Sentry. Even if the user just says "help me write about [feature/topic]" — if it sounds like it could become a Sentry blog post, use this skill.

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

Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.

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

Organize Linear or Jira backlogs through the Composio CLI, a command-line tool. Fetch issues in bulk, group likely duplicates, update labels, priorities, and owners, then share a summary of changes in Slack.

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

• Weekly reviews of unassigned or stale issues
• Post-release bug reviews and owner assignment
• Grouping duplicate reports and linking related issues

Build Node.js, Express, and TypeScript APIs with consistent structure. Separate request handling, business logic, and database access, while following guidance for input validation, error tracking, configuration, and tests when adding features or refactoring existing services.

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

• Adding an API endpoint
• Separating business logic from database access
• Standardizing input validation and error handling

Build a graph of functions and calls across multiple programming languages to investigate entry points, paths to sensitive operations, and potential impact. Use the results to prioritize security reviews and connect external findings with source code.

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

• Tracing call paths from entry points to sensitive functions
• Prioritizing code for a security audit
• Connecting calls across language and RPC boundaries

Maps externally callable smart contract functions that change stored data, then groups them by access restrictions. Produces a structured audit report showing public functions, privileged operations, and access checks that need further review.

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

• Mapping entry points before a smart contract audit
• Listing administrator and role-restricted operations
• Reviewing caller restrictions on callbacks

Analyze strategic interactions in markets, including firm entry, pricing, auctions, and bargaining. Guides equilibrium selection and computation, explains how to handle multiple possible outcomes, and helps assess whether data can identify the model's parameters.

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

• Choosing and computing an equilibrium
• Planning an analysis of firm entry or price competition
• Handling multiple equilibria in empirical models

Decides whether and how to enter a new market — sizing demand from the bottom up rather than from a market report, testing whether your advantage transfers, choosing between organic entry, partnership and acquisition, sequencing the operational and regulatory work that entry actually requires, and setting the criteria that would tell you to stop. Use this to evaluate a new geography, segment or vertical, pressure-test an entry plan, or work out why a launched market never reached scale.

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

Triage Sentry errors: list organizations, projects, and recent issues; resolve, archive, and assign issues. Trigger phrases: sentry, sentry errors, error tracking.

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

Triage new issues in the Sentry `javascript` project by archiving non-actionable noise. Use when asked to "triage issues", "triage the javascript project", "archive non-actionable issues", "triage new frontend issues", or "clean up the sentry/javascript queue". Operates only on the sentry/javascript project, only archives (never resolves), and always archives with `untilEscalating`.

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

Add Temps error tracking to applications using the Sentry-compatible SDK. Temps exposes a Sentry-compatible DSN that works with the official Sentry SDK for each language/framework — no code changes beyond initialization are required. Use when the user wants to: (1) Add error tracking to any app (React, Next.js, Vue, Svelte, Angular, Node.js, Python, Go, Rust, Ruby, Java, PHP, .NET, React Native, Flutter), (2) Wire up uncaught exception and unhandled promise rejection capture, (3) Configure session replay for errors, (4) Upload source maps for readable stack traces, (5) Report releases and environments, (6) Capture custom errors/messages. Triggers: "add error tracking", "add sentry", "track exceptions", "report errors", "temps error tracking", "wire up error monitoring".

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

Guide for using the Sentry CLI to interact with Sentry from the command line. Use when the user asks about viewing issues, events, projects, organizations, making API calls, or authenticating with Sentry via CLI.

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

Use when the user shares a Sentry URL, says "check Sentry", or wants to investigate production errors. Uses Sentry MCP tools for deep analysis.

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

Drafts one service catalogue entry (description, scope in and out, owners and support groups, service levels exactly as provided, request path, dependencies, charging, lifecycle) from the service team's notes, questionnaire answers or existing documents, with UNKNOWN and a question list for every field the inputs do not cover. Never invents a service level, owner or price. Use when the user asks to "write the catalogue entry for this service", "turn these questionnaire answers into a service description", "tidy this request catalogue item" or "check this draft entry for empty fields". Do not use for a how-to or known-error article, use knowledge-article-drafter instead; for operating procedures, use runbook-drafter. Drafts for human review; never approves, authorises or signs off.

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

差分が「その差分自身を審査するレビュー基準・品質ゲート」を弱めていないかを diff-time で検出する。Check 1 レビュールールの削除・弱体化（.river/rules.md / .river/rules.d/*）、Check 2 実行時コンフィグの閾値・ゲート緩和（.river-review.{json,yaml,yml} の review.severity 引き下げ / exclude 拡大 / memory.suppressionEnabled 無効化 / selection.skills.exclude 追加）、Check 3 suppression entry の新規追加、Check 4 lint・静的解析設定からのルール削除や無効化、Check 5 branch protection・required check の緩和、の 5 Check を対象とし、これらが機能変更と同一 PR に混在し、かつ意図の宣言が無い場合に指摘する。report-only。workflow の permissions / action pin は gha-workflow-security、既存 suppression entry の使い分けは suppression-feedback、設定ファイルの一般的妥当性は config-json、.only / .skip / @ts-ignore / @ts-nocheck は heuristic-review.mjs の決定論検出器、リファクタと機能追加の混在は behavior-structure-separation へ委譲する

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

전자 의무 기록의 진료 기록, 처방, 검사 결과 화면을 설계합니다. 약물 상호작용 경고, 변경 이력, 의료 현장에서 입력하기 쉬운 화면의 설계 지침을 정리합니다.

• 진료 흐름 설계
• 약물 상호작용 경고 구현
• 검사 결과의 이상 수치 표시

Prepare a CHANGELOG.md entry for a Storybook minor or major release. Collect changes from prereleases, filter out changes already backported to patch releases, select significant highlights, and combine them with the full change list.

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

• Prepare a changelog for a Storybook minor release
• Summarize major release highlights
• Consolidate changes from prereleases

Review multi-step forms to find information users must enter more than once. Suggest automatic filling, reuse options, and preserving data between steps, while explaining relevant accessibility requirements and exceptions for security or validity.

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

• Checking repeated fields during checkout
• Reviewing signup and onboarding forms
• Reusing information in support flows

Set up or review production error monitoring to capture unhandled errors, failed requests, and performance signals. Check event context, release labels, and alert routing so teams receive useful information when problems occur.

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

• Setting up error monitoring for a new production app
• Investigating errors that monitoring fails to capture
• Reviewing critical alerts and on-call routing