「hub」の検索結果

Collect project brief and stack choices, then output canonical project-config.json for downstream web-builder skills.

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

Plan reproducible ML experiment runs with explicit parameters, metrics, and artifacts. Use before model training to standardize tracking-ready experiment definitions.

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

Aggregate SAST, SCA, DAST, secrets, API, frontend, and backend security checks into one report.

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

Test egress and DLP controls using synthetic canary data across authorized exfiltration channels.

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

Design phishing and social engineering simulations with explicit authorization and measurable outcomes.

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

Assess lateral movement and pivot paths across authorized internal trust boundaries.

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

Test APIs against OWASP API Security Top 10 including discovery, auth abuse, and protocol-specific checks.

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

Retest remediated findings, detect regressions, and generate remediation status and certification artifacts.

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

Design Gmail, Drive, Sheets, and Calendar automations with scope-aware plans. Use for repeatable daily task automation with explicit OAuth scopes and audit-ready outputs.

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

Build transformer fine-tuning run plans with task settings, hyperparameters, and model-card outputs. Use for repeatable Hugging Face or PyTorch finetuning workflows.

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

Integrate authentication and authorization flows with provider-specific setup and RBAC safeguards.

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

Run controlled exploitation against confirmed vulnerabilities while enforcing scope and authorization gates.

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

Aggregate findings and generate multi-format pentest reports with remediation roadmap and risk scoring.

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

Build repeatable data-to-Docs pipelines from Sheets and Drive sources. Use for automated status reports, template-based document assembly, and scheduled publishing workflows.

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

Review a GitHub pull request and provide structured feedback with severity ratings

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

Fix a GitHub issue by reading the issue, finding relevant code, implementing a fix, and creating a commit

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

Draft or refine IDD-ready GitHub issues, roadmap issues, and sub-issues before the normal IDD execution loop begins. Use when a request is too large or ambiguous for one reviewable change, when work needs decomposition or dependency encoding, or when the user asks for issue drafting, roadmap planning, or parallelizable task breakdown.

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

自动搜索、抓取、改写技术内容，生成适合微信公众号的中文科普文章。涵盖AI大模型、GitHub开源工具、技术话题。当用户说"写一篇关于XXX的文章"、"帮我研究XXX"、"生成公众号文章"时使用。

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

Conditional discipline for projects hosted on a git forge (GitHub, GitLab, Forgejo, …): branch↔PR mapping, self-contained PR prose, review-on-forge, merge consent, and the forge audit. Trigger when: - Opening, updating, reviewing, or merging a pull/merge request. - A campaign's integration branch is ready to surface on a forge. - Auditing forge-side presence at merge-consent or campaign CLOSE. - Prompt contains: /forge, pull request, PR body, merge request, forge discipline, PR review, stacked PR.

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

Shape every agent comment as a short typed brief the owner can triage in seconds — 🔴 issue · 💡 proposal · ✅ done · 🔀 choice · 🛠 action · 👀 review — with all the depth collapsed behind it. Enforced by the require-owner-brief hook. Use before posting ANY GitHub comment as an agent, or when asked to "make this shorter", "brief me", "just tell me what I need to do".

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

Generate a daily "where are we?" digest from this repo's GitHub epics — a render-only HTML + plain-text email summarising the last 24h of activity plus a progress snapshot of every open epic. Use when asked for a "daily digest", "epic report", "status rapport", "what moved this week", or "where are we on the epics".

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

Symptom → root-cause lookup table for nuxt-crouton's recurring failure modes — exact error strings mapped to their known cause, fix, and evidence issue. Use when you hit an error you don't recognize in this repo, before debugging from first principles. Trigger phrases and symptoms: "Cannot resolve entry module .nuxt/hub/db/schema.entry.ts", "Could not load '@fyit/crouton'", "No migrations present", "No schema files found", "$setup.t is not a function", "does not provide an export named 'Map'", "no such table: translations_ui", "collection pages 500 in production", "the build was green but the app is broken", "is this a known issue?".

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

The map of nuxt-crouton's GitHub workflows and the deploy-pipeline anatomy — what each workflow gates, how a merge reaches Cloudflare, which secrets/tokens exist where, and how the agent-pipeline workflows chain. Use when a CI check fails and you need to know what it is, when asked "which workflow deploys X / why did staging update / what does this check gate / where is that secret / why didn't my label trigger anything", when wiring a new app into CI, or when debugging a deploy that never fired. Trigger phrases: "what runs on merge to main", "map of the workflows", "WORKER_SECRETS_JSON", "why is the daily sweep not running", "deploy-apps vs deploy-app", "which token does this workflow use".

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

Before creating a GitHub issue or epic, search for an existing related one and force a reuse / replace / new decision — so the issue-first flow can't silently mint a duplicate. The create-time half of the dedup gate (the pickup-time half is /issue-sanity-check). Use whenever you're about to open an issue/epic, or run /issue-dedup. Backed by a hard PreToolUse hook on issue_write create.

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