9.9천건 · 관련도순
Move verified development work toward a merged pull request, a request to review and combine code changes. Push the branch, generate the request body, optionally trigger a review, and track progress through the merge.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Practice a chosen law subject with a fixed number of multiple-choice questions, essay prompts, or flashcards. Get explanations after each answer, record results, and use weak-topic patterns to guide the next study recommendations.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Submit shopping questions to Amazon's Alexa/Rufus assistant and collect answers as JSON, a structured data format. Use product search results as context for category research, or run a series of general shopping questions.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Guide team Git work with consistent commit messages, branch naming, and review practices. Follow concrete steps for everyday development, urgent fixes, releases, merge conflicts, and version tags, including guidance on when to use merge or rebase.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Deliver TeamHarness messages to the correct room, channel, or session using recorded reply routes. It covers task handoffs and requester reports, while defining when to reply directly or suppress acknowledgements that could cause message loops.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Query GitHub pull requests by author, status, or review needs, and extract selected fields as JSON. Inspect the data structure and size first, then use jq, a JSON filtering tool, to refine results.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Organize changes into focused branches and commits, write consistent commit messages and pull requests, and run relevant checks before pushing. It also handles dependent pull requests, CI follow-up, and updates that preserve review history.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Guide team Git work with consistent commit messages, branch naming, and review practices. Follow concrete steps for everyday development, urgent fixes, releases, merge conflicts, and version tags, including guidance on when to use merge or rebase.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Bring one selected pull request toward a mergeable state by reviewing feedback, applying changes within scope, and checking tests and CI, the automated build checks. Bounded retries produce a readiness result or a clear blocker without merging.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn a specified GCP access request into a reviewable Pulumi change and pull request. Select the narrowest suitable role and encrypt personal email identities, covering resource permissions and Cloud Run viewer access through IAP, an access gateway.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Clarifies a vague clinical or biomedical research idea into a structured, bounded, searchable, researchable, and testable question. Always use this skill whenever a user has an early-stage clinical or research thought, an over-broad topic, an ill-defined evidence question, or an unclear problem statement that must be translated into a question framing suitable for literature retrieval, evidence synthesis, gap analysis, study design, or downstream protocol planning. Never jump straight to answering the substantive medical question unless the user explicitly asks for that. Focus first on question framing, boundary setting, and downstream-ready formulation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Answer Viking AI Search product questions, CLI usage questions, API/auth questions, configuration questions, and troubleshooting questions by grounding every claim in either the installed `vs` CLI's own output or official Volcengine documentation. Never fabricate.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when a customer or prospect has sent a security questionnaire, due diligence form or vendor assessment and someone asks "answer this security questionnaire", "fill in the customer's vendor assessment", "draft answers from our policies", "we have 300 questions due Friday", "reuse our previous questionnaire answers" or "which answers can we not back up". Drafts every answer from the company's own documents with a source and a confidence level, flags answers without evidence and answers that create commitments, checks consistency with past answers, and writes an answer sheet plus a list of items for owners to confirm.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when a company needs a working process for privacy requests, or just received one and has none, and asks "DSAR procedure", "how do we handle a subject access request", "someone asked us to delete their data", "right to erasure process", "data subject rights workflow", "GDPR request handling" or "we missed the one-month deadline". Designs intake from any channel, a proportionate identity check, the system search map, review and redaction, response templates per right, deadline tracking and a request log, written as a procedure the support and privacy teams can run.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when hunting Pwn Request vulnerabilities where pull_request_target workflows checkout attacker-controlled PR code and execute it in a privileged context with access to repository secrets. Trigger on: "pwn request", "pull_request_target", "checkout PR head", "npm install in CI", "lifecycle scripts in CI", "preinstall script", "postinstall script", "package.json scripts CI", "npm ci ignore-scripts false", "actions/checkout ref pull request head sha", privileged workflow running PR code, "Gato-X", supply chain via PR lifecycle scripts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Creates GitHub Pull Requests with existing PR detection, branch pushing, and intelligent title/body generation. Use when user requests to create pull request, open PR, update PR, push for review, ready for review, send for review, get this reviewed, make a PR, share code, request review, create draft PR, submit for review, run /create-pr command, or mentions "PR", "pull request", "merge request", "code review", "GitHub PR", or "draft".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Prepares a DRAFT vendor risk screening brief from the material the user provides on one vendor (questionnaire answers, certificates, assurance reports, policies, contract extracts): per screening topic, what a document evidences with reference, date and scope, what is only asserted, what is missing or contradicted, certificate and report details as stated, and ready-to-send questions for the vendor and the internal owners. No web research, no risk rating, tier, score or recommendation. Use when the user asks to "screen this vendor", "review the vendor's questionnaire answers", "check what the vendor's certificate covers", "what is missing from this due diligence pack" or "draft the follow-up questions for the vendor". Do not use for answering a customer's questionnaire about your own organisation, use vendor-security-questionnaire-prefill instead. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Prepares a DRAFT internal audit pack from the audit plan: scope as stated, criteria with clauses quoted from the documents provided, document requests per auditee with due dates, open interview questions per process and role, previous findings to follow up and a readiness checklist. Never pre-judges conformity, writes findings or selects the sample; the lead auditor decides. Use when the user asks to "prepare the internal audit", "build the audit pack from this plan", "draft the document requests and interview questions" or "get us ready for the supplier audit". Do not use for evidence requests built from a control list, use control-evidence-request-pack instead; to chase actions from earlier audits, use corrective-action-tracker. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turns plain-language requests (emails, chat messages, form submissions, meeting asks, voicemail or call notes) into one intake record per request (what is asked, who asks and for whom, urgency as evidenced, category, suggested owner, missing information with draft clarifying questions) and a triage table sorted for the operations lead to act on. Use when the user asks to "log these requests", "triage this pile of asks", "turn this message into an intake record", "who should own this request", "what is missing before we can start" or "build today's intake list". Do not use for customer support tickets, use ticket-triage-pack instead; for clearing a personal mailbox by reply bucket, use inbox-triage. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Prepares a change request pack (description and justification, scope, schedule, implementation plan, risk as stated, rollback, test evidence as provided, communications, approvals route) from an engineer's notes, ticket or pull request description, with UNKNOWN for anything not provided and a question list for the engineer. Never rates risk or marks a change tested or approved. Use when the user asks to "write the change request for this", "fill in the change ticket from my notes", "prepare the CAB submission" or "turn this pull request into an RFC". Do not use for the step-by-step procedure with commands and rollback, use runbook-drafter instead; for release notes describing what shipped, use release-notes-writer. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Assembles a DRAFT capital expenditure request pack from the requester's inputs: business need, options including do nothing, costs exactly as provided, benefits as stated, risks, assumptions, budget status and the approvals route read from the organisation's own delegation of authority, with UNKNOWN for every missing figure, date or name. Use when the user asks to "prepare a capex request", "draft the business case for this equipment", "fill in the capital request form", "structure this investment proposal" or "what approvals does this spend need". Do not use for a board or committee decision paper, use board-paper-skeleton instead; for an IT change approval, use change-request-pack; to pressure-test a finished business case, use cfo-reviewer. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
FaceTime 내부 상태와 발신 준비를 확인하고, 승인 후 설정된 소유자 연락처로 음성·영상 통화를 겁니다. 통화 종료를 요청하고 이후 상태도 확인합니다.
웹사이트 통신을 HAR 파일로 기록하고 JSON을 가져오는 API를 분석해 HTTP 클라이언트를 만듭니다. 브라우저 없이 검색 등의 작업을 다시 실행할 수 있습니다.
완성된 변경을 GitHub 풀 리퀘스트로 정리합니다. 브랜치와 커밋 정리, 설명과 검증 기록 작성, 화면 변경 증거 첨부, 리뷰 답변을 진행합니다.