「findings」の検索結果

Interpret learning analytics data and translate dashboard findings into actionable teaching decisions. Use when reviewing LMS data, quiz patterns, or engagement metrics.

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

Expert knowledge for Azure External Attack Surface Management development including configuration. Use when filtering EASM inventory by ASN, domains, hosts, IPs, pages, SSL certs, or exporting findings to analytics tools, and other Azure External Attack Surface Management related development tasks. Not for Azure Defender For Cloud (use azure-defender-for-cloud), Azure Security (use azure-security), Azure Sentinel (use azure-sentinel), Azure Networking (use azure-networking).

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

Audit trending repos for real security vulnerabilities and disclose responsibly - scan and route findings (PVR / dependency PR), re-submit queued advisories, and send armed email disclosures

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

Review open PRs two ways - default is a per-PR deep review with severity-tagged findings, inline comments, and a verdict; --survey runs a risk-tiered triage digest of what's safe to merge first

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

Step 5 of the PaperOrchestra pipeline (arXiv:2604.05018). Iteratively refine drafts/paper.tex by simulating peer review and applying targeted revisions, with strict accept/revert halt rules, deterministic 0-100 decision bands (Accept/Minor/Major/Reject) that drive a target-met early stop, and a Devil's Advocate concession-threshold guard that blocks acceptance on unresolved critical findings. Maintains a worklog and snapshots each iteration so revert is real, not symbolic. TRIGGER when the orchestrator delegates Step 5 or when the user asks to "refine the draft", "iterate on the paper", or "run peer review on this paper".

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

Review uncommitted code changes to find unreasonable design, unfinished requirements, potential bugs, missed reuse opportunities, and optimization opportunities. Use when the user asks for a review of pending, uncommitted, or unpublished code changes and expects both findings and concrete improvements.

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

Use when published content has to be audited — pull channel data, classify winners and losers by percentile across pillar, format, and hook, find the pattern behind performance, and decide what to keep, kill, or scale. Trigger on 'content audit', 'which posts are working', 'content performance review', 'why did that one go viral', 'our reach is dropping', 'evaluate what we posted last month'. Also use when the user only says content does not seem to work anymore. Not for — the plan for next period built on these findings, see `40-next-content-plan-global`; paid ad account review, see `21-ads-audit-global`; the stakeholder report, see `07-marketing-report-global`.

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

Cyber threat intelligence and OSINT analysis toolkit. Runs structured investigations and delivers analyst-grade intelligence products with sourced, trust-scored findings. Use for OSINT and CTI cases, digital-footprint and exposure review, domain/subdomain/DNS/certificate recon, web-infrastructure pivoting (favicon hashes, tracker IDs, TLS certs, phishing-kit fingerprinting, campaign clustering), username/email/phone enumeration, breach and infostealer-log triage, image forensics, geolocation, crypto-wallet and IBAN/bank-account tracing, darknet search, M365/Azure and SaaS tenant recon, China/Sinophone recon (ICP filings, PRC corporate registries, Baidu/FOFA/Quake/ZoomEye), vulnerability and ransomware lookup, threat modeling, PII redaction, and structured reporting. Commands include /case, /sweep, /query, /webpivot, /username, /phone, /email-deep, /breach-deep, /icp, /cn-corp, /iban, /stealer-log, /exposure, /threat-model, /report, /brief, /redact, /apikeys.

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

Expand all TaskMaster tasks with deep research before coding begins. Reads tasks.json, launches parallel research agents per task in waves using the research-expander agent. Writes findings back to tasks.json. Part of the prd-taskmaster toolkit. Use after PRD is parsed and before implementation. Invoke with /expand-tasks.

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

Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.

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

Use after /gsd-audit-uat when the user wants the findings fixed, not just listed. Classifies each issue as auto-fixable or manual and fixes the auto-fixable ones with test verification and atomic commits; --severity sets the floor.

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

Use after gsd-code-review has written REVIEW.md, when you want its Critical and Warning findings fixed. Spawns the fixer agent, commits each fix atomically and writes REVIEW-FIX.md (--all, --auto to iterate).

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

Posts sanitized batches of PR review comments or replies through configured review tooling. Use after review-ticket when findings are approved for publication.

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

Application Security Posture Management persona. Correlates findings from SAST, DAST, and SCA tools, deduplicates noise, maps vulnerabilities to specific code commits, and generates targeted remediation PRs.

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

Captures redacted, provenance-aware cybersecurity observations with shared status fields, independent ground truth, and honest limitations. Use when recording exercise evidence, findings, validation results, or security-review handoffs.

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

Define a repository review policy fixing what each review pass checks, how severities rank, which paths are skipped, the nit cap, and who approves. Use when review findings feel inconsistent or noisy, or when tuning an automated reviewer.

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

Record a vetted Hex package version in hex_vet.exs after a security review — manages the audit ledger, not the scanner. Use to approve a dep after /phx-deps-audit findings or to initialize hex_vet.exs.

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

Record a vetted Hex package version in hex_vet.exs after a security review — manages the audit ledger, not the scanner. Use to approve a dep after /skill:phx-deps-audit findings or to initialize hex_vet.exs.

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

Triage review findings interactively — approve, skip, or prioritize; Use after $elixir-phoenix:phx-review to filter…

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

Review changed Elixir/Phoenix code read-only. Check requirements, cite evidence, deduplicate findings, and return a severity-based verdict.

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

Record a vetted Hex package version in hex_vet.exs after a security review — manages the audit ledger, not the scanner. Use to approve a dep after phx-deps-audit findings or to initialize hex_vet.exs.

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

Plan features spanning multiple domains: billing (Stripe), auth (RBAC), real-time (Presence), webhooks, jobs (Oban). Use when designing interconnected systems or converting review findings into tasks.

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

Plan features spanning multiple domains: billing (Stripe), auth (RBAC), real-time (Presence), webhooks, jobs (Oban). Use when designing interconnected systems or converting review findings into tasks.

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

Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.

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