「ticket」の検索結果

Weekly on a Friday, conditional browser lane. Scores the week from the ledgers with a source beside every number and an estimate nowhere, reads the review and rating movement off the member's own listing screens, replays the browser flows the weekday routines depend on, and names the one product change that would have removed the most tickets this week. It sends only where you released the channel, never posts, never resolves anything, spends only where you released it, and never touches a credential.

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

Weekdays, conditional browser lane. Reads the ticket ledger and the account, billing, and usage surfaces the member named, and decides which paying customers are about to leave. Every flag is a dossier carrying the trip wires that fired, the exact evidence behind each one, that account's whole history, and one suggested save with its cost and the screen it happens on. It reads billing screens and touches no control on them: a refund, a credit, a plan change, and a cancellation are named and never made.

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

Implement work from a spec, ticket, or agreed conversation. Use explicitly when the user wants an existing plan carried through to working code.

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

Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.

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

Summarizes GitHub PR, GitLab MR, or Azure DevOps PR metadata, review threads, changed files, and template completeness. Use during review-ticket or code-review workflows when PR/MR context exists.

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

Maps acceptance criteria to implementation evidence, tests, and scope creep. Use during review when a diff, PR, ticket, or story includes numbered ACs.

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

Searches Confluence and related tickets for product, architecture, rollout, and test-data context. Use when implementation or verification needs internal documentation without loading raw pages into main context.

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

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

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

Quarantines an intermittently failing test behind a ticket with an owner and expiry, assigns a root-cause bucket from isolated reruns, and defines when the test leaves quarantine. Use when a test is a QUARANTINE_CANDIDATE or fails without a code change; not for deterministic failures.

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

Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.

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

Validate Jira/JPD ticket reference and create a feature branch

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

Performs root-cause analysis of a bug — from a GitHub issue, an issue URL, or a free-text description — before any reproduction or fix is written. TRIGGER when: triaging or diagnosing a bug, investigating why something misbehaves, an issue number/URL handed over for analysis, needing the root cause before touching code. DO NOT TRIGGER when: a failing reproduction test already exists and you are ready to fix → opsmill-dev-fixing-bugs; writing that reproduction test → opsmill-dev-test-driving-bugs; capturing a new bug as a ticket → opsmill-dev-creating-issues.

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

Stress-tests a fuzzy or vague feature idea before any PRD, spec, or ticket is written. TRIGGER when: the user has a fuzzy feature idea — one or two paragraphs, vague on users / scope / success — and wants to harden it, or says "grill / stress-test / pressure-test this idea." DO NOT TRIGGER when: the idea is already turned into a spec or PRD; bug fixes or refactors; the idea is hardened and you are ready to write the PRD → creating-prd.

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

规划一大块工作——超过一次 agent 会话能容纳的体量——在你的 Issue 跟踪器上以共享的决策 ticket 地图形式呈现，逐个解决，直到通往目的地的道路变得清晰。

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

基于 spec 或一组 tickets 实现工作内容。

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

在代码中实现 /to-spec 与 /to-tickets 的产物。

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

Builds an app, site, bot, or feature end-to-end from a dictated idea — requirements, briefing, spec, tickets, subagents, review, acceptance — with a live dashboard, for users who expect a finished result without reviewing specs or code. Starts only on /autopilot; a bare /autopilot resumes an interrupted run.

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

Use when reviewing, designing, or modifying Java enterprise systems from a maintainer-authored or maintainer-sanitized NIS2 engineering evidence inventory. Supports essential or important entities, critical-sector services, managed service providers, supply-chain dependencies, and cybersecurity incident escalation obligations without ingesting raw code, logs, runbooks, tickets, provider documents, or other operational free text. Part of Plinth Toolkit

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

Jira Cloud integration for issue management and search. This skill should be used when working with Jira tickets, searching issues with JQL, creating or updating issues, adding comments, or transitioning issue status. Covers REST API v3 and Jira Query Language.

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

Triage a single security finding — from a scanner, audit, advisory, or report — to a defensible disposition with a mitigation plan, false-positive justification, or accepted-risk writeup. Use when the user mentions 'triage this finding,' 'is this a real vulnerability,' 'mitigation plan,' 'false positive,' 'accept this risk,' 'compensating controls,' 'risk justification,' 'security ticket,' 'CVSS this,' 'should we fix this,' 'disposition,' 'sign off on,' or has a single security finding and needs to decide what to do.

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

Learn what the user cares about, prepare useful work privately, and prompt them with clear visual decisions. Use to start or continue Agency or handle its tickets.

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

This skill should be used when handling issue intake rotation duties for the Positron repository. It provides workflows for reviewing and organizing new issues, responding to discussions, handling support tickets, and searching for related content. Use this skill when on intake rotation duty, when helping someone with intake tasks, or when learning the intake rotation process.

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

QA engineering workflows on top of Playwright. Use when a QA engineer asks to design test cases from a ticket, PRD or acceptance criteria, decide what to automate, write a bug report from a failing test or trace, convert manual test cases (TestRail, Xray, CSV) into Playwright specs with case-ID traceability, or review Playwright test code and pull requests.

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

Use when attacking a Windows Active Directory domain — Kerberos roasting/delegation, coercion + NTLM/Kerberos relay (CVE-2025-33073), ADCS ESC1-16 (EKUwu), ticket forgery & DCSync, dMSA BadSuccessor (CVE-2025-53779), BloodHound attack-path enumeration, domain dominance

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