원클릭으로 Manus에서 모든 스킬 실행

$pwd:

reproduce-bug-report-local

Name: Reproduce Bug Report Local
Author: warpdotdev

// Repo-specific bug reproduction guidance for Warp. Specializes the core reproduce-bug-report skill for logged-out Warp UI repros, exact reporter-version installs, and login-free onboarding.

Manus에서 실행

$ git log --oneline --stat

stars:59,731

forks:4,713

updated:2026년 5월 20일 21:00

SKILL.md

readonly

name	reproduce-bug-report-local
specializes	reproduce-bug-report
description	Repo-specific bug reproduction guidance for Warp. Specializes the core reproduce-bug-report skill for logged-out Warp UI repros, exact reporter-version installs, and login-free onboarding.

Repo-specific bug reproduction guidance for `warp`

This file is a companion to the core reproduce-bug-report skill. It does not redefine the shared Oz computer-use orchestration, artifact handling, safety rules, or reporting format. It specializes scope and setup for Warp bug reports.

Scope

Use this workflow only for Warp bugs that can be exercised while the app remains logged out.
Apply it to UI-visible Warp bugs, interaction bugs, rendering/layout bugs, logged-out onboarding bugs, settings bugs, editor/display bugs, terminal-display bugs, and other visual or interactive issues where screenshots or recordings would help.
Do not use it for authenticated-user flows, account-specific state, cloud-synced state, logged-in onboarding, or AI behaviors that require login.
If a report requires authentication, account state, cloud sync, or another logged-in-only capability, do not launch a repro agent with this local specialization; report that it is out of scope for the current logged-out Warp workflow.

Warp version and install strategy

Prefer reproducing against the exact Warp version/build and channel reported by the user.
Do not build Warp from source by default. Install the matching Linux package or binary release for the reporter's version/channel instead.
If the bug report names a macOS or Windows build, use the corresponding Linux build from the same version/channel when a matching Linux artifact exists, and state that this is a Linux proxy for the reporter's platform.
Use the repository's or Warp release tooling/docs available in the environment to find and install the exact versioned Linux artifact. Do not silently substitute the latest stable build when an exact matching version can be installed.
If the exact version/build cannot be found or installed, report that clearly, explain what was attempted, and use the closest justified fallback only when it is useful for continuing the investigation.
Record the requested reporter Warp version, the installed Linux version, the source of the installed artifact, and any fallback decision in the manifest and final report.

Logged-out Warp baseline

Keep Warp logged out for the entire repro attempt. Do not create an account, sign in, paste auth tokens, or use real user credentials.
Launch Warp and complete the login-free / continue-without-account onboarding path until a normal logged-out terminal session is usable.
Capture a post-onboarding baseline screenshot before attempting the bug-specific reproduction.
If the assigned bug cannot be exercised after entering a normal logged-out Warp session, stop and report the blocker instead of improvising an authenticated flow.

Local prompt additions

When applying the core skill to Warp, ensure the parent prompt and child prompts include:

Reporter Warp version/build/channel: the exact value from the report, or unknown.
Build/app target: the exact versioned Linux Warp package/binary to install, or the justified fallback if an exact artifact is unavailable.
Assigned Warp state: first-run logged-out state, completed logged-out onboarding, terminal/session/layout/settings state, or the targeted code-path hypothesis.
A reminder that Warp must remain logged out and that logged-in-only reports are blocked for this specialization.

Local reproduction priorities

Match the reporter's Warp version/build/channel before broadening the search space.
Follow the issue's exact steps first, then test at most two targeted variations supported by the issue or by a code-path hypothesis.
Prefer targeted hypotheses derived from Warp UI strings, settings names, feature names, telemetry names, route names, and relevant components over broad exploratory clicking.
In the final report, include:
- the reporter-requested Warp version/build/channel
- the installed Linux Warp version/build/channel
- the package or binary source
- whether a fallback was used
- whether the test was a Linux proxy for a macOS or Windows report

related-skills.json

같은 저장소

changelog-draft.md

from "warpdotdev/warp"

Generate a reviewable changelog draft from PRs merged in a release range. Extracts explicit CHANGELOG markers, classifies unmarked PRs, adds external contributor attribution, and outputs markdown + JSON artifacts. Does NOT mutate channel_versions.json.

2026-05-2159.7k

onboarding-verification-skill.md

from "warpdotdev/warp"

Launch two parallel Oz cloud agents with computer use to download and install the latest stable Linux Warp build, capture screenshots while walking through first-time onboarding in both logged-out and logged-in states, then selectively fan out follow-up cloud agents for distinct onboarding branches proposed by those initial explorers. Use this whenever the user asks to test, document, screenshot, or walk through the Warp first-time install/onboarding experience in a cloud Linux environment.

2026-05-2059.7k

feedback.md

from "warpdotdev/warp"

