2,212 件 ・ 関連度順
概要と使いどころ
Create a reviewable GitHub pull request from the current branch with a Conventional Commits title, a concise evidence-based body, and before/after screenshots for UI changes. Use when asked to open, create, publish, or prepare a PR.
日本語の概要は準備中です。原文の説明を表示しています。
Reviews code changes and provides actionable feedback. Use when the user asks to review a PR, diff, commit, or code changes. Triggers on "/review", "review this PR", "review my changes", "code review".
日本語の概要は準備中です。原文の説明を表示しています。
Commit and push changes, then create a new PR or append to an existing one.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze branch commits and consolidate iterative modifications.
日本語の概要は準備中です。原文の説明を表示しています。
Automated code review and fix for local branches, PRs, commits, and files. Supports single-agent interactive fix and multi-agent adversarial review with auto-fix.
日本語の概要は準備中です。原文の説明を表示しています。
Accept screenshot baseline changes and commit the updated version.json.
日本語の概要は準備中です。原文の説明を表示しています。
Execute git operations on behalf of Workers who don't have git credentials. Use when a Worker sends a git-request: message to clone, push, pull, commit, rebase, or perform any git operation.
日本語の概要は準備中です。原文の説明を表示しています。
Assess tests for an identified code or test change, feature, PR or commit. USE FOR: review changed behavior or regression tests, prove pre-fix/missing behavior is detected, revision-bound red-green evidence. Polyglot. DO NOT USE without an identified change: hypothetical mutations or general suite blind spots (test-gap-analysis). Also exclude per-test readiness/A-F grades (grade-tests), coverage (coverage-analysis), new suites (code-testing), or mutation engines.
日本語の概要は準備中です。原文の説明を表示しています。
Generate an eight-panel repository statistics infographic with individual-PR diff histograms and human/agent comment and commit comparisons.
日本語の概要は準備中です。原文の説明を表示しています。
Never read .env files or write secrets to .squad/ committed files
日本語の概要は準備中です。原文の説明を表示しています。
Web2 recon pipeline — subdomain enumeration (subfinder, Chaos API, assetfinder), live host discovery (dnsx, httpx), URL crawling (katana, waybackurls, gau), directory fuzzing (ffuf), JS analysis (LinkFinder, SecretFinder), continuous monitoring (new subdomain alerts, JS change detection, GitHub commit watch). Use when starting recon on any web2 target or when asked about asset discovery, subdomain enum, or attack surface mapping.
日本語の概要は準備中です。原文の説明を表示しています。
Draft flexible daily or weekly schedules around a user's priorities, availability, energy patterns, and fixed commitments. Use for day planning, deadline reverse-planning, focus protection, or a time audit.
日本語の概要は準備中です。原文の説明を表示しています。
Open a pull request on the Kiln repo for a human to complete. The title gets a `WIP: ` prefix and a semantic-commit type. The description keeps the human-only header of the PR template as empty placeholders, and the agent writes only the Agentic PR Summary below it (one-line TLDR, summary, implementation bullets, warnings, optional Mermaid diagram, collapsible examples and screenshots). The agent never signs the CLA. Also covers the short watch window for review-bot comments and CI. Use when the user asks to open, create, or raise a PR, to write or rewrite a PR description, or to update a PR after a push.
日本語の概要は準備中です。原文の説明を表示しています。
Find and fix the docs and agent guidance that a branch makes stale - agent skills and their reference files, AGENTS.md and .agents/*.md prompts, READMEs, docs/ folders, and code-adjacent docs that name a changed path, command, symbol, env var, setting, endpoint or behaviour. Use before opening a PR, before pushing new commits to an open PR, and when asked to update docs or skills after a change. The open-pr skill runs it every time.
日本語の概要は準備中です。原文の説明を表示しています。
Web2 recon pipeline — subdomain enumeration (subfinder, Chaos API, assetfinder), live host discovery (dnsx, httpx), URL crawling (katana, waybackurls, gau), directory fuzzing (ffuf), JS analysis (LinkFinder, SecretFinder), continuous monitoring (new subdomain alerts, JS change detection, GitHub commit watch). Use when starting recon on any web2 target or when asked about asset discovery, subdomain enum, or attack surface mapping.
日本語の概要は準備中です。原文の説明を表示しています。
Review or de-slop concrete changes in ccch1mneyyy/dsh-TUI at maintainer level: PR numbers or URLs, branches, commit ranges, patch files, staged or unstaged worktrees, and scoped repository-hygiene requests. Use for evidence-first correctness, contract, repository-rule, process, and behavior-preserving cleanup review, including debug residue, dead or duplicate code, speculative abstractions, stale comments or tests, and unrelated diff churn. Do not use for abstract designs with no concrete repository artifact; use audit for repository-wide assessments and vuln-check for security-only checks.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to inspect automated test runs, list failed or flaky tests, debug a failing testcase with historical context, or filter runs by branch, commit, author, environment, browser, status, or tags. Includes list_testruns, get_run_details, list_testcase, get_testcase_details, and debug_testcase.
日本語の概要は準備中です。原文の説明を表示しています。
Deep analysis of Git history: identify frequently changed hotspot files, analyze code ownership by contributor, and scan for leaked secrets. Triggered when users ask about Git analysis, code hotspots, who owns what code, secret scanning, security audits of commit history, or optimizing code review assignments.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a PR, branch, commit, or git diff into an interactive visual recap with diagrams, file maps, API/schema summaries, annotated diffs, and focused review notes.
日本語の概要は準備中です。原文の説明を表示しています。
Use when starting any task the organization may already have an approved skill, prompt, MCP server, or Agent for: reviewing code, a commit, a diff, or a pull request; writing tests or documentation; querying a database, API, or service; automating a browser or web page; running untrusted code; connecting to a SaaS tool; drafting, researching, or any other substantive work. The user will not mention Observal: the task type is the trigger. Check what is already installed, then run observal discover search as the first action, before reading the repository or working from scratch. Also use when the user wants to log in, configure Observal, inspect local harness setup, share or open a repository Agent share, manage a teamspace or invitation, process inbox items, check installed registry items, or call an endpoint without a dedicated command.
日本語の概要は準備中です。原文の説明を表示しています。
Check, turn off, or troubleshoot bb cloud, the hosted service that writes thread titles and commit messages and transcribes voice input for signed-in bb accounts.
日本語の概要は準備中です。原文の説明を表示しています。
Repository conventions for commits, pull requests, and tests in this example project.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a nontrivial change needs end-to-end verification before committing or shipping
日本語の概要は準備中です。原文の説明を表示しています。
Interrogate a plan, decision, or design one question at a time until it holds — use to stress-test your own thinking before committing to it
日本語の概要は準備中です。原文の説明を表示しています。