「detect」の検索結果

Detect, triage, de-duplicate, and raise compiler bug reports when an agent encounters a likely compiler defect during implementation, review, testing, or issue work. Use when a task surfaces an ICE, panic, wrong accept/reject behavior, miscompile, lowering/emission bug, diagnostic bug, formatter/LSP/frontend drift, or other likely compiler/tooling defect; pause current work, minimize the repro, decide whether the bug blocks the task or has a valid workaround, check whether it is already reported, and then use create-github-issue to raise the bug.

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

Write the postmortem for an incident, in its incident channel, once it is mitigated or resolved. Use on "write up this incident", "postmortem", "incident summary", "what happened here for people who weren't around", "draft the retro", or when the oncall memory says incidents of this severity get one. Reads the incident channel (and the alert thread it came from), the investigation findings and the data behind them, and writes a one-screen, zero-context write-up: what happened, impact with numbers, detection, timeline with durations, why it happened, what fixed it, follow-ups with proposed owners, and one before/during/after chart. Posted and pinned in the incident channel as its final pinned post, with edit requests updating that one pinned post in place — unless the person or the team's conventions say write-ups live elsewhere, in which case it is written there and only a link is posted, nothing pinned. A person edits and publishes it; never assigns blame.

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

Maintain local bcrypt and Argon2id password generation, prefixed imports, reusable hashing configuration/parser, duplicate detection, changes, resets, credential revocation, and authentication work equalization.

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

Use when searching for buying signals, detecting intent data, scoring prospect readiness, or monitoring accounts for trigger events. Triggers: 'scan for signals', 'find buying signals', 'who is ready to buy', 'intent signals', 'signal scoring', 'account signals'.

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

Story Driven Development workflow. Use this skill whenever working in a project that has `.sdd/config.yaml`, or when the user mentions SDD, sdd sync, story driven development, spec-driven development, change requests, bugs, or asks to implement a feature described in `product/` or `system/`. Also trigger on phrases like "sync the docs", "mark synced", "apply this CR", "fix this bug" when an SDD project is detected.

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

Go-to-market engineering for the Yupcha portfolio (OmniVoice-Studio, the Clay-alternative in this repo, ResuBird). A closed set of executable verbs — research, audit, draft, measure, prepare, publish, escalate — each with a typed contract, required sources, and a risk tier. Use when: (1) researching ICP/competitors/channels/prior art, (2) auditing our own properties for what's actually broken (dead pricing pages, 404ing clone URLs, unfilled demos, licence detection, watermark coverage), (3) drafting docs/comparison pages/release notes/launch copy, (4) measuring real numbers against GOAL.md, (5) preparing a Show HN or a listing up to the send button, (6) any question about whether a GTM action is allowed. Triggers: 'gtm', 'go to market', 'launch', 'show hn', 'growth', 'marketing', 'positioning', 'icp', 'competitors', 'outreach', 'cold email', 'audit our', 'is it ok to', 'can we post', 'promote'.

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

Odoo engineering workflows for addon development, codebase exploration, debugging, architecture/refactor review, manifest/docs sync, and routing to migration work. Use when the user mentions Odoo, addons, modules, manifests, models, XML views, security CSVs, record rules, Odoo shell, OWL/QWeb/assets, or when an Odoo codebase is detected.

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

Use when the user wants to post or schedule to Bluesky through Publora. Handles the 300-character cap, auto-detected hashtags and links, up to 4 images, and videos. Alt text cannot be set through the API. Needs a Bluesky app password, never the main password. Not for Mastodon (use social-post).

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

Write or rewrite prose so it sounds like a human wrote it — not a frontier model. Named in homage to Rabindranath Tagore, whose prose carried what frontier models reach for and miss: a point of view, specificity over abstraction, and restraint over puffery. Merges two complementary approaches: a 29-pattern catalog of AI tells (from humanizer) plus an 8-rule operating system with an 8-dimension scoring gate (extending stop-slop). Use when drafting, editing, or reviewing any prose: essays, posts, docs, reports, emails. Detects and removes inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary, passive voice, negative parallelisms, filler phrases, inanimate-verb constructions, narrator-from-a-distance voice, and metronomic rhythm. Adds back the things AI writing usually lacks: point of view, stakes, specificity, restraint, varied rhythm, and trust in the reader.

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

