「clo」の検索結果

Detect path traversal vulnerabilities in a codebase using a three-phase approach: recon (find file-loading sinks with dynamic paths), batched verify (trace user input and mitigations in parallel subagents, 3 sinks each), and merge (consolidate batch results). Requires sast/architecture.md (run sast-analysis first). Outputs findings to sast/pathtraversal-results.md. Use when asked to find path traversal, directory traversal, or file disclosure bugs.

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

Connects a domain the user already owns (bought at another registrar) to their DropTheHassle site, free, with one A record. Use when the user says "use my own domain", "connect my domain", "add a custom domain", "point my domain to my site" or already has a .com at GoDaddy, Namecheap, Cloudflare or similar. Gets the A record from DropTheHassle, shows it to the human to set at their registrar, then checks HTTPS is live. Never edits DNS at the registrar for them. For a name they don't own yet, use buy-domain.

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

Publishes (deploys) a built website or web app to a free HTTPS link, then your own .com with no DNS. Use when the user wants to deploy a website, publish a website or host a website, or says "go live", "make it live", "put this live", "put it online", "publish my site", "deploy my website", "host my website", "share it with friends", "send my friends a link", "get a link", "make it public", "it only works on localhost" or "get a .com", or asks to deploy or host a site built with an AI tool (Claude Code, Cursor, Codex, Windsurf, Lovable, Bolt, v0, ChatGPT), or mentions DropTheHassle, and has not picked another host. Covers building first, CLI or MCP setup, deploying, Update and Restore, the claim link, the live check, linking a server part the user hosts on AWS, Google Cloud, DigitalOcean or their own server with set_backend, and domain search. The agent never spends money. The human pays.

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

Use when the user wants to read, search, summarize, draft or triage their Apple Mail / Gmail / Outlook / iCloud email in Apple Mail on macOS. Powered by LMCP's Mail tools, which are macOS-only.

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

Pick the next work in an epic or bead graph; closed is not proven. Use when: asked what is next or whether an epic is done.

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

Operate Bitbucket Cloud or Data Center repositories, pull requests, branches, issues, pipelines, permissions, and webhooks with bkt. Use when a request names Bitbucket or bkt; confirm the platform before platform-specific commands.

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

First-time Archcore setup. Wires the host (MCP config, hooks, CLAUDE.md/AGENTS.md managed block), measures the authored context the repo already holds, then composes a first-day seed — stack rule, run guide, data-model, integrations, config, entry points, public surface, a linked architecture overview, and specs for the top hotspot modules — shown in ONE preview and created on a single confirm. Modes, named as the first word: init import converts the repo's authored context — CLAUDE.md, AGENTS.md, .cursor/rules and other agent instructions, ADR and RFC folders, contributor docs, internal pages of a published docs site, recoverable git history — into native typed documents with no import marks, staged by a plan when the volume is large; init refresh adds facts that appeared since, or drills into one domain with init refresh <domain>. Use on a fresh clone, empty `.archcore/`, 'set up archcore', 'migrate our CLAUDE.md to archcore', 'import our docs and ADRs', or to wire host configs. Not for individual docs or planning.

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

Plan a feature or initiative through a computed route: the conductor derives the canon delta and assembles the document package — from a zero-document null route for small fixes to an umbrella PRD with one spec per capability for large initiatives. Modes, named as the first word: sdd (full package), sources (MRD → BRD → URD) for market research, customer discovery, and business or user requirements, iso (BRS → StRS → SyRS → SRS) for ISO 29148 and regulated work, research for a technical investigation — never market research — that the research instrument closes either by scope coverage (a research document) or by a recommendation (an rnd). Explicit form: plan research <topic>. Use for 'plan the X redesign', 'create a roadmap', 'plan a new feature', 'I need market research before we plan', 'we're regulated — start the ISO requirements cascade', 'investigate X before we plan', 'compare the alternatives for Y' — a new investigation, not a finished report already in hand. Not for recording a decision or documenting existing code — use /archcore:document. Not for checking docs against code — use /archcore:review.

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

Context engineering: compaction, progressive disclosure, structured notes via AgentDB. Triggers: tokens, compaction, memory, handoff, summarize, context window.

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

