「que」の検索結果

Use when sending notifications via mail, Slack, database, or custom channels — with queuing, on-demand recipients, and notification preferences.

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

Use when configuring Laravel task scheduling — cron expressions, frequency helpers, overlap prevention, maintenance mode, or output handling.

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

Use when creating or modifying Laravel middleware — request/response filtering, groups, priority, terminable middleware, or route-level assignment.

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

Use when working with Laravel queues in production — Horizon dashboard, worker supervision, job metrics, balancing strategies — even when the user just says 'my jobs are piling up'.

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

Use when building Laravel emails — Mailables, Markdown templates, queued sending, attachments, previews — even when the user says 'send this as an email' without naming Mailables.

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

Use when creating a new Laravel API endpoint — Controller, FormRequest, Resource, route, Policy, OpenAPI annotations — versioned route layout, single-action `__invoke` controllers.

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

When running discovery interviews — question-bank build, bias audit, insight extraction. Triggers on 'audit my guide', 'extract insights from transcript', 'is my hypothesis falsifiable'.

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

Autonomous multi-step investigation — deep research carried end-to-end without per-step approval; explicit request only, never for normal feature work.

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

Route codebase-structure questions (who calls X, where used, change-impact) to an existing code-graph first: impact, tests-for, dead cheaper, never more precise; grep routine. Also 'call graph'.

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

Use BEFORE editing shared code — enumerates every call site, event consumer, queue worker, API client, migration, and test that a planned change will touch, with a file:line citation per dependency.

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

Use when picking which analysis or project-analysis-* skill fits a request — routes by scope, framework, and symptom — even if the user just says 'analyze this' or 'dig into the codebase'.

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

Use when reviewing authorization end-to-end — route → gate → policy → query scope → response filter — before changes to permissions, tenants, ownership, or admin flows.

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

Use when comparing this package to a peer / competitor — ours-vs-theirs verdict table, axis selection, adoption queue. Triggers on 'how do we compare to X', 'should we adopt their pattern'.

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

Audit how a brand is currently expressed across touchpoints and flag drift from its defined tokens, voice, and strategy. Use to inventory and critique an existing brand before changing it.

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

Before finishing any code (endpoint, query, migration, render, file, infra, dependency, test) — the senior pre-ship checklist of invisible cross-cutting controls AI omits, with backstop greps

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

Use when capturing an architectural decision — file naming, next ADR number, Status / Context / Decision / Consequences, index regen; fires even without saying 'ADR'.

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

Create or update a GitHub pull request for the current branch. Use when the user invokes `$pr-create`, asks to create/open a PR, or wants the current branch pushed and described as a draft PR.

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

Run an infrastructure-first security audit of a repository - secrets archaeology, dependency supply chain, CI/CD pipeline, LLM/AI attack surface, agent skill supply chain, OWASP Top 10, STRIDE threat model, and data classification - with a confidence gate and a pre-emit verification gate that suppress speculative findings. Use when asked for a security audit, threat model, pentest-style review, OWASP pass, or a pre-release security check. Not for reviewing a single diff - use requesting-code-review for that.

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

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

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

Address GitHub PR review feedback at line, file, and PR level — fetch, evaluate, fix, commit, and resolve. Use when given a PR URL, a review-comment URL, or a PR-level comment URL. Triggers: GitHub discussion URLs, "fix this review comment", "address PR feedback", "resolve PR comments", PR URLs with #discussion_, #issuecomment-, or #pullrequestreview- fragments.

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

Retrieve current documentation, API references, and code examples for any library, framework, SDK, CLI tool, or cloud service — including well-known ones like React, Next.js, Prisma, Django, or Spring Boot. Use for API syntax, configuration options, version migrations, setup instructions, and library-specific debugging, even when you already think you know the answer: training data on API details and signatures is frequently outdated. Prefer this over web search for library documentation.

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

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

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

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

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

Diagnoses failing GitHub Actions runs by reading logs, identifying the root cause, and suggesting fixes. Use this skill whenever a user shares a GHA run URL, pastes runner log output, mentions a failing workflow, asks why a CI job is broken, or says anything like "my GHA is failing", "workflow failed", "can you check my run", or "CI is broken". Also trigger when raw log text is detected in the conversation that appears to come from a GitHub Actions runner. Do NOT use for general GHA workflow authoring questions, YAML formatting help, or passing runs with no failure context.

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