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

redbar-init

스타6

포크0

업데이트2026년 7월 13일 22:52

Set a project up so redbar can inspect it. Detects the language and the test runner it actually uses, then proposes the test libraries that are missing (unit, integration, e2e) and prints the exact install command. It NEVER installs anything and never edits a manifest — the human approves and runs the command. Use when redbar reports no coverage report, when a project has no test setup, or when asked how to start testing a repo.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

emersonjds

emersonjds/redbar

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

다운로드

Manus에서 실행

User Input

$ARGUMENTS

Optional. A repo path.

The one rule

Never install a dependency. Never edit package.json, pom.xml, Cargo.toml, composer.json, or any other manifest.

Not "ask first, then install". Not "install if it seems safe". Print the command and stop. Editing someone's manifest unasked is a rejected PR at best and a supply-chain incident at worst. The human presses enter, or does not.

This holds even if the human seems to want you to move fast. Print the command.

Outline

Run init from the project root:
```
npx redbar init $ARGUMENTS
```
Fall back to npx tsx src/cli.ts init $ARGUMENTS if redbar is not on PATH.
Report what it proposes, exactly:
- which language and runner it detected (and how — which manifest file gave it away)
- which test libraries are missing, grouped by layer (unit / integration / e2e)
- the exact install command, verbatim, in a copyable block
- the coverage command to run afterwards
Stop there. Do not run the install. Do not run the coverage command either — it can be slow, and it is the human's call.
If the human explicitly says "go ahead, install it", you may run the install command exactly as printed — no extra packages, no version bumps, no "while I'm here" additions.

What to say about the libraries

The libraries redbar proposes are the standard ones for that ecosystem, not exotic picks. If the human asks why a given library:

The unit libs are the runner the project already uses, plus its coverage reporter — redbar needs the coverage report to exist at all.
The integration libs are the ones the library's own docs point at (Testcontainers for Spring, httpx for Python, supertest for Node).
The e2e lib is Playwright, in every ecosystem that has a binding.

If the project already has a different but equivalent library, say so and leave it alone. The goal is a coverage report redbar can read, not a specific dependency list.

이 저장소의 다른 Skills

같은 저장소

redbar-fix

emersonjds/redbar

Write the missing tests for the gaps redbar found, following the canonical standard for that layer (Playwright's best practices for e2e, Vitest/Jest idiom for unit, Testcontainers for integration). Reads `.redbar/gaps.json`, writes one test file per gap, RUNS each test it wrote, and never leaves a failing test behind — a test that fails twice is marked needs-human and deleted. Use after /redbar.inspect, or when asked to write the missing tests, cover a gap, or fix coverage.

2026-07-136

redbar-inspect

emersonjds/redbar

Find the test-coverage gaps in what changed on this branch. Runs the redbar engine, which crosses the project's coverage report with `git diff` and ranks the untested symbols by criticality. It calls no model to produce the number — the number comes from the coverage report and git. Use before opening a PR, when asked "what should I test?", or when asked what the branch left untested. It writes `.redbar/gaps.json` and reports what came back.

2026-07-136

name	redbar.init
description	Set a project up so redbar can inspect it. Detects the language and the test runner it actually uses, then proposes the test libraries that are missing (unit, integration, e2e) and prints the exact install command. It NEVER installs anything and never edits a manifest — the human approves and runs the command. Use when redbar reports no coverage report, when a project has no test setup, or when asked how to start testing a repo.
argument-hint	Optional repo path (defaults to the current project)
user-invocable	true

User Input

$ARGUMENTS

Optional. A repo path.

The one rule

Never install a dependency. Never edit package.json, pom.xml, Cargo.toml, composer.json, or any other manifest.

This holds even if the human seems to want you to move fast. Print the command.

Outline

Run init from the project root:
```
npx redbar init $ARGUMENTS
```
Fall back to npx tsx src/cli.ts init $ARGUMENTS if redbar is not on PATH.
Report what it proposes, exactly:
- which language and runner it detected (and how — which manifest file gave it away)
- which test libraries are missing, grouped by layer (unit / integration / e2e)
- the exact install command, verbatim, in a copyable block
- the coverage command to run afterwards
Stop there. Do not run the install. Do not run the coverage command either — it can be slow, and it is the human's call.
If the human explicitly says "go ahead, install it", you may run the install command exactly as printed — no extra packages, no version bumps, no "while I'm here" additions.

What to say about the libraries

The libraries redbar proposes are the standard ones for that ecosystem, not exotic picks. If the human asks why a given library:

The unit libs are the runner the project already uses, plus its coverage reporter — redbar needs the coverage report to exist at all.
The integration libs are the ones the library's own docs point at (Testcontainers for Spring, httpx for Python, supertest for Node).
The e2e lib is Playwright, in every ecosystem that has a binding.

If the project already has a different but equivalent library, say so and leave it alone. The goal is a coverage report redbar can read, not a specific dependency list.