'quest' 검색 결과

Turns a control list and an audit scope into draft evidence requests grouped by control owner, each with the control as stated, the audit period, evidence examples (commonly requested) and a proposed due date derived from the fieldwork dates. Never judges whether evidence is sufficient, never selects the sample and never sends a request; the auditor decides. Use when the user asks to "prepare the evidence requests", "draft the PBC list", "build the evidence request pack for the audit" or "what do we need to ask each control owner for". Do not use for document requests and interview questions built from an audit plan, use audit-prep-pack instead; to check claims in a report against sources, use claims-evidence-map. Drafts for human review; never approves, authorises or signs off.

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

Pull Request / Merge Request を作成するときに必ず参照する。`gh pr create`/`glab mr create` で PR/MR を作る、コミット済みの作業をレビューに出す、並列・stacked 作業の各ブランチで PR を起こす、といった場面で使う。リポジトリの pull_request_template/merge_request_template を決定論スクリプトで検出して優先し、テンプレの骨組み（見出し・チェックリスト・順序）を改変せず入力箇所を埋めるだけにする（作成前に骨組み照合ゲートで機械検証）。無ければ汎用観点で本文を構成。本文の素材は対象リポジトリの git 差分のみに限定し、他リポジトリ・他タスクの内容を混入させない。draft 既定。head が保護ブランチ（GitHub 上・origin/HEAD の既定ブランチ、main・master・develop・trunk・release 系など）のときだけ push と作成の前にユーザー承認を取り、それ以外は確認せず push して作成する。GitHub(gh) 基本、GitLab(glab) 等にも対応。

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

Systemic questioning techniques: Circular questions, scaling questions, miracle question, and exception questions for reflection and perspective expansion.

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

Systemic and solution-focused methods: miracle question, scaling, exception exploration, circular questions, hypothetical questions, worsening questions, coping questions. Merged from solution-focused-therapy and systemic-questioning.

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

Create branch, atomic commits, push, and open a pull request with terse, exact messages. Conventional branch + commit format. PR title ≤70 chars, body says "why", not "what". Use when the user says "create pr", "create pullrequest", "create pull request", "make pr", "open pr", "open pullrequest", "open pull request", "submit pr", "raise pr", "/create-pr", or asks to ship/send changes as a pull request (PR/pullrequest/pull-request, any spelling).

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

구현이 끝나면 전체 테스트를 확인하고 로컬 병합, 풀 리퀘스트 생성, 현상 유지 중 선택한 작업을 수행합니다. 선택과 작업 환경에 따라 브랜치와 작업 공간을 정리합니다.

• 완성한 기능을 로컬에서 병합
• 브랜치를 푸시하고 풀 리퀘스트 생성
• 완료한 변경을 나중에 통합하도록 보관

현재 브랜치에서 기존 템플릿에 맞는 초안 풀 리퀘스트를 만듭니다. 변경 사항과 기준 브랜치를 확인하고 설명, 테스트 항목, 라벨을 정리합니다.

• 현재 브랜치에서 초안 풀 리퀘스트 만들기
• 템플릿에 변경 내용과 테스트 정보 채우기
• 단계별 풀 리퀘스트의 비교 기준 확인하기

Create a GitHub pull request that follows the project's template. Review commits and changed files, gather issue and testing details, check branch readiness, and use the GitHub CLI to submit a regular or draft request.

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

• Submitting completed changes for review
• Writing a PR description from commits
• Creating a draft pull request

Prepare for investment diligence meetings with management, experts, customers, or advisors. Create a one-page brief with prioritized questions, comparison metrics, concerns to investigate, and follow-up requests based on the meeting's purpose and existing findings.

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

• Prepare questions for a management presentation
• Plan an industry expert call
• Check customer satisfaction and renewal intentions

Stage and commit code changes, push them to GitHub, and create or update a pull request, a request to review changes. Use the repository template and describe the motivation and final changes for reviewers.

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

• Commit completed changes and open a draft pull request
• Update an existing pull request on the current branch
• Write a pull request description using the repository template

Publish the current Git branch to origin and create or update its pull request, a request to review and merge changes. The skill runs validation and refreshes the title and description to match the full scope.

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

• Publish local branch changes to origin
• Create a pull request using the project template
• Refresh a pull request after its scope changes

