スキル 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.