「repository」の検索結果

Evaluate proposed repository harness changes with pinned Darwin tools and explicit evidence limits.

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

Extract a design system from a screenshot (PNG/JPG/WEBP) or a live URL and produce a schema-compliant `design.v1.json` file plus a ready-to-use agent prompt for applying the design to any website/app. When run inside the sleek-ui repository, offers to add the extracted design to the public catalog as a PR — updating `public/designs/`, `src/data/designs/`, `src/data/designs.ts`, and generating a preview. Use when users ask to "extract a design from this screenshot", "clone this site's design", "reverse-engineer the design tokens", "reskin my app to look like {site}", "generate a sleek-ui design from this URL", or provide an image/URL and want a reusable design system.

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

Analyzes a repository and any existing test suite, grades existing tests for weakness, classifies mocks, emits a phased roadmap for building a test suite that catches real regressions, then executes those phases one at a time. Use when planning or building a test suite, assessing whether existing tests are worth anything, adding tests to a legacy codebase, or when the user mentions test coverage, test strategy, or weak tests. Not for reviewing a branch for bugs, and not for fixing the bugs it logs.

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

Transform a project into a professional open-source repository by adding LICENSE, README, CONTRIBUTING, CODE_OF_CONDUCT, SECURITY, and GitHub issue/PR templates. Don't use for documentation overhauls, landing-page generation, or registry publishing.

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

Multi-repository coordination, synchronization, and architecture management with AI swarm orchestration

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

Advanced GitHub Actions workflow automation with AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management

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

Suede Labs agent-team orchestrator: split complex work into coordinated lanes with explicit file ownership, WIP collision detection, quality gates, escalation thresholds, rollback plans, and handoffs that prove what shipped. Use when one shared change needs safe parallel ownership across builders and reviewers, when a lane map must be resolved before anyone opens a file, or when running a repeatable public-repository contribution program with issue scoring, atomic task leases, isolated worktrees, and explicit publication authority. NOT FOR: one repo change a bundled DAG can run end to end (use suede-graph-flo-xr); findings-only review of a diff (use suede-code-review) or an A-F ship grade (use suede-code-grader); CI, branch protection, or merge-gate wiring (use suede-ci-gate); branch and worktree setup on a stale mirror (a private Suede Labs companion, not in this pack).

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

Inspect repository session replay and verify configured MetaHarness field memory boundaries before reusing outcomes.

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

Evaluate proposed repository harness changes with pinned Darwin tools and explicit evidence limits.

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

Search an index of public repositories, GitHub issues, merged pull requests, repository READMEs, and curated documentation sites. Use when a programming question needs external documentation or upstream evidence.

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

Repository quality gates for Rust and generated artifacts. Use when validating changes locally or before committing Rust, schema, or documentation updates.

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

Drive a pull request on this repository to green — which fast checks to run before pushing, how to read a red check, and what to do about a review comment. Use when a CI failure, a review comment, a merge conflict, or a scheduled check-in arrives on a PR you opened or were asked to drive.

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

Capture the before/after rendered PNGs a UI-affecting PR in this repository needs as visual evidence, including bringing an Android SDK up in a fresh sandbox. Use when a change touches a Compose @Preview, a catalog, the VS Code webview, an overlay, a theme, an icon or a fixture, and the PR body needs real pixels.

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

Neo4j Java Driver v6 — driver lifecycle, Maven/Gradle setup, executableQuery, executeRead/Write managed transactions, explicit transactions, async/reactive patterns, error handling, data type mapping, connection pool tuning, causal consistency/bookmarks. Use when writing Java or Kotlin code that connects to Neo4j via GraphDatabase.driver, executableQuery, SessionConfig, executeRead, executeWrite, or TransactionCallback. Does NOT handle Cypher authoring — use neo4j-cypher-skill. Does NOT cover driver version upgrades — use neo4j-migration-skill. Does NOT cover Spring Data Neo4j (@Node, Neo4jRepository) — use neo4j-spring-data-skill.

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

Use when the repository is Defold, MonoGame, pygame/pygame-ce, Excalibur or KAPLAY (or melonJS, Stride, Python arcade, macroquad/ggez) - each engine's lifecycle and delta, where logic goes, the test runner, the headless build/run command, and how to capture a frame.

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

Use when a game task could run on more than one engine or the repository has no engine yet - read the repo's engine and pinned version, and only for a brand-new game pick one from platforms, 2D/3D, team language, scale and licensing.

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

Use when an analiz task arrives in done (approved) - turn the approved split into implementation tasks with repository, AC, derived_from and ordering arguments

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

Use when you start an analiz task - explore every affected repository and resolve unknowns before writing the report

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

Use after the targeted cases pass - choosing the adjacent behaviour this change can break from the PR's files and the component's links, and the per-repository smoke set

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

Wire the automation test project into the repository's own pipeline so every task must pass the suite before it can leave QA

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

Use when you are about to hand off any change to a screen or component on a mobile repository - the size, text-scale and dark-mode matrix, the exact tool calls to see your own build, and the checklist that decides whether the screen is done.

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

Use when the mobile repository has no theme tokens or component library yet (a new app, an "Apply design system" task, or a task that asks for one), before building any screen - writes the approved design system's generated files from get_design_system (files true) and builds the theme from them when there is one.

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

Maintain a dedicated automation test project per repository - separate from the product's unit tests - with API, worker, and UI suites written scenario-first

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

Use when a repository needs CI/CD - author GitHub Actions workflows so TaskTrooper's pipeline auto-detects your validate/build/test jobs and stage/preprod/prod deploys, and so a dispatch delivery profile can dispatch the production deploy

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