Organize customer feature requests into themes and rank the top three against product goals, customer value, effort, and risk. For each recommendation, explain the underlying need, possible alternatives, uncertain assumptions, and simple ways to test them.

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

• Grouping customer requests into themes
• Selecting the top three requests for product goals
• Considering alternatives to requested features

Triage employee questions in an HR inbox against policies documented in Notion. Prepare Gmail drafts with policy references for routine questions, and route ambiguous, legal, personal, or compensation matters to HR through Slack.

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

• Drafting replies to routine HR policy questions
• Routing sensitive employee questions to HR
• Checking the HR inbox on a regular schedule

Prepares reports for GDPR personal data access or deletion requests. Checks Gmail, verifies identity, searches related Postgres records without changing them, and creates a Google Doc for legal review, leaving deletion and requester replies to people.

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

• Check incoming personal data requests each day
• Compile a data inventory for a verified requester
• Flag requests with insufficient identity evidence

Handle personal data access, deletion, portability, and correction requests through a structured checklist. Guide identity checks, data searches, legal exceptions, and deadlines, then draft separate acknowledgment and substantive response letters for attorney review and human delivery.

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

• Preparing a response to a personal data access request
• Organizing checks for deletion and portability requests
• Tracking data searches across internal systems

Triage quick legal questions against company risk guidelines and return a brief proceed, review, or hold response. It checks for hidden issues in apparently simple requests and identifies the next step when further review is needed.

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

• Answering a product manager's quick legal question
• Checking permission to display customer logos
• Spotting data and consent issues in feature changes

Inspect live development or staging traffic to find an identifier that distinguishes one developer’s requests across services. Produce a matching mirrord HTTP filter and a report showing where the identifier survives, disappears, or cannot be observed.

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

• Find a filter for personal requests on a shared staging cluster
• Check whether request IDs survive across services
• Build mirrord filters using JWT claims or cookies

Create a Markdown questionnaire for someone who has information you need. Clarify the recipient and required decisions, then produce prioritized questions with context and answer spaces for asynchronous replies or a meeting.

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

• Requesting information from a subject expert
• Gathering answers without scheduling a meeting
• Preparing questions for a discovery meeting

Select open pull requests for initial classification and distribute them to dedicated workers with a concurrency limit. Record why each request is included or excluded, without merging changes, assigning owners, or requesting reviewers.

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

• Classify a mixed list of open pull requests
• Include community pull requests without linked issues
• Limit concurrent triage workers

Finish completed development work by checking the full test suite and presenting integration choices: merge locally, create a Pull Request, or keep the branch. It carries out the selected path and handles workspace cleanup accordingly.

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

• Merging a completed feature locally
• Pushing a branch and creating a Pull Request
• Keeping completed work for later integration

Expert blueprint for quest tracking systems (objectives, progress, rewards, branching chains) using Resource-based quests, signal-driven updates, and AutoLoad managers. Use when implementing RPG quests or mission systems. Keywords quest, objectives, Quest Resource, QuestObjective, signal-driven, branching, rewards, AutoLoad.

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

Expert blueprint for quest tracking systems (objectives, progress, rewards, branching chains) using Resource-based quests, signal-driven updates, and AutoLoad managers. Use when implementing RPG quests or mission systems. Keywords quest, objectives, Quest Resource, QuestObjective, signal-driven, branching, rewards, AutoLoad.

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

Track Claude's best and worst questions in DuckDB. Use when Claude asks a notably good or bad question, or to review question quality. Triggers: leaderboard, bad question, good question, question quality.

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

Pre-fills a customer's or prospect's security or third-party risk questionnaire from the organisation's own answer sources (prior questionnaires, answer library, policies), returning one row per question with a draft answer marked Reused, Adapted, Missing or Routed, its source, date, scope match and owner, plus the Missing list by owner. Never invents an answer, certification or control and never submits. Use when the user asks to "pre-fill this security questionnaire", "take a first pass at the customer's due diligence form", "answer this vendor assessment from our previous responses", "populate the third-party risk questionnaire" or "which questions can we reuse answers for". Do not use for screening a vendor's own answers, use vendor-risk-screening-brief instead; for RFP or tender answers use rfp-response-drafter. Drafts for human review; never approves, authorises or signs off.

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