staging-db-local-sync

النجوم٦

التفرعات٥

آخر تحديث١٠ يوليو ٢٠٢٦ في ١٣:٢٠

Use when syncing, restoring, documenting, or debugging the 6529 backend local database from staging via scripts/sync-staging-db-local.sh, including AWS SSM tunnel setup, local Docker MySQL restore, restart recovery, and staging DB env configuration.

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

المصدر

6529-Collections

6529-Collections/6529seize-backend

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مديرو الشبكات وأنظمة الحاسوبمهن الحاسوب والرياضيات·SOC 15-1244

SKILL.md

readonly

name	staging-db-local-sync
description	Use when syncing, restoring, documenting, or debugging the 6529 backend local database from staging via scripts/sync-staging-db-local.sh, including AWS SSM tunnel setup, local Docker MySQL restore, restart recovery, and staging DB env configuration.

Staging DB Local Sync

Use this skill when the task involves the staging-to-local database sync script.

First Read

Before changing behavior or giving detailed instructions, read:

scripts/sync-staging-db-local.sh
docs/staging-db-local-sync.md
scripts/AGENTS.md
package.json scripts for db:staging:*

If the user asks about their local env file, inspect only variable names and structure. Do not print secrets.

Safety

Do not run --fresh, restore, or any command that can replace the local database unless the user explicitly confirms.
Treat .env.staging-db.local as trusted local shell config. Do not source unknown files without user approval.
Do not commit local dump files, local env files, AWS credentials, profile names that are personal to one machine, instance IDs copied from private context, or local machine paths.
Keep --restore-only usable without staging credentials and without AWS credentials.

AWS Credentials

The script uses the normal AWS CLI credential chain.

Valid credential sources include:

~/.aws/credentials
AWS_PROFILE
AWS SSO cached credentials
AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY

Do not tell users they must run "aws login" in general. Say aws sso login --profile <profile> only when they use an SSO profile and the SSO cache is expired.

The script only calls AWS when STAGING_SSM_TARGET is set. Without that variable, it expects the configured staging host and port to already be reachable.

Common Commands

Resume or start the normal sync:

npm run db:staging:resume

Archive the old dump and build a new one:

npm run db:staging:fresh

Dump only:

bash scripts/sync-staging-db-local.sh --dump-only

Restore only:

bash scripts/sync-staging-db-local.sh --restore-only --yes

Debugging Checklist

When a run fails, check:

Is .env.staging-db.local present in the repo root?
Is Docker Desktop running, or is AUTO_START_DOCKER=true?
Is the local Docker MySQL service up?
If using SSM, are aws and session-manager-plugin installed?
If using SSM, can AWS CLI resolve valid credentials?
Does .staging-db-dump/current/logs/ssm-tunnel.log show a tunnel error?
Are staging read credentials valid?
Are local MySQL root credentials valid?

Editing Guidance

Preserve resumable dump behavior: atomic temp files, gzip validation, completion markers, and schema drift invalidation.
Validate numeric chunk values and SQL identifiers before interpolation.
Keep local DB passwords out of command-line arguments where practical.
Keep docs aligned when changing flags, env vars, default values, or safety behavior.

Validation

Use focused checks for shell or docs changes:

bash -n scripts/sync-staging-db-local.sh
git diff --check

Use broader repo validation when code paths outside docs or shell parsing change.

المزيد من هذا المستودع

نفس المستودع

deploy-6529

6529-Collections/6529seize-backend

Route and execute 6529 backend, frontend, or coupled staging and production releases through Simple Release Bus v2 by exact PR head SHA, or use the serialized manual fallback only while v2 reports OFF. Use for staging, deploy, promotion, release merge, pause, resume, recovery, or rollout coordination.

2026-07-246

write-prs

6529-Collections/6529seize-backend

Write, open, iterate, and prepare pull requests in the 6529 SEIZE backend for merge or deployment with clear PR descriptions, safe validation notes, review-bot follow-up, DCO-signed commits only when explicitly requested, backend/API checks, lambda deployment planning, and deployment handoff notes. Use when preparing PR bodies, creating PRs, responding to CodeRabbit or Codex review bots, deciding whether a PR is ready, or preparing a backend/API PR for merge, staging, or production rollout; use deploy-6529 for actual deployment execution.

2026-07-236

write-prs

6529-Collections/6529seize-backend

