'backfill' 검색 결과

Use when the user asks to query Volcengine CloudTrail audit logs, investigate login or resource operations, or manage CloudTrail trails and backfill delivery tasks. Trigger on 操作审计, 审计日志, CloudTrail, cloud_trail, trail, 跟踪, 历史补投, or backfill in a Volcengine context. Audit queries are read-only; trail and backfill mutations require an explicit preview and confirmation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

대량 데이터 수집, 과거 데이터 보충, 변환, 동기화의 지연을 단계별로 조사합니다. 처리 방식을 비교해 속도를 높이고 행 수, 파일 수, 시각의 일치 여부를 확인합니다.

• 대량 데이터 수집과 내보내기 가속
• 과거 데이터 보충 시간 단축
• 배치 크기와 병렬 작업 수 비교

Turn exported AI chats and agent session logs into dated, searchable pages in gbrain. Check for missing conversations, extract facts, and trace when a topic first appeared or how an idea developed, with quotes and dated references.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Organizing exported AI chat histories
• Finding the first discussion of a topic
• Tracing how an idea developed

Manage ClawHub Convex production data migrations from implementation and testing through deployment, execution, verification, and temporary code removal, with dry runs and explicit user approval before destructive changes and cleanup.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Backfilling fields in production data
• Removing obsolete fields or table data
• Repairing ownership and relationships

Produce one revision-fenced Planner backfill proposal for either a Detailer replan or task-set closure, with compact Frontdesk status evidence.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

[omh] Data pipeline work -- an ETL or streaming job, a backfill or replay, duplicate events, a schema change downstream, a lineage question, a data-quality regression: make every rerun idempotent, bound every replay, and gate each load on observed checks. Use when the user says: data-pipelines, data pipeline, data pipelines, etl, elt, etl pipeline, etl job, etl backfill.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill for planning, testing, and safely executing PostgreSQL schema migrations — especially when working with production data or shared databases. **Trigger when user asks to:** - Test a schema migration before applying it to production - Add, remove, or rename columns safely on a live table - Change a column's data type without downtime - Add or drop indexes, constraints, or foreign keys on large tables - Understand which ALTER TABLE operations lock the table - Roll back a failed migration - Plan a zero-downtime migration strategy - Fork a database to test a migration safely **Keywords:** migration, schema change, ALTER TABLE, add column, drop column, rename column, change type, zero downtime, lock, AccessExclusiveLock, concurrent index, forking, rollback, backfill, deploy Covers: lock-level reference for every common DDL operation, safe migration patterns, fork-based testing, zero-downtime column changes, index creation, constraint addition, backfill strategies, pre/post-migration validation, and rollback planning.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Import a large archive into the vault in controlled batches: triage what is worth ingesting, process oldest first, checkpoint after every batch, and keep cost visible. Use this skill whenever the user wants to import years of bookmarks, an export from another notes app, a downloads folder, a chat history dump, or says "backfill", "bulk import", "process my archive". Do NOT use for ingesting one or a few new sources, which is second-brain-ingest.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Plan additive, zero-downtime schema migrations with rollout, backfill, and rollback awareness. Use when renaming columns, backfilling data, or shipping risky database changes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create a CHANGELOG.md following keepachangelog.com conventions with version history backfilled from GitHub releases or git tags. Use when the user asks to "create a changelog", "add a changelog", "initialize changelog", "start a changelog", "set up changelog", "generate changelog", or "backfill changelog".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

