「quest」の検索結果

Create and manage pull requests using GitHub CLI. Covers branch preparation, writing PR titles and descriptions, creating PRs, handling review feedback, and merge/cleanup workflows. Use when proposing changes from a feature or fix branch for review, merging completed work into the main branch, requesting code review from collaborators, or documenting the purpose and scope of a set of changes.

日本語の概要は準備中です。原文の説明を表示しています。

GitHubでpull requestを作り、文章を書く時の心得。PRのタイトルと概要欄の書き方、リンクが壊れない書き方、親子PRの組み方、squash and mergeのcommit messageの書き方を定める。 pull requestを作成・更新・mergeする時、GitHubに載る文章を書く時に読み込む。

Use when a feature or code change made by Claude is complete and the developer wants to confirm they actually understood it before shipping. Triggers on "handoff", "quiz me", "comprehension check", "did I understand this", "verify I read the code", "test my understanding", or after finishing a feature when the developer wants to take ownership of AI-written code. Also triggers on requests for an interactive or clickable quiz ("interactive mode", "let me answer with the mouse", "mode interactif", "je réponds à la souris"). Quizzes the developer on WHERE the logic lives (file/function) and WHY decisions were made (trade-offs, behavior, debugging), with the number of questions scaled to the size of the change. Multiple-choice questions are clickable by default (asked through `AskUserQuestion`) and fall back to typed answers. Points to file:line on wrong answers, allows one retry, then reveals the answer, and ends with a score plus the weak areas to re-read. Conducts the quiz in the developer's language.

日本語の概要は準備中です。原文の説明を表示しています。

AquesTalk（ゆっくりボイス）の音声記号列を自動生成・変換するスキル。 普通の日本語テキストをアクセント記号・句切記号付きの音声記号列に変換する。 以下の場面で必ず使うこと： - 「調声して」「発音を直して」「アクセントをつけて」 - 「音声記号列に変換して」「ゆっくりの発音を自然にして」 - 「棒読みを直して」「セリフの読み方を修正して」 - 「タイムラインのセリフを調声して」「全セリフに発音記号をつけて」 - AquesTalk・音声記号・アクセント記号・句切記号に関する操作全般

Identify and exploit HTTP Request Smuggling (HTTP Desync) vulnerabilities caused by discrepancies in how front-end proxies (load balancers, CDNs) and back-end servers parse the Content-Length and Transfer-Encoding headers. Use this to bypass security controls, hijack user sessions, and poison web caches.

日本語の概要は準備中です。原文の説明を表示しています。

Cross-Site Request Forgery (CSRF) tricks authenticated users into submitting forged requests to a target application by exploiting browser automatic cookie attachment. Detect via missing or predictable CSRF tokens in state-changing requests (POST/PUT/DELETE), absent `SameSite` cookie attributes, and JSON endpoints accepting `text/plain` Content-Type. Test using HTML auto-submitting forms, XHR requests, and CORS-enabled fetch. Tools: Burp Suite (Generate CSRF PoC), OWASP ZAP.

日本語の概要は準備中です。原文の説明を表示しています。

Hand a Prisma Next question or report off to the team — file a GitHub issue (bug or feature request), or route Q&A / design discussion / direct-team-contact to the Prisma Discord at pris.ly/discord. Use for bug, bug report, file an issue, report a bug, feature request, missing feature, this should be a feature, file this, this is a bug, this is broken, surprising behaviour, this doesn't work, file feedback, send feedback, capability gap, file via prisma-next-feedback, ask the team, talk to the team, talk to the Prisma team, talk to Prisma, Discord, Prisma Discord, Q&A, design feedback, is this the intended way, how should I do X, extension author question, extension author needs help.

日本語の概要は準備中です。原文の説明を表示しています。