Use when starting any new project from scratch. Asks for project identity (name, GitHub org, Cloudflare account), detects project type, sets up design system, staging+production, i18n from day 1, SEO foundation, AGENTS.md manifest, test infrastructure, 8-gate deploy pipeline, and disciplined development workflows. Prevents wrong deploys, redundant repos, and technical debt from day 0.

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

Booking & Calendar CRO Engine — Packages all booking, scheduling, .ics download, and Google Calendar integration into a revenue-boosting system. Auto-detect industry → select matching pattern → generate calendar engine + booking UI + export logic. Integrates with cm-google-form (form → sheet) and cm-ads-tracker (conversion events). ALWAYS trigger for: booking, appointment, calendar, reminder, download ics, google calendar, add to calendar, book appointment, schedule, "create booking", "add scheduling", "appointment reminder system", "calendar CRO", "reduce no-show"

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

Code hygiene gate — detect and eliminate dead code, duplicates, naming mess, and code smells. TRIZ-powered. Run after features, before PRs, during debt sprints.

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

End-to-end ad conversion tracking: Meta Pixel+CAPI, TikTok Events API, Google Ads Enhanced Conversions, GTM, attribution. Auto-detects industry, maps standard events, outputs a developer-ready implementation doc. Use for pixels, GTM, CAPI, ROAS, or 'set up tracking' requests.

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

Skill Chain Engine — compose skills into automated pipelines. One task triggers multi-skill workflows with progress tracking, auto-detection, and step management.

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

Detect documentation and architecture-model drift by comparing source-of-truth code (CLI commands, flags, env vars, GH Action inputs/outputs, package structure, pipeline stages, providers, adapters, platforms) against web docs, README, and LikeC4 architecture model (.c4 files). Use when files that define the user-facing interface or internal structure change, when the user asks to check docs, or when mentioning doc drift, architecture drift, stale docs, or documentation sync.

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

Lints Protocol Buffer definitions using the Buf CLI ruleset and validates gRPC service contracts. Detects breaking changes between proto revisions using buf breaking with git integration.

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

Uses htmltest to crawl generated documentation or static site output, detect broken internal and external links, and return a link-focused validation report before deploy. This is a narrow docs QA skill for agents validating already-built HTML, not a generic site generator or crawler listing.

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

A fast, configurable secrets scanner built by the creator of Gitleaks and backed by Aikido Security. Betterleaks detects leaked passwords, API keys, and tokens in git repositories, directories, and stdin with CEL-based validation and parallelized scanning.

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

Scan a repository for secrets, keep an auditable baseline, and review only newly introduced findings during commits or CI checks.

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

Run structured prompt-injection attack and defense experiments against an LLM-integrated app before production by measuring attack success and testing detection or recovery pipelines.

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

Runs CloudWatch Logs Insights queries via AWS SDK for JavaScript v3. Analyzes Lambda cold starts, API Gateway latency, and ECS container logs. Generates anomaly detection alarms with math expressions.

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

Executes structured diagnostic runbooks when CloudWatch Anomaly Detection triggers alarms. Uses the AWS SDK CloudWatch client (GetMetricData, DescribeAlarms) to gather context and suggest remediations.

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

Scans AWS CloudWatch Logs using the CloudWatch Logs Insights API and CloudWatch Anomaly Detection API. Identifies unusual error patterns, latency spikes, and log volume anomalies across log groups.

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

Investigates anomalous patterns in AWS CloudWatch Logs using the CloudWatch Logs Insights API and CloudWatch Anomaly Detection. Correlates log spikes with deployment events via AWS CodeDeploy API.

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