스킬 mirrord-db-branching

📦

mirrord-db-branching

Name: mirrord-db-branching
Author: metalbear-co

v2.7 콘텐츠 리비전 r1 높은 위험 🔑 환경 변수⚙️ 외부 명령어🌐 네트워크 접근📁 파일 시스템 접근

Configure Isolated Database Branches with mirrord

Shared databases make migration testing and development experiments difficult to isolate. This skill helps configure mirrord branches with separate connections, controlled data copying, and validation guidance.

지원: Claude Codex Code(CC)

⚠️ 38 나쁨

Maintain this Skill? Claim it ⚠️ 38 나쁨

설치 전에 중지하고 확인을 요청하세요.

계획을 검토하고 파일을 변경하기 전에 사용자의 명시적 동의를 받으세요.

내 에이전트로 설치

이 요청을 에이전트에 복사하세요. 공식 Skill 페이지와 매니페스트가 포함되어 있습니다.

에이전트 요청

Review the Skillstore skill "mirrord-db-branching" from https://skillstore.io/skills/metalbear-co-mirrord-db-branching.md and its manifest at https://skillstore.io/api/skills/metalbear-co-mirrord-db-branching/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

에이전트는 계속해서 계획을 표시하고 보안 정책에서 요구하는 확인을 요청해야 합니다.

에이전트가 읽기 쉬운 리소스

AI 에이전트, 크롤러, 스크립트가 전체 페이지 대신 정리된 컨텍스트만 필요할 때 이 링크를 사용하세요.

Markdown 상세 GET /skills/metalbear-co-mirrord-db-branching.md 서명된 manifest GET /api/skills/metalbear-co-mirrord-db-branching/manifest 서명된 lockfile GET /api/skills/metalbear-co-mirrord-db-branching/lockfile

테스트해 보기

"mirrord-db-branching" 사용 중입니다. Set up an empty PostgreSQL branch using DATABASE_URL.

예상 결과:

The proposed configuration nests database branches under feature and selects PostgreSQL.
The connection references DATABASE_URL by name, without including its value.
The branch starts empty; validate the configuration with mirrord before starting a session.

"mirrord-db-branching" 사용 중입니다. Why does Flyway reject my schema-only branch?

예상 결과:

Schema-only copying transfers table definitions but not migration history rows.
Include the Flyway history table in the selected table copies, or start empty and apply migrations from scratch.

"mirrord-db-branching" 사용 중입니다. Branch an S3 bucket and copy only fixtures.

예상 결과:

Use the bucket environment variable as the source and select an object pattern anchored to the fixtures prefix.
The operator creates the branch bucket in your AWS account; no database pod is created.
Review copied security settings, scoped IAM permissions, and provider charges before starting.

보안 감사

높은 위험

v1 • 2026. 9. 29. 버전별 보고서 열기

All 400 presented static matches are false positives involving documentation, configuration references, or Kubernetes variable expansion. Two semantic risks remain: credential-bearing diagnostic output and a predictable administrator password in a generic branch example. The analyzer reports 59 additional matches outside this catalog; they still require manual review before automatic publication. Static review was capped at 400/459 representative findings; omitted static matches are unconfirmed, so automatic publishing stays disabled until manual review.

스캔된 파일

3,619

분석된 줄 수

검토 항목

오탐 무시됨

확인된 보안 우려 사항 (2)

높음

references/troubleshooting.md:74-78

Troubleshooting Can Expose Database Credentials

The troubleshooting command runs `env | grep -iE 'database|postgres|mysql|redis|mongo'` through mirrord, printing matching values rather than names. Database URLs can contain credentials, which may enter terminal logs or an agent transcript without redaction.

The command directly prints matching environment entries without removing their values. Exposure depends on the target environment, but no output redaction is shown.

중간

references/db-branches-schema.json:362

Predictable Administrator Password in Branch Example

The generic InfluxDB example sets DOCKER_INFLUXDB_INIT_USERNAME to admin and DOCKER_INFLUXDB_INIT_PASSWORD to mirrord-branch. Reusing this example creates a predictable administrator credential, allowing unauthorized access wherever the branch service is reachable.

The schema description explicitly supplies a fixed administrator username and password in an executable configuration example. Exploitability depends on network reachability and example reuse.

위험 요인

🔑 환경 변수 (31)

⚙️ 외부 명령어 (50)

🌐 네트워크 접근 (16)

references/db-branches-schema.json:2 references/db-branches-schema.json:4 references/db-branches-schema.json:203 references/db-branches-schema.json:2435 SKILL.md:35 SKILL.md:36 SKILL.md:37 SKILL.md:38 SKILL.md:39 SKILL.md:40 SKILL.md:50 SKILL.md:187 SKILL.md:230 SKILL.md:363 SKILL.md:502 SKILL.md:507