Sales enablement, technical presales and deal acceleration for B2B SaaS revenue teams. Use this skill when planning outbound campaigns, running discovery calls, building deal strategy, creating battle cards, writing proposals, responding to RFPs, preparing a product demo, scoping a proof of concept or pilot, answering a security questionnaire or the AI annex buyers now attach to it, executing sales sequences, coaching qualification, or deciding what the website's AI chat agent is allowed to say. Also triggers on: outbound, cold outreach, reply handling, reply classification, out-of-office replies, auto-replies counted as replies, our reply rate is inflated, prospect replied remove me, opt-out by reply, is this list ready to send, launch readiness, CRM segment outbound, we emailed a current customer, outbound hit an open opportunity, ownerless leads, prospects engaging our competitors, competitor connections, displacement list, is this personalization creepy, can we mention they visited our site, signal freshness, deal strategy, pipeline, battle card, objection handling, common objections, why do we keep hearing this objection, mine call transcripts for objections, objection register, proposal, RFP, discovery call, MEDDPICC, sales sequence, qualification, sales engineer, solutions engineer, presales, demo plan, demo script, POC, proof of concept, pilot success criteria, technical evaluation, technical win, security questionnaire, vendor security review, SOC 2 questionnaire, AI security questionnaire, AI annex, AI vendor due diligence, the buyer is asking if we train on their data, do you train on customer data, which model do you use, model provider sub-processor, AI subprocessor disclosure, where does inference run, can the customer turn the AI feature off, AI-CAIQ, CSA AI Controls Matrix, ISO 42001, ISO/IEC 42001, NIST AI RMF, EU AI Act Article 50, are we a provider or a deployer, AI feature disclosure, our model vendor changed and nobody told the buyer, technical objection, mutual action plan, MAP, close plan, mutual close plan, buyer enablement, the deal is stalled, deal stalled after the demo, how do I get this deal to close, close date keeps slipping, JOLT, buyer indecision, no-decision loss, website chatbot, chat widget, AI chat agent, AI SDR, inbound AI SDR, conversational marketing, live chat, what should our chatbot be allowed to say, our chatbot quoted the wrong price, the bot promised a discount, do we have to disclose it is AI, EU AI Act chatbot disclosure, chatbot handoff to sales, chat transcript review, prompt injection on our chatbot, Drift, Qualified, Intercom.

日本語の概要は準備中です。原文の説明を表示しています。

Programmatically driving Salesforce Approval Processes from Apex — `Approval.process(ProcessSubmitRequest)` to submit, `ProcessWorkitemRequest` to approve / reject / reassign, recall semantics, querying `ProcessInstance` and `ProcessInstanceWorkitem` to find pending approvals, and the bulk-submit / bulk-action error-row handling. Covers when to use Apex-driven approval (system-initiated submission, batch approvals, custom UIs) vs leaving the platform's standard buttons in place. NOT for the Approval Process metadata definition itself (that's admin / declarative — see admin/approval-processes), NOT for Flow-based approvals (use flow/flow-orchestration-patterns).

日本語の概要は準備中です。原文の説明を表示しています。

Find question-based Google Autocomplete suggestions for any topic. Prepends question modifiers (what, how, why) to a seed topic and returns real autocomplete suggestions — useful for AEO prompt research, content ideation, and understanding what people ask about a topic. Use when the user wants to discover questions people search for, find content angles, or do keyword/prompt research for a topic.

日本語の概要は準備中です。原文の説明を表示しています。

Re-asks the most recent question through the agent's interactive questionnaire tool instead of plain text, and keeps using that tool for every later question with concrete options. Use when the user invokes `/qs` or `$qs`, or asks for a question to be re-posed as selectable choices.

日本語の概要は準備中です。原文の説明を表示しています。

JIRA Service Management via the jira-as wrapper: service desks, request types, requests, customers, organizations, queues, SLAs, approvals (8 sub-domains). Triggers: 'create JSM request', 'list service desks', 'SLA status for KEY', 'approve request KEY', 'list queue NAME'. Requires JSM-licensed tenant + agent role. NOT for core Jira issue ops (mk:jira-issue); NOT for project admin (mk:jira-admin).

日本語の概要は準備中です。原文の説明を表示しています。

Build an evidence-backed working model of an existing codebase. Use when you must orient in a large or unfamiliar repository; explain architecture or a subsystem; trace a request, runtime, control, or data flow for a concrete question or bug; analyze a branch, commit, diff, or pull request for behavioral impact and blast radius; or assess AI-generated or changed code against requirements, contracts, invariants, tests, and runtime evidence. Default to read-only investigation. Do not trigger only because a coding task touches an existing repository; use when understanding or verification is the requested outcome or a substantial prerequisite.

日本語の概要は準備中です。原文の説明を表示しています。

Relentless one-question-at-a-time interview (tappable options with a recommended answer) that sharpens a requirement, business plan, project plan, proposal, or raw idea through conversation, then writes it up as a brief with a glossary and decision log. Use whenever the user wants their thinking stress-tested or pinned down before acting — trigger phrases include "grill me", "grill this", "詰めて", "詰めたい", "壁打ち", "要件を固めたい", "企画を練りたい", "計画を整理したい", "アイデアをぶつけたい", "突っ込んで", "clarify", "質問して", "何が決まってないか教えて", or when the user describes a plan/idea vaguely and asks what to do next. Do NOT use for reviewing a finished document (use a document-review skill) or when the user just wants an answer, not questions.

