تشغيل أي مهارة في Manus بنقرة واحدة

ابدأ الآن

applying-staging-candidate

النجوم٣

التفرعات٠

آخر تحديث١٩ أبريل ٢٠٢٦ في ٠٠:٠٦

Use internally when /refactor-mart dispatches one approved Type: stg candidate

التثبيت

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

تشغيل في Manus

المصدر

accelerate-data

accelerate-data/migration-utility

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

تنزيل

تشغيل في Manus

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

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

مطوّرو البرمجياتمهن الحاسوب والرياضيات·SOC 15-1252

مستكشف الملفات

3 ملفات

SKILL.md

readonly

name	applying-staging-candidate
description	Use internally when /refactor-mart dispatches one approved Type: stg candidate

Applying Staging Candidate

Apply one approved staging candidate and update only that candidate section.

Inputs

Parse exactly two positional arguments:

<plan-file> <candidate-id>

Read references only when needed:

references/staging-validation-contract.md before deciding scope, rewrites, validation, or status writeback.
references/status-writeback.md before updating plan status.

Checks

Missing plan file: stop with PLAN_NOT_FOUND.
Missing candidate section: stop with CANDIDATE_NOT_FOUND.
Before editing files or plan status, extract the plan Targets plus the candidate Output: and Validation: model names, then scan matching catalog table and view entries for unresolved diagnostics with severity: "error". If any exist, stop with CATALOG_ERRORS_UNRESOLVED, report the catalog object and error code, and do not apply, validate, or update the candidate.
Candidate not approved with - [x] Approve: yes: stop with CANDIDATE_NOT_APPROVED.
Type: is not stg: stop with NON_STAGING_CANDIDATE; do not change execution status.
Missing or invalid Output: for a stg_* model: mark this candidate blocked.
Missing or ambiguous downstream scope: mark this candidate blocked.

Workflow

Read the plan and isolate ## Candidate: <candidate-id>.
Extract Output: and Validation:.
Resolve staging output and downstream consumers using references/staging-validation-contract.md.
Create or update the declared stg_* model.
Rewire every resolved downstream consumer file so it references the declared stg_* model with ref().
Run the smallest validation command covering the staging model and resolved consumers. Prefer the command listed in Validation:.
Update only this candidate section using references/status-writeback.md.

Completion

Report:

applying-staging-candidate complete -- <candidate-id>

status: applied|failed|blocked
validation: <command or reason>
plan: <plan-file>

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

نفس المستودع

verifying-completion-claims

accelerate-data/migration-utility

Use automatically before any completion, successful, passing, PR-ready, merged, or stage-complete statement to verify fresh evidence and choose accurate claim wording.

2026-04-223

applying-mart-candidates

accelerate-data/migration-utility

Use internally when /refactor-mart dispatches one approved Type: int or Type: mart candidate

2026-04-213

classifying-data-domains

accelerate-data/migration-utility

Use when a monolith warehouse or lakehouse has a whole-warehouse `warehouse-ddl/` snapshot and needs tables or views grouped into business data domains with data owners for data mesh decentralization, setup-source selection, migration planning, or scope and migrate-mart inputs.

2026-04-213

generating-model

accelerate-data/migration-utility

Use when generating or revising one dbt model for a single profiled table or view after refactor and approved test-spec work are complete.

2026-04-213

reviewing-model

accelerate-data/migration-utility

Use when the generate-model workflow needs a read-only review of generated dbt model artifacts before accepting the result or sending it back for fixes.

2026-04-213

generating-tests

accelerate-data/migration-utility

Use when a migrated table, view, or materialized view needs a new or merge-safe `test-specs/<schema.object>.json`, especially after SQL changes or reviewer feedback.

2026-04-193

name	applying-staging-candidate
description	Use internally when /refactor-mart dispatches one approved Type: stg candidate

Applying Staging Candidate

Apply one approved staging candidate and update only that candidate section.

Inputs

Parse exactly two positional arguments:

<plan-file> <candidate-id>

Read references only when needed:

references/staging-validation-contract.md before deciding scope, rewrites, validation, or status writeback.
references/status-writeback.md before updating plan status.

Checks

Missing plan file: stop with PLAN_NOT_FOUND.
Missing candidate section: stop with CANDIDATE_NOT_FOUND.
Before editing files or plan status, extract the plan Targets plus the candidate Output: and Validation: model names, then scan matching catalog table and view entries for unresolved diagnostics with severity: "error". If any exist, stop with CATALOG_ERRORS_UNRESOLVED, report the catalog object and error code, and do not apply, validate, or update the candidate.
Candidate not approved with - [x] Approve: yes: stop with CANDIDATE_NOT_APPROVED.
Type: is not stg: stop with NON_STAGING_CANDIDATE; do not change execution status.
Missing or invalid Output: for a stg_* model: mark this candidate blocked.
Missing or ambiguous downstream scope: mark this candidate blocked.

Workflow

Read the plan and isolate ## Candidate: <candidate-id>.
Extract Output: and Validation:.
Resolve staging output and downstream consumers using references/staging-validation-contract.md.
Create or update the declared stg_* model.
Rewire every resolved downstream consumer file so it references the declared stg_* model with ref().
Run the smallest validation command covering the staging model and resolved consumers. Prefer the command listed in Validation:.
Update only this candidate section using references/status-writeback.md.

Completion

Report:

applying-staging-candidate complete -- <candidate-id>

status: applied|failed|blocked
validation: <command or reason>
plan: <plan-file>