「by」の検索結果

Git-aware undo by logical work unit (track, phase, or task)

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

Build features guided by data insights, A/B testing, and continuous measurement using specialized agents for analysis, implementation, and experimentation.

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

You are a code education expert specializing in explaining complex code through clear narratives, visual diagrams, and step-by-step breakdowns. Transform difficult concepts into understandable explanations for developers at all levels.

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

Using records, pattern matching, primary constructors, collection expressions. C# 12-15 by TFM.

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

Close out a completed workstream by updating README artifacts when needed, producing a commit message, and applying changelog-ready content when the work is ready for commit. Use after review when a stable checkpoint is reached.

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

Close out a completed workstream by updating README artifacts when needed, producing a commit message, and applying changelog-ready content when the work is ready for commit. Use after review when a stable checkpoint is ready.

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

Assembles the minimal context pack for a given task. Use when the task spans multiple domains or the context set has obvious redundancy. Do not trim required working context by default.

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

Prepare a MYOT commit by writing SuggestedCommit.txt and SuggestedCommitBody.md following Conventional Commits, without actually committing.

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

Start or resume a MYOT task by reading AGENTS.md, project_map.md, and history.md, archiving history.md when switching tasks, and preparing a concise current task snapshot.

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

Gather phase context through adaptive questioning before planning. Use --auto to skip interactive questions (the agent picks recommended defaults). Use --chain for interactive discuss followed by automatic plan+execute. Use --power for bulk question generation into a file-based UI (answer at your own pace).

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

Create phases to close all gaps identified by milestone audit

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

Auto-fix issues found by code review in REVIEW.md. Spawns fixer agent, commits each fix atomically, produces REVIEW-FIX.md summary.

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

Create a clean PR branch by filtering out .planning/ commits — ready for code review

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

Identifies and exploits SQL injection vulnerabilities in web applications during authorized penetration tests using manual techniques and automated tools like sqlmap. The tester detects injection points through error-based, union-based, blind boolean, and time-based blind techniques across all major database engines (MySQL, PostgreSQL, MSSQL, Oracle) to demonstrate data extraction, authentication bypass, and potential remote code execution. Activates for requests involving SQL injection testing, SQLi exploitation, database security assessment, or injection vulnerability verification.

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

Identifying and exploiting Insecure Direct Object Reference vulnerabilities to access unauthorized resources by manipulating object identifiers in API requests and URLs.

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

Spearphishing targets specific individuals using personalized, researched content that bypasses generic spam filters. Email security gateways (SEGs) like Microsoft Defender for Office 365, Proofpoint,

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

Detect unauthorized SaaS and cloud service usage (shadow IT) by analyzing proxy logs, DNS query logs, and netflow data using Python pandas for traffic pattern analysis and domain classification.

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

Testing WebSocket implementations for authentication bypass, cross-site hijacking, injection attacks, and insecure message handling during authorized security assessments.

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

Detect suspicious PowerShell execution patterns including encoded commands, download cradles, AMSI bypass attempts, and constrained language mode evasion.

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

Detect process injection techniques (T1055) including classic DLL injection, process hollowing, and APC injection by analyzing Sysmon events for cross-process memory operations, remote thread creation, and anomalous DLL loading patterns.

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

Detects typosquatting attacks in npm and PyPI package registries by analyzing package name similarity using Levenshtein distance and other string metrics, examining publish date heuristics to identify recently created packages mimicking established ones, and flagging download count anomalies where suspicious packages have disproportionately low usage compared to their legitimate targets. The analyst queries the PyPI JSON API and npm registry API to gather package metadata for automated comparison. Activates for requests involving package typosquatting detection, dependency confusion analysis, malicious package identification, or software supply chain threat hunting in package registries.

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

Executes comprehensive red team exercises that simulate real-world adversary operations against an organization's people, processes, and technology. The red team operates with stealth as a primary objective, employing the full attack lifecycle from initial reconnaissance through objective completion while testing the organization's detection and response capabilities. This differs from penetration testing by focusing on adversary emulation rather than vulnerability identification. Activates for requests involving red team exercise, adversary simulation, adversary emulation, or full-scope offensive security assessment.

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

Detect and exploit race condition vulnerabilities in web applications using Turbo Intruder's single-packet attack technique to bypass rate limits, duplicate transactions, and exploit time-of-check-to-time-of-use flaws.

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

Tests APIs for excessive data exposure where endpoints return more data than the client application needs, relying on the frontend to filter sensitive fields. The tester intercepts API responses and analyzes them for leaked PII, internal identifiers, debug information, or sensitive business data that the UI does not display but the API transmits. This maps to OWASP API3:2023 Broken Object Property Level Authorization. Activates for requests involving API data leakage testing, excessive data exposure, response filtering bypass, or API over-fetching.

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