Clarify ambiguous or conflicting requests by researching first, then asking only judgment calls. Use when prompts say "grill me", ask hard questions, request relentless interrogation, pressure-test assumptions, clarify scope/requirements, define success criteria, or request system-design/optimization decisions before implementation; stop before implementation.

日本語の概要は準備中です。原文の説明を表示しています。

Create a pull request from the current branch. Triggers on create PR/open PR/make PR/submit PR/push PR/raise PR/open a pull request/create a pull request/ready to merge/branch is ready when the user wants to turn their current branch into a GitHub pull request with a well-structured description

日本語の概要は準備中です。原文の説明を表示しています。

システム療法および解決志向アプローチの手法：ミラクル・クエスチョン、スケーリング、例外の探索、サーキュラー・クエスチョン、仮定の質問、悪化の質問、コーピング・クエスチョン。solution-focused-therapy および systemic-questioning から統合。

Builds a DRAFT quiz from the training content the user supplies (slide deck, manual, e-learning script, session transcript, procedure): numbered questions with the correct answer, distractors drawn from the content itself, an explanation quoting the source passage with its location, a difficulty tag (Recall, Apply, Analyse) with its basis, and a coverage table showing which sections and objectives each question tests and which are left uncovered. Use when the user asks to "build a quiz from this deck", "write knowledge check questions for this module", "create an assessment from this training", "test understanding of this procedure" or "which sections does this quiz cover". Do not use for a reader-facing question and answer page built from documents, use faq-builder instead; for writing the procedure itself from notes or a walkthrough, use sop-drafter. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Reads a purchase order extract (spreadsheet, CSV or pasted table) and returns a DRAFT question sheet for the buyer: possible split orders, round amounts, amounts just under an approval threshold, first-seen or near-duplicate vendors, duplicate orders and missing or self approvals, each a neutral question naming the PO numbers, never a finding. Use when the user asks to "review these purchase orders", "screen the PO log", "spot anomalies in this spend extract", "sanity-check the PO register" or "prepare buyer questions before the audit". Do not use for an expense claim or travel request checked against policy, use expense-policy-precheck instead. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Reads a cash forecast (spreadsheet, model export, pasted table or the narrative that accompanies it) and returns a DRAFT assumptions sheet: every assumption the forecast rests on, stated or implied by the figures, with its value as read, its location in the model, the cash lines it drives, its stated source or "not stated", the evidence that would test it, an owner, and one neutral challenge question, so a reviewer can work through the assumptions one by one. Use when the user asks to "list the assumptions behind this cash forecast", "what is this cash flow forecast assuming", "prepare the challenge questions for the treasury review", "pull out the drivers of the 13-week cash forecast" or "build an assumptions register for the liquidity plan". Do not use for actuals against budget by line, use budget-variance-explainer instead; do not use for the case behind a capital request, use capex-request-pack instead. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill when writing a pull request description, change summary, or release notes in Japanese for this project. Trigger words: PR 説明, プルリク, 変更サマリ, リリースノート, PR 文章, レビュー依頼, 日本語で説明, pull request.

Use when the user presents an idea/plan/proposal and wants a specific 16-minds (MBTI) personality to ask probing questions back — instead of giving an answer. Triggers on Japanese phrases like 「ENTPでツッコんで」「INFJに問い詰めて」「ENTJ視点で質問して」「このアイデア叩いて」, English equivalents like "as ENTP, question this" / "INFJ would ask what?", or 16-minds commands with a `--ask` flag. AIに「答えさせる」のではなく「問わせる」ためのSkill。ユーザーが思考を整理したい時に使う。

MUST USE when source footage or a material folder is provided and material understanding or 03_analysis generation is needed. Trigger not only on explicit analysis requests ('分析して', '素材を見て') but also when the user points at footage and says things like 'この動画で', 'この素材で', or any request that requires understanding the provided media before planning or editing.

Unified pull request workflow: prepare a safe branch, run read-only review, fix Required findings, create/update a GitHub draft PR, and verify CI plus automated review comments. Subcommands: `create` (simplify + PR, skip code review), `review` (read-only findings only), `fix` (Required fixes + commit, no push), `simplify` (simplification only), `verify` (existing PR checks/reviews only). Use when creating or reviewing PRs, self-reviewing changes, simplifying PR changes, or requesting "PR作成", "レビュー", "簡素化". Do NOT use for responding to review comments or a lightweight review of the current working diff without the PR workflow (use the built-in /code-review instead).