📁 파일 시스템 접근 (3)

references/db-branches-schema.json:2234 SKILL.md:118 SKILL.md:231

감사자: codex

이 보고서 공유 및 인용

버전이 지정된 평가 보고서, 중립 배지, 임베드 카드 및 인용을 공유하세요. Skillstore는 근거를 보고하지만 이 Skill의 안전 여부를 판단하지 않습니다.

버전별 보고서 열기

보고서 링크 복사

https://skillstore.io/skills/metalbear-co-mirrord-db-branching/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown 배지

[![Skillstore security assessment](https://skillstore.io/badges/skills/metalbear-co-mirrord-db-branching/security.svg)](https://skillstore.io/skills/metalbear-co-mirrord-db-branching?utm_source=security_passport_badge)

HTML 배지

<a href="https://skillstore.io/skills/metalbear-co-mirrord-db-branching?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/metalbear-co-mirrord-db-branching/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

임베드 카드

<iframe src="https://skillstore.io/embed/skills/metalbear-co-mirrord-db-branching.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

학술 인용 (APA · BibTeX · CFF)

APA 인용

metalbear-co. (2026). mirrord-db-branching security audit report (audit version 1) [Author version 2.7]. Skillstore. https://skillstore.io/skills/metalbear-co-mirrord-db-branching/audits/1

BibTeX 인용

@techreport{metalbear-co-metalbear-co-mirrord-db-branching-2026,
  author = {metalbear-co},
  title = {mirrord-db-branching security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/metalbear-co-mirrord-db-branching/audits/1},
  note = {Author version 2.7}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "mirrord-db-branching security audit report (audit version 1)"
version: "2.7"
type: report
authors:
  - name: "metalbear-co"
date-released: "2026-09-29"
url: "https://skillstore.io/skills/metalbear-co-mirrord-db-branching/audits/1"
identifiers:
  - type: other
    value: "skillstore:metalbear-co-mirrord-db-branching:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore 점수

이 점수의 이유 증거 신뢰도: 중간

아키텍처

유지보수성

콘텐츠

커뮤니티

사양 준수

만들 수 있는 것

Test Application Migrations

Prepare a PostgreSQL or MySQL branch with the required schema and migration history before testing application changes.

Build Focused Test Datasets

Configure engine-specific filters to copy approved records into temporary branches for integration tests.

Standardize Branch Configuration

Review engine prerequisites, IAM sources, generic image policies, and storage settings for shared development clusters.

이 프롬프트를 사용해 보세요

Create an Empty PostgreSQL Branch

Generate a minimal PostgreSQL 16 branch configuration using DATABASE_URL as the variable name. Start empty and explain the prerequisites and validation command.

Copy Selected Test Records

Configure a PostgreSQL schema branch for app_db using DATABASE_URL. Copy users only where email ends with @test.com, and explain compatible copy modes.

Prepare Branch Migrations with IAM

Configure PostgreSQL branching for AWS RDS IAM with Flyway migrations from ./migrations. Preserve migration history when copying schema and reference credentials without displaying values.

Review a Generic Branch Design

Review my generic branch configuration against the bundled schema. Check approved images, copy Job readiness, secret-backed parameters, unique branch IDs, and version compatibility. Propose changes without executing workloads.

모범 사례

Confirm engine versions and connection variable names, then validate every generated configuration with mirrord verify-config.
Use secret references and approved images; keep credential values out of prompts, configurations, and diagnostic output.
Prefer empty or narrowly filtered copies, unique branch IDs, and limited lifetimes for authorized test data.

피하기

Copying full production datasets when schema or approved test records would suffice.
Assuming SQL table filters still apply when the copy mode is all.
Reusing sample administrator passwords or printing remote environment values during troubleshooting.

자주 묻는 질문

Which AI tools can use this skill?

The marketplace lists support for Claude, Codex, and Claude Code. Runtime validation and branch operations still require the appropriate local tools and cluster access.

Does remote branching require a paid mirrord feature?

Yes. Remote database branching requires a Team or Enterprise operator license, compatible versions, and the relevant engine feature enabled.

Which databases and services are covered?

Coverage includes MySQL, MariaDB, PostgreSQL, MSSQL, MongoDB, Redis, DynamoDB, ClickHouse, Google Spanner, Amazon S3, and generic container services.

Should I give the assistant my database password?

No. Provide variable names or secret references, not credential values. Avoid diagnostic commands that print complete connection strings.

Can I copy only selected records?

Yes, using engine-specific filters. SQL table filters require empty or schema mode; MongoDB, DynamoDB, Redis, and S3 use different filtering options.

How are branches reused and removed?

Remote branches can be reused by ID until their idle lifetime expires. The default lifetime is five minutes, capped at fifteen. Explicit removal commands are documented.