Turn rough feedback about the Warp app into a filed GitHub issue or duplicate-issue response for `warpdotdev/warp`. Use ONLY when the user explicitly wants to report a problem with the Warp terminal/IDE/app itself—not when they're working on their own code, managing their own GitHub repos, or doing general software development tasks. SKIP when: the user is creating/managing GitHub issues or PRs for their own projects, reviewing PRs, diagnosing CI failures, using `gh` CLI for repo management, or performing any GitHub workflow not specifically about reporting a problem with the Warp application itself.

2026-05-1959.7k

review-pr-local.md

from "warpdotdev/warp"

Repo-specific review guidance for warp. Only the categories declared overridable by the core review-pr skill may be specialized here.

2026-05-1359.7k

classify-changelog-pr.md

from "warpdotdev/warp"

Reference guidance for classifying whether an unmarked PR should appear in the changelog and under which category. Used inline by the changelog-draft skill — not dispatched as a separate agent.

2026-05-1359.7k

create-launch-modal.md

from "warpdotdev/warp"

Create a one-time launch modal in the Warp client (feature announcement, onboarding, etc.). Use when adding a new modal that should appear exactly once per user on startup, gated by a feature flag, with colors sourced from Warp theme tokens and terminal theme colors.

2026-05-1159.7k

package.json

"author": "warpdotdev"

"repository": "warpdotdev/warp"

GitHub 저장소 열기 Creator 저장소 보기

$ install --global

$ download --local

Manus에서 실행

$ useful --forSOC

소프트웨어 품질 보증 분석가·테스터컴퓨터 및 수학직15-1253L4

Repo-specific bug reproduction guidance for warp

Scope

Use this workflow only for Warp bugs that can be exercised while the app remains logged out.

Apply it to UI-visible Warp bugs, interaction bugs, rendering/layout bugs, logged-out onboarding bugs, settings bugs, editor/display bugs, terminal-display bugs, and other visual or interactive issues where screenshots or recordings would help.

Do not use it for authenticated-user flows, account-specific state, cloud-synced state, logged-in onboarding, or AI behaviors that require login.

If a report requires authentication, account state, cloud sync, or another logged-in-only capability, do not launch a repro agent with this local specialization; report that it is out of scope for the current logged-out Warp workflow.

Warp version and install strategy

Prefer reproducing against the exact Warp version/build and channel reported by the user.

Do not build Warp from source by default. Install the matching Linux package or binary release for the reporter's version/channel instead.

If the bug report names a macOS or Windows build, use the corresponding Linux build from the same version/channel when a matching Linux artifact exists, and state that this is a Linux proxy for the reporter's platform.

Use the repository's or Warp release tooling/docs available in the environment to find and install the exact versioned Linux artifact. Do not silently substitute the latest stable build when an exact matching version can be installed.

If the exact version/build cannot be found or installed, report that clearly, explain what was attempted, and use the closest justified fallback only when it is useful for continuing the investigation.

Record the requested reporter Warp version, the installed Linux version, the source of the installed artifact, and any fallback decision in the manifest and final report.

Logged-out Warp baseline

Keep Warp logged out for the entire repro attempt. Do not create an account, sign in, paste auth tokens, or use real user credentials.

Launch Warp and complete the login-free / continue-without-account onboarding path until a normal logged-out terminal session is usable.

Capture a post-onboarding baseline screenshot before attempting the bug-specific reproduction.

If the assigned bug cannot be exercised after entering a normal logged-out Warp session, stop and report the blocker instead of improvising an authenticated flow.

Local prompt additions

When applying the core skill to Warp, ensure the parent prompt and child prompts include:

Reporter Warp version/build/channel: the exact value from the report, or unknown.

Build/app target: the exact versioned Linux Warp package/binary to install, or the justified fallback if an exact artifact is unavailable.

Assigned Warp state: first-run logged-out state, completed logged-out onboarding, terminal/session/layout/settings state, or the targeted code-path hypothesis.

A reminder that Warp must remain logged out and that logged-in-only reports are blocked for this specialization.

Local reproduction priorities

Match the reporter's Warp version/build/channel before broadening the search space.

Follow the issue's exact steps first, then test at most two targeted variations supported by the issue or by a code-path hypothesis.

Prefer targeted hypotheses derived from Warp UI strings, settings names, feature names, telemetry names, route names, and relevant components over broad exploratory clicking.

In the final report, include:

the reporter-requested Warp version/build/channel
the installed Linux Warp version/build/channel
the package or binary source
whether a fallback was used
whether the test was a Linux proxy for a macOS or Windows report

reproduce-bug-report-local

Repo-specific bug reproduction guidance for warp

Scope

Warp version and install strategy

Logged-out Warp baseline

Local prompt additions

Local reproduction priorities

이 저장소의 다른 Skills

이 저장소의 다른 Skills

Repo-specific bug reproduction guidance for warp

Scope

Warp version and install strategy

Logged-out Warp baseline

Local prompt additions

Local reproduction priorities

Repo-specific bug reproduction guidance for `warp`

Repo-specific bug reproduction guidance for `warp`