数据工程 — 数据平台从业者的认知操作系统, 覆盖把数据从源系统搬运成可靠 / 可查询 / 可信赖形态供分析 / ML / 数据产品消费的全生命周期 (生成 → 摄取 → 存储 → 转换 → 服务 + 安全/数据管理/DataOps/数据架构/编排/软件工程 六条暗流, Reis & Housley 框架): 摄取与集成 (批 + CDC 变更数据捕获 Debezium + EL 工具 Fivetran/Airbyte/Meltano/dlt + Kafka Connect + schema drift) / 存储与文件表格式 (对象存储数据湖 + 列存 Parquet/ORC/Arrow/Avro + 开放表格式 Apache Iceberg/Delta Lake/Apache Hudi + lakehouse + 分区/compaction) / 转换与建模 (ELT dbt/SQLMesh + Spark + 维度建模 Kimball + Inmon + Data Vault + 大宽表 OBT + 渐变维 SCD + 增量模型 + 语义/指标层) / 编排与工作流 (Apache Airflow/Dagster/Prefect/Mage/Kestra/Apache DolphinScheduler + DAG + 幂等 + 回填 backfill + 数据资产调度) / 批流与实时 (Apache Kafka/Apache Flink/Spark Structured Streaming/Kinesis/Pulsar/Redpanda + Lambda vs Kappa + watermark/窗口/exactly-once + 流式 SQL Materialize/RisingWave + 实时 OLAP ClickHouse/Apache Druid/Apache Pinot/StarRocks/Apache Doris) / 数仓与查询引擎 (Snowflake/BigQuery/Redshift/Databricks SQL/Trino/Presto/DuckDB/Polars + 存算分离 + MPP) / 数据质量测试与可观测性 (dbt tests/Great Expectations/Soda + 数据契约 + Monte Carlo data downtime + 新鲜度/量/schema 异常检测) / 数据治理编目与血缘 (DataHub/Amundsen/OpenMetadata/Unity Catalog + 列级血缘 + PII 分类 + 访问控制 + GDPR) / DataOps 与可靠性 (数据 CI/CD + 转换版本控制 + 环境隔离 + 幂等重处理 + 数据 SLA/SLO + 计算存储 FinOps) / 数据架构范式 (现代数据栈 + lakehouse + data mesh + data fabric + 去中心化 vs 中心化所有权) / 分析工程角色 (dbt 时代连接数据工程与分析的桥) — 不含 数据科学/ML 建模本身 (是下游消费者) / BI 仪表盘制作 (serving 下游) / 数据分析报表为终点 / 'data engineer = 跑 Hadoop 的' 过时窄化 / 通用后端应用开发 (平行学科) (Data Engineering — the cognitive operating system of practitioners who design, build, and operate the data platform: moving data from source systems into reliable, queryable, trustworthy form for analytics / ML / products, covering (a) the data engineering lifecycle (generation → ingestion → storage → transformation → serving, with the undercurrents security / data management / DataOps / data architecture / orchestration / software engineering — Reis & Housley framing), (b) ingestion & integration (batch + CDC change-data-capture with Debezium, EL tools Fivetran / Airbyte / Meltano / dlt, Kafka Connect, API + file + database sources, schema drift handling), (c) storage & file/table formats (object storage data lakes, columnar formats Parquet / ORC / Arrow / Avro, open table formats Apache Iceberg / Delta Lake / Apache Hudi, lakehouse architecture, partitioning / compaction / Z-ordering), (d) transformation & modeling (ELT with dbt / SQLMesh, Spark, dimensional modeling Kimball, Inmon CIF, Data Vault, One Big Table / wide tables, normalization vs denormalization, slowly changing dimensions, incremental models, the semantic / metrics layer), (e) orchestration & workflow (Apache Airflow, Dagster, Prefect, Mage, Kestra, Apache DolphinScheduler, DAGs, idempotency, backfills, data-aware / asset-based scheduling), (f) batch vs streaming & real-time (Apache Kafka, Apache Flink, Spark Structured Streaming, Kinesis / Pulsar / Redpanda, the Lambda vs Kappa debate, watermarks / windowing / exactly-once, streaming SQL Materialize / RisingWave, real-time OLAP ClickHouse / Apache Druid / Apache Pinot / StarRocks / Apache Doris), (g) warehouses & query engines (Snowflake, BigQuery, Redshift, Databricks SQL, Trino / Presto, DuckDB, Polars, decoupled storage & compute, MPP), (h) data quality, testing & observability (dbt tests, Great Expectations, Soda, data contracts, Monte Carlo / data downtime, freshness / volume / schema anomaly detection, unit / integration testing of pipelines), (i) data governance, catalog & lineage (DataHub, Amundsen, OpenMetadata, Unity Catalog, column-level lineage, PII / data classification, access control, GDPR / data privacy), (j) DataOps & reliability (CI/CD for data, version control of transformations, environments, idempotent reprocessing, SLAs / SLOs for data, cost / FinOps for compute & storage), (k) data architecture paradigms (modern data stack, data lakehouse, data mesh, data fabric, decentralized vs centralized ownership), (l) the analytics engineering role (the dbt-era bridge between data engineering and analysis); N

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

スキーマ/データ移行の安全性を framework 非依存で審査する。破壊的スキーマ変更・ロック誘発・backfill・ロールバック可逆性・expand-contract の段階適用を、prisma / typeorm / Rails / Django / Alembic / 生 SQL などに横断適用する。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Bootstrap full agent infrastructure for an existing, already-coded project without modifying a single line of source code. Surveys the repo, infers conventions from manifests, README, git history, and source samples, then generates the missing AGENTS.md, docs/architecture.md, docs/product-soul.md, ADR backfill, and seeded docs/memory/ files. Asks the user only about gaps the repo cannot reveal. Load when the user asks to "retroactive project setup", "backfill agent infrastructure", "bootstrap agents for this existing repo", "onboard agents to a legacy codebase", "set up agents without touching code", or "fill in missing agent context for this project".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Capture the "why" behind technical choices to prevent architectural drift. Load when the user makes a major technical decision, chooses a library/framework, defines a system boundary, or changes a core architectural pattern. Also triggers on "record a decision", "write an ADR", "why did we do this", "document this architectural choice", or "architectural decision record". Supports `SYNTHESIS=true` mode for retrospective ADR backfill from observed repo state — used by `retroactive-project-setup` and any future backfill skill. Essential for long-term project maintainability and agent alignment.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Plans and executes safe Prisma schema migrations with data backfills, rollback strategies, and SQL preview. Handles complex schema changes including data transformations. Use for "Prisma migrations", "schema changes", "database migrations", or "data backfills".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

ClawSweeper로 OpenClaw의 이슈와 PR을 점검합니다. 보고서 확인, 수정 작업 생성, GitHub Actions 조사와 권한 및 검증 조건에 따른 자동 수정·병합을 지원합니다.

• 이슈와 PR 점검 보고서를 확인할 때
• 기존 보고서로 수정 작업을 만들 때
• GitHub Actions 실패를 조사할 때

운영 데이터베이스의 열, 인덱스와 데이터 변경을 설계합니다. 대규모 테이블의 분할 갱신, 단계적 구조 전환과 복구 계획을 포함해 마이그레이션 절차를 정리합니다.

• 대규모 테이블에 열과 인덱스 추가
• 중단을 피하는 단계적 열 이름 변경
• 기존 데이터의 분할 보완

Turn bundled Paperclip issues, comments, and documents into readable wiki updates covering project purpose, current progress, decisions, risks, and next actions, while preserving existing knowledge and citing the supporting activity.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Summarizing recent project activity in a wiki
• Building wiki pages from historical project activity
• Recording decisions and their supporting evidence

Translate and synchronize Cherry Studio documentation in English and Simplified Chinese. Update affected sections, add missing translations, reconcile edits in both languages, and coordinate paired files during renames or deletions while checking terminology and structure.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Translating new English and Simplified Chinese document pairs
• Updating a translation after its source changes
• Reconciling sections edited in both languages

Turn work history into clear accomplishment statements for performance reviews, promotion cases, and weekly updates. Use Copilot CLI sessions, git commits, and GitHub pull requests to connect each action with its result and supporting evidence.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Recovering work accomplishments missing from a personal log
• Preparing evidence for a performance review
• Organizing achievements for a promotion case

Adapt a knowledge collection's schema, the rules defining page types and relationships. Review untyped pages, propose new types, update classification settings, and apply those types to existing pages after previewing the changes and checking consistency.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding page types for researchers and papers
• Classifying existing pages that have no type
• Proposing new types from stored content

Prepare software releases by detecting version files, reviewing changes, and writing changelogs in multiple languages. The workflow updates versions, creates annotated tags with release notes, and can publish GitHub Releases or fill in missing historical releases.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing a new version from recent changes
• Updating changelogs in multiple languages
• Previewing release changes without modifying files

Summarize WeChat group conversations into organized digests with discussion highlights, verified speaker attribution, and message statistics. Keep group history, participant profiles, and factual notes across runs, or summarize only messages received since the previous digest.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Catching up on a week's WeChat group discussions
• Summarizing messages since the previous digest
• Reviewing message counts and active participants

Generate Drizzle database migrations on a fresh Neon branch and review their production safety. Check table sizes, locking order, execution time, and data transfer needs, with load testing for changes affecting busy or large tables.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Generate migrations after changing a database schema
• Review locking risks before production deployment
• Rehearse large table changes under load