“diff”的搜索结果

An advanced agent for de novo antibody design and optimization using state-of-the-art protein language models (MAGE, RFdiffusion).

中文简介正在准备中。当前显示原文说明。

Perform a read-only, defect-first review of a specified code change and return every actionable finding. Use when another agent delegates review of uncommitted changes, a base-branch diff, a commit, or custom review instructions.

中文简介正在准备中。当前显示原文说明。

MANDATORY prerequisite — load this skill BEFORE every `generate_diagram` tool call. NEVER call `generate_diagram` directly without loading this skill first. Trigger whenever the user asks to create, generate, draw, render, sketch, or build a diagram — flowchart, architecture diagram, sequence diagram, ERD or entity-relationship diagram, state diagram or state machine, gantt chart, or timeline. Also trigger when the user mentions Mermaid syntax or wants a system architecture, decision tree, dependency graph, API call flow, auth handshake, schema, or pipeline visualized in FigJam. Routes to type-specific guidance, sets universal Mermaid constraints, and tells you when to use a different diagram type or skip the tool entirely (mindmaps, pie charts, class diagrams, etc.).

中文简介正在准备中。当前显示原文说明。

Expert en génération d'images ComfyUI (workflows, nodes, models, inpainting, upscaling)

中文简介正在准备中。当前显示原文说明。

Use taste as a competitive moat and business advantage. In the AI and vibe-coding era, execution is commoditized. Taste is the defensible edge. Use when advising founders on product differentiation, building product culture, evaluating why some products win despite fewer features, or understanding taste as a strategic asset.

中文简介正在准备中。当前显示原文说明。

Tell the difference between design decisions that age well and decisions that follow the crowd. Use when evaluating whether a design choice is principled or fashionable, or when a client asks to 'make it look modern.'

中文简介正在准备中。当前显示原文说明。

List all pb-* playbooks with duration, difficulty and requirements, and start one. Generated from plugin-commands.json; invoke as $bdb-aos:playbooks.

中文简介正在准备中。当前显示原文说明。

Turn a GitHub issue into a tested fix on a branch with an open PR: read the issue as the contract, find the root cause, write the failing test first, fix, prove it, review the diff against the issue, push and open the PR only after GO. Merging stays with pb-ship. Use for "fix issue 42", "bug fix from this issue", "turn this issue into a PR".

中文简介正在准备中。当前显示原文说明。

Run a security sweep over one repo: secrets, dependencies and the diff, a security review and a silent-failure hunt, one deduped and ranked findings report, issues filed for blocking findings only after GO, each one handed to pb-bug-fix. Use for "security sweep", "audit this repo", "check for leaked secrets and vulnerable deps".

中文简介正在准备中。当前显示原文说明。

Check invoices and receipts line by line against your offers and list what matches, what differs and what has no offer. Nothing is paid or sent. Use for "check my invoices", "match invoices to offers", "does this invoice match the quote".

中文简介正在准备中。当前显示原文说明。

Review a diff for clarity and safe simplifications, then optionally apply low-risk fixes.

中文简介正在准备中。当前显示原文说明。

Comprehensive security auditing, diff analysis, defensive checklists, and vulnerability testing.

中文简介正在准备中。当前显示原文说明。

Use when `aos-plan-canvas await` returns an item with route "visual-edit", or the human points at an element in a running local dev app and wants the source edited. Finds the source with a deterministic search, posts a diff plan in the canvas, and edits one file only after a yes given in the canvas. Not for remote or production sites.

中文简介正在准备中。当前显示原文说明。

Use when facing 2+ independent tasks — "in parallel", "independent tasks", "multiple unrelated failures", "different test files or subsystems" — that can be worked on without shared state or sequential dependencies. Dispatch one agent per independent slice, each with only the context it needs, even when the user did not ask for subagents explicitly.

中文简介正在准备中。当前显示原文说明。

Browser automation powers web testing, scraping, and AI agent interactions. The difference between a flaky script and a reliable system comes down to understanding selectors, waiting strategies, and anti-detection patterns.

