549 件 ・ 関連度順
概要と使いどころ
Drafts or opens a GitHub pull request, runs changed-area preflight checks, and commits validated preflight repairs, and routes Azure DevOps repositories to the backlog-management pull request protocol. Use when a user asks to prepare, create, or update a pull request on GitHub or Azure DevOps.
日本語の概要は準備中です。原文の説明を表示しています。
Run /document `pr` | `changelog` | `release-note` | `postmortem` (or let it ask) to write the human facing prose about a change. Drafts from the real commits and diff, writing to the right place. Does not write code, tests, or specs.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked 把这段黑话翻译成人话, 这句话到底什么意思, 帮我把周报去黑话, 用大厂黑话改写这段, 互联网黑话词典, 对齐抓手闭环是什么意思, or translate Chinese internet-company jargon (互联网黑话) into plain words and back. Produces a line-by-line translation of 黑话 into plain Chinese with what each sentence actually commits to (who, what, by when), a rewrite at the chosen tone (白话, 得体职场, or 满分大厂味 parody), a 40-plus term glossary with plain meanings, and a 周报去黑话 mode that turns a jargon-heavy weekly report into one a reader can act on.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a list of changes, commits, or PRs into clean release notes / a changelog entry. Use when asked to write release notes, a changelog, or a version announcement from raw changes. Produces a Keep-a-Changelog-style entry grouped by type (Added/Changed/Fixed/etc.), written for users — surfacing breaking changes and upgrade notes up top. To go straight from a raw git log use changelog-generator instead.
日本語の概要は準備中です。原文の説明を表示しています。
Run all reference benchmarks under benchmarks/eval/ and refresh the reference-table cells in benchmark_*.py. Auto-detects host hardware (H200/H100/H800/...). For each row's matching hw entry: replace cells in place. For new hardware or a new workload tag: append a new row to the section's table. Local-Pipeline-Result tables are skipped. One slash command runs everything end-to-end and auto-commits.
日本語の概要は準備中です。原文の説明を表示しています。
SCM (software configuration management) and Git — branching, merges, conflicts, worktrees, baselines, audit readiness, plus Conventional Commits and safe staging.
日本語の概要は準備中です。原文の説明を表示しています。
Manage Git branches, merges, conflicts, commits, and release baselines. Use for repository history and change-management operations.
日本語の概要は準備中です。原文の説明を表示しています。
Combines all git commits for a change into a single commit and pushes it to gerrit. Use when you push to gerrit.
日本語の概要は準備中です。原文の説明を表示しています。
Guides Metronome usage-based billing integration decisions — event ingestion (single and batch, idempotency, billable metrics), contract design (rate cards, overrides, dimensional pricing, products), invoicing lifecycle (grace periods, finalization, Stripe sync), credit and commit management (prepaid, postpaid, thresholds, auto-recharge), and Stripe integration (arrears invoicing, tax providers, line item limits). Use when building, modifying, or reviewing any Metronome integration — including ingesting usage events, creating customers, contracts, or rate cards, designing billable metric group keys, managing credits and commits, configuring invoicing, syncing invoices with Stripe Billing, billing AI applications for token usage, setting up self-serve (PLG) pricing, reviewing customer health, commit burn, portfolios, or renewals, or migrating from Stripe Billing Meters to Metronome.
日本語の概要は準備中です。原文の説明を表示しています。
Git operations: commits, branches, PRs, and conflict resolution
日本語の概要は準備中です。原文の説明を表示しています。
Use for every request to commit changes or draft a commit message. Creates Sentry-style conventional commits with issue references.
日本語の概要は準備中です。原文の説明を表示しています。
Generate one short Conventional Commits squash message describing only the net diff between the PR's base and head, set its header as the PR title, validate it with the repository's commitlint and both copy its description to the clipboard and display it, when asked for a squash message. Works in any Scenario repository, whatever its default branch.
日本語の概要は準備中です。原文の説明を表示しています。
Live-site visual QA audit with fix loop. 10-category checklist (~80 items) including AI Slop Detection (10 blacklisted patterns). Atomic commits per fix. Before/after screenshots. A-F grading. Parallel cross-model code-level design audit. Modes: Full, Quick, Deep, Diff-aware, Regression.
日本語の概要は準備中です。原文の説明を表示しています。
Fully automated ship workflow: pre-flight, merge base, run tests, coverage audit, pre-landing review, design review, adversarial review, version bump, CHANGELOG generation, TODOS.md update, bisectable commits, push and PR creation, auto-sync docs via document-release.
日本語の概要は準備中です。原文の説明を表示しています。
Auto-generate changelog from git commits
日本語の概要は準備中です。原文の説明を表示しています。
Generate changelogs from recent commits and merged PRs
日本語の概要は準備中です。原文の説明を表示しています。
Prevent 此地无银三百两式 residue: finalize artifacts without echoing rejected session-only alternatives into labels, metadata, commits, PRs, or handoffs. Use after corrections or discarded proposals. Not for ordinary deletion, deprecation, migration, or exclusions materially required for safety, accuracy, compatibility, audit, quotation, or requested comparison.
日本語の概要は準備中です。原文の説明を表示しています。
Generate changelogs and release notes from Conventional Commits with semver bump detection, Keep a Changelog formatting, and monorepo scopes. Use when preparing releases, enforcing commit standards, or automating release notes.
日本語の概要は準備中です。原文の説明を表示しています。
Initialize a PM Brain — a markdown-native second brain for a product operator (PM, product lead, founder, or anyone accountable for one product or initiative) doing judgment-heavy work with scattered inputs. Detects greenfield vs. migration mode, runs a focused interview, copies the deterministic scaffold into the working directory, populates placeholders from interview answers, runs a self-test, and commits. Use when invoked via `/pm-brain` or when the user asks to set up a PM Brain.
日本語の概要は準備中です。原文の説明を表示しています。
Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.
日本語の概要は準備中です。原文の説明を表示しています。
TrailSnap 仓库提交、推送、需求平台与 PR 工作流规则。Use when preparing commits, pushing branches, managing the corresponding platform requirement, creating or merging pull requests, or monitoring PR CI in this repository; do not use for ordinary code changes that do not involve submission.
日本語の概要は準備中です。原文の説明を表示しています。
Update an existing pull request with new changes. Use when the user wants to update a PR, push follow-up changes to a PR, refresh a PR description, or sync a PR with latest commits. Triggers on: update pr, update-pr, update the pr, push to pr, refresh pr, sync pr, update pull request.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a user-facing changelog from recent commits/PRs across watched repos - write it in-repo (Keep a Changelog format) or open a cross-repo changelog PR on a docs/marketing repo.
日本語の概要は準備中です。原文の説明を表示しています。
Pull framework updates from the upstream Aeon repo into this instance - 3-way merges canon's new commits into a PR, never clobbering operator config.
日本語の概要は準備中です。原文の説明を表示しています。