Write, open, iterate, and prepare pull requests in the 6529 SEIZE backend for merge or deployment with clear PR descriptions, safe validation notes, review-bot follow-up, DCO-signed commits only when explicitly requested, backend/API checks, lambda deployment planning, and deployment handoff notes. Use when preparing PR bodies, creating PRs, responding to CodeRabbit or Claude review bots, deciding whether a PR is ready, or preparing a backend/API PR for merge, staging, or production rollout; use deploy-6529 for actual deployment execution.

2026-07-236

api-skill

6529-Collections/6529seize-backend

Build or modify API endpoints in this repository by driving API contracts from src/api-serverless/openapi.yaml, regenerating generated models/routes, implementing thin handlers or legacy manual routes, and wiring validation/auth/timing correctly. Use when creating new API endpoints, changing API request or response models, adding generated x-6529-router operations, or updating API route behavior.

2026-06-186

write-skills

6529-Collections/6529seize-backend

Create, improve, or review Codex/OpenAI Agent Skills and SKILL.md files. Use when writing a new skill, updating an existing skill, designing skill frontmatter and trigger behavior, choosing scripts/references/assets, validating skill structure, or turning repeatable Codex workflows into reusable skills.

2026-06-186

community-metrics

6529-Collections/6529seize-backend

Add or change community metrics in the 6529 SEIZE backend by updating metric rollup enums, recorder methods, recording call sites, optional historical backfills, OpenAPI response models, and community-metrics API aggregation. Use when adding new community metrics, exposing metric summaries or series, tracking community activity, or changing MetricsRecorder/MetricsDb behavior.

2026-06-186

name	staging-db-local-sync
description	Use when syncing, restoring, documenting, or debugging the 6529 backend local database from staging via scripts/sync-staging-db-local.sh, including AWS SSM tunnel setup, local Docker MySQL restore, restart recovery, and staging DB env configuration.

Staging DB Local Sync

Use this skill when the task involves the staging-to-local database sync script.

First Read

Before changing behavior or giving detailed instructions, read:

scripts/sync-staging-db-local.sh
docs/staging-db-local-sync.md
scripts/AGENTS.md
package.json scripts for db:staging:*

If the user asks about their local env file, inspect only variable names and structure. Do not print secrets.

Safety

Do not run --fresh, restore, or any command that can replace the local database unless the user explicitly confirms.
Treat .env.staging-db.local as trusted local shell config. Do not source unknown files without user approval.
Do not commit local dump files, local env files, AWS credentials, profile names that are personal to one machine, instance IDs copied from private context, or local machine paths.
Keep --restore-only usable without staging credentials and without AWS credentials.

AWS Credentials

The script uses the normal AWS CLI credential chain.

Valid credential sources include:

~/.aws/credentials
AWS_PROFILE
AWS SSO cached credentials
AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY

Do not tell users they must run "aws login" in general. Say aws sso login --profile <profile> only when they use an SSO profile and the SSO cache is expired.

The script only calls AWS when STAGING_SSM_TARGET is set. Without that variable, it expects the configured staging host and port to already be reachable.

Common Commands

Resume or start the normal sync:

npm run db:staging:resume

Archive the old dump and build a new one:

npm run db:staging:fresh

Dump only:

bash scripts/sync-staging-db-local.sh --dump-only

Restore only:

bash scripts/sync-staging-db-local.sh --restore-only --yes

Debugging Checklist

When a run fails, check:

Is .env.staging-db.local present in the repo root?
Is Docker Desktop running, or is AUTO_START_DOCKER=true?
Is the local Docker MySQL service up?
If using SSM, are aws and session-manager-plugin installed?
If using SSM, can AWS CLI resolve valid credentials?
Does .staging-db-dump/current/logs/ssm-tunnel.log show a tunnel error?
Are staging read credentials valid?
Are local MySQL root credentials valid?

Editing Guidance

Preserve resumable dump behavior: atomic temp files, gzip validation, completion markers, and schema drift invalidation.
Validate numeric chunk values and SQL identifiers before interpolation.
Keep local DB passwords out of command-line arguments where practical.
Keep docs aligned when changing flags, env vars, default values, or safety behavior.

Validation

Use focused checks for shell or docs changes:

bash -n scripts/sync-staging-db-local.sh
git diff --check

Use broader repo validation when code paths outside docs or shell parsing change.