中文简介正在准备中。当前显示原文说明。

Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessary. This skill covers tool design from schema to error handling.

中文简介正在准备中。当前显示原文说明。

Document-code change notification system: traceable doc-code binding via git tree hash, git-diff-driven reconciliation plans with confidence/risk metadata, and idempotent execution. Use when maintaining documentation freshness, detecting stale docs, or binding docs to source code.

中文简介正在准备中。当前显示原文说明。

Liquid Glass material best practices for SwiftUI, UIKit, and AppKit on iOS 26+/macOS 26+ (Tahoe) through iOS 27/macOS 27. Use when implementing, reviewing, or migrating to glass: glassEffect, Glass variants (.regular/.clear/.identity), tint, interactive(), GlassEffectContainer, glassEffectUnion, toolbar glass, ToolbarSpacer, scrollEdgeEffectStyle, sharedBackgroundVisibility, tabBarMinimizeBehavior, backgroundExtensionEffect, NSGlassEffectView, UIGlassEffect, Tahoe window chrome, glass accessibility (Reduce Transparency/Increase Contrast), pre-26 Material fallbacks, UIDesignRequiresCompatibility. Also fires on symptoms: glass renders dark or muddy, glass looks like a flat tinted rectangle, glass button doesn't register taps, tap passes through glass, "'glassEffect' is only available in iOS 26.0 or newer", "ambiguous use of 'opacity'", "'cornerRadius' was deprecated", glass looks different in simulator vs device, screenshots of glass UI don't match. For glass animation, morphing, glassEffectID, transitions, Metal shaders, or performance profiling use the liquid-glass-motion skill instead.

中文简介正在准备中。当前显示原文说明。

A skill for AI agents that want to produce better daily reports and discover more of what their users actually want. Scans source front pages, diffs them against yesterday, prescreens with a weighted profile, reviews with an LLM, deduplicates, publishes, and evolves the profile from user feedback. All decisions go to an append-only tape for audit and replay.

中文简介正在准备中。当前显示原文说明。

Pixel-based motion and UI change analysis from frame sequences or screenshots using computer vision and visual comparison. Use when `.transition` or visual effects are not observable via MotionEyes logs, when you only have screenshots/video, when you need regression diffs across builds, or when you need to summarize on-screen changes without instrumentation. Do not use when MotionEyes traces are available and you need precise timing/values; use `motioneyes-animation-debug` instead.

中文简介正在准备中。当前显示原文说明。

When the user wants to discover, evaluate, or prioritize App Store keywords. Also use when the user mentions "keyword research", "find keywords", "search volume", "keyword difficulty", "keyword ideas", or "what keywords should I target". For implementing keywords into metadata, see metadata-optimization. For auditing current keyword performance, see aso-audit.

中文简介正在准备中。当前显示原文说明。

Implement, review, or improve localization and internationalization in iOS/macOS apps — String Catalogs (.xcstrings), LocalizedStringKey, LocalizedStringResource, pluralization, FormatStyle for numbers/dates/measurements, right-to-left layout, Dynamic Type, and locale-aware formatting. Use when adding multi-language support, setting up String Catalogs, handling plural forms, formatting dates/numbers/currencies for different locales, testing localizations, or making UI work correctly in RTL languages like Arabic and Hebrew.

中文简介正在准备中。当前显示原文说明。

Review a git diff or explicit file scope for reuse, code quality, efficiency, clarity, and standards issues, then optionally apply safe Codex-driven fixes. Use when the user asks to "simplify code", "review changed code", "check for code reuse", "review code quality", "review efficiency", "simplify changes", "clean up code", "refactor changes", or "run simplify".

中文简介正在准备中。当前显示原文说明。

Structured 3-phase peer review of a diff or PR — intent, issues by severity, then pointed merge-readiness questions and a verdict. Use for general code review. Not for AI workflow self-fix-and-edit (ai-systems-review) or no-edit devil's-advocate threat models (adversarial-challenge). Phase 3 asks questions only; it is not the adversarial-challenge skill.

中文简介正在准备中。当前显示原文说明。