中文阶段收尾技能。用于完成一个阶段、准备开新对话、需要更新状态快照、冻结模块、整理已完成任务和下一步任务时。触发语包括"阶段收尾""帮我收工""准备开新对话""更新快照""冻结阶段""总结当前状态"。

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

Use when implementing a new Spark expression in DataFusion Comet. Walks through cloning latest Spark master to study the canonical implementation, checking the upstream datafusion-spark crate before writing native code, building the Comet serde and Rust wire-up from the contributor guide, then running audit-comet-expression to drive a test-coverage iteration loop.

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

Triage open Comet issues marked `requires-triage` per the project bug triage guide. Classifies each issue as a bug or an enhancement, applies the recommended type (`bug`/`enhancement`), priority, and area labels, removes `requires-triage`, and files a dated summary issue listing what was done. A human reviews the summary issue and closes it when satisfied.

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

CP-7 retrospective: audit checkpoints, evidence quality, action items, and harvest candidates. Closes the V-model cycle and feeds the next run. Use via /retro after ship, escalate, or significant session.

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

Run a large, multi-session goal (e.g. shipping a whole side product) through the full V-model closed loop, one phase at a time, with cross-session state and a final north-star acceptance gate. Ultragoals never downgrade the lane: every phase runs CP-1→CP-6 with adversarial verification. Opt-in: invoke with /ultragoal or by calling something a long-running goal. Ordinary work does not run this.

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

Use when the contribution of an American Economic Journal: Microeconomics (AEJ: Micro) manuscript is fuzzy or oversold relative to the closest existing results. Stakes the theorem-relative delta against the nearest theory; it does not build the model (see aejmic-theory-model) or frame the prose (see aejmic-writing-style).

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

Use when running the final pre-submission preflight for Agricultural Systems (AgSy) via the current Elsevier submission path / Editorial Manager — article-type selection, abstract <= 250 words, Highlights, graphical abstract, CRediT and declaration-of-interest statements, funding/AI disclosures, reference style, and data/code/model availability. Final checks; it does not draft content.

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

Use when positioning the contribution of an American Economic Review: Insights (AER: Insights) short-format manuscript against the closest published work in one or two tight paragraphs. Stakes the gap concisely; it does not write the full literature review (there is no room for one).

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

Use when running the final pre-submission preflight for AEJ: Economic Policy via the AEA online submission system — single-blind review front matter, JEL codes, submission and publication fees, format, the Data and Code Availability Statement, and disclosure. Final checks; it does not draft content.

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

Use when running the final pre-submission preflight for an American Economic Journal: Applied Economics (AEJ: Applied) manuscript via the AEA ScholarOne system — single-blind review front matter, JEL codes, submission and publication fees, format, disclosures, and AEA data-policy readiness. Final checks; it does not draft content.

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

Use when running the final pre-submission preflight for the American Economic Journal: Macroeconomics (AEJ: Macro) via the AEA submission system — membership-scaled fee, JEL codes, PDF and length rules, ≤100-word abstract, disclosure statements, and data/code readiness. Final checks; it does not draft content.

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

Use when positioning an ACM CCS submission against the security big-four and specialist literature, including arXiv preprints, prior CCS/S&P/USENIX/NDSS papers, concurrent disclosures, CVE and advisory records, and the attack-and-defense lineage that a SIGSAC program committee expects to see credited.

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

Use when explaining or planning around ACM CCS peer review, the two-cycle HotCRP workflow, decision categories including minor revision, the rebuttal window, the adversarial reviewer pool, ethics and disclosure scrutiny, meta-review dynamics, and ACM proceedings outcomes.

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

Use when the mechanism analysis for a 《会计研究》 (Accounting Research) manuscript is missing or mis-specified — the channel must be an information mechanism (reduce information asymmetry, raise disclosure quality, constrain earnings management, improve audit assurance), not a generic pricing or financing channel. Use after the main result holds.

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

Use when strengthening reproducibility evidence for an ACL paper reviewed through ACL Rolling Review, covering the Responsible NLP checklist end to end, hyperparameter and compute reporting, prompt and decoding disclosure for LLM experiments, data contamination auditing, variance across runs, and checklist-to-paper consistency.

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