「requesting」の検索結果

Pre-commit review: security scan, quality gates, auto-fix.

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

Code review practices with technical rigor and verification gates. Use for receiving feedback, requesting code-reviewer subagent reviews, or preventing false completion claims in pull requests.

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

Submit proof requests on the Boundless ZK proof marketplace. Covers wallet setup, CLI configuration, building or discovering guest programs, self-hosting via Cloudflare Quick Tunnels (no Pinata/S3 needed), submitting, and retrieving results. Use when a developer wants to request a ZK proof, submit a proof request, get started with Boundless, try Boundless, or learn the requestor workflow.

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

Use when receiving code review feedback (especially if unclear or technically questionable), when completing tasks or major features requiring review before proceeding, or before making any completion/success claims. Covers three practices - receiving feedback with technical rigor over performative agreement, requesting reviews via code-reviewer subagent, and verification gates requiring evidence before any status claims. Essential for subagent-driven development, pull requests, and preventing false completion claims.

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

Prepares a focused code review request for a branch, commit, pull request, or substantial working-tree diff by defining the review boundary, contract, risk areas, evidence, and questions for an independent reviewer. Use before merge or when another agent needs to review an implementation. Not for processing feedback already received or for claiming runtime correctness.

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

Processes code review feedback by classifying each finding, reproducing or validating it against the real contract, applying the smallest in-scope fix, and re-running focused proof. Use after comments arrive on a diff, pull request, design, or implementation. Not for requesting a first review or debugging an unrelated failure.

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

Systematic code review skill covering both requesting a review (pre-commit checklist) and receiving and responding to review feedback. Checks code quality, security, test coverage, architectural alignment, and documentation before any code is committed.

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

Active Directory exploitation after domain credentials exist: Kerberos (AS-REP/Kerberoast including cracking the ticket then using the account), delegation, NTLM coercion/relay, lateral movement, ACL abuse, ADCS ESC1-ESC17 and CVE paths, dMSA/BadSuccessor, Kerberos reflection, identity confusion, management-plane, domain trust, and domain persistence. Own the current AD chain through crack-and-use to DA, equivalent domain control, or the targeted host SYSTEM. Do not stop after requesting TGS. Host C2 belongs to /post. Operator chooses next modules.

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

Dispatch code-reviewer agent for two-stage review. Use after completing implementation tasks.

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

Review a pull request end-to-end using GitHub CLI. Covers diff analysis, commit history review, CI/CD check verification, severity-leveled feedback (blocking/suggestion/nit/praise), and gh pr review submission. Use when a pull request is assigned for review, performing a self-review before requesting others' input, conducting a second review after feedback is addressed, or auditing a merged PR for post-merge quality assessment.

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

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.

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

Verify a change before committing: security, tests, independent review.

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

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

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

Use when receiving code review feedback (especially if unclear or technically questionable), when completing tasks or major features requiring review before proceeding, or before making any completion/success claims. Covers three practices - receiving feedback with technical rigor over performative agreement, requesting reviews via code-reviewer subagent, and verification gates requiring evidence before any status claims. Essential for subagent-driven development, pull requests, and preventing false completion claims.

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

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

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

Exploit Active Directory Certificate Services (AD CS) misconfigurations, specifically ESC1. By requesting a certificate based on a overly permissive template that allows the enrollee to supply a Subject Alternative Name (SAN), an attacker can impersonate highly privileged users (like Domain Admins) and seamlessly escalate privileges across the entire AD environment.

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

完成任务、实现重要功能或合并前使用，用于验证工作成果是否符合要求

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

Hunts for Kerberoasting and related ticket attacks by analyzing Kerberos service ticket request events (4769) for weak encryption types, abnormal request volume per account, and non-machine accounts requesting many SPNs. Activates for requests to hunt Kerberoasting, detect RC4 ticket requests, or find SPN-targeting credential attacks.

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

Use when a task needs the judgment of an EMT (Basic Life Support tier) — deciding whether a chest-pain patient gets aspirin under protocol, dosing an epinephrine auto-injector for anaphylaxis and knowing when to repeat it, applying spinal-motion-restriction criteria instead of routine backboarding, recognizing the moment a call exceeds BLS scope and requesting ALS intercept, or working a patient refusal (AMA) to a legally defensible conclusion.

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

Manages cloud infrastructure through natural language conversations with Pulumi Neo, an AI agent for platform engineers. Enables infrastructure analysis, resource provisioning, stack deployment, and configuration management via conversational AI. Use when creating Neo tasks, requesting infrastructure analysis, automating cloud deployments, managing infrastructure as code (IaC), provisioning AWS/Azure/GCP resources, managing infrastructure through natural language prompts, reviewing PRs with Neo, handling Neo approval workflows, or checking Neo task status and events. Also use when the user mentions "Pulumi Neo", "Neo task", "Neo agent", or wants AI-assisted infrastructure management.

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

Refresh Claude Ads platform, API, policy, regulation, benchmark, issue, pull-request, fork, and repository evidence. Use for ads research refresh, expired refresh_due dates, stale API or platform claims, reverify-or-demote decisions, release-current claim validation, ecosystem review, current platform changes, or updating paid-media knowledge. When tools or sources are unavailable, still demote the stale claim for the current run and block dependent release-current assertions before requesting access.

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

Supports Interactive Media Ads (IMA) SDK. Use this skill for client-side ad insertion when you are requesting video ads for websites, apps, TVs or other platforms using VAST or VMAP. Do not use for Dynamic Ad Insertion (DAI), SSAI, or SGAI.

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

Always use this skill before claiming any work is done, fixed, passing, or complete — even if it seems obvious. Also use when receiving code review feedback from any source (human or automated), when finishing a task or major feature, before committing or creating a PR, or when about to express satisfaction with work. Covers three practices: receiving feedback with technical rigor (no performative agreement), triggering code review via /code-review command or cook/fix pipelines, and verification gates (run the command, read the output, then make the claim). Never skip — the cost of false completion claims is higher than the cost of verifying. References: code-review-reception.md, requesting-code-review.md, verification-before-completion.md.

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

Detects push notification implementations that violate Guideline 4.5.4 — including requesting push permission at launch, using push for unsolicited marketing, and broken notification handling.

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