Run any Skill in Manus with one click

atlas-best-practices

Stars51

Forks6

UpdatedFebruary 26, 2026 at 02:30

Use when working with atlas.hcl, Atlas CLI commands, schema HCL/SQL files, or migration planning and reviews, including Atlas v1.1 security, data, and exporter capabilities.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

alleneubank

alleneubank/claude-code

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Database ArchitectsComputer and Mathematical Occupations·SOC 15-1243

File Explorer

5 files

SKILL.md

readonly

name	atlas-best-practices
description	Use when working with atlas.hcl, Atlas CLI commands, schema HCL/SQL files, or migration planning and reviews, including Atlas v1.1 security, data, and exporter capabilities.

Atlas Best Practices

Atlas supports declarative and versioned schema workflows. Keep this file minimal and load only the reference file needed for the current task.

Workflow Selection

Use declarative workflow when desired schema state is the source of truth.
Use versioned workflow when migration files are required for auditing and staged deployments.
Use baseline workflow when onboarding an existing database.

Default Execution Flow

Confirm the target env in atlas.hcl.
Confirm dev is configured and isolated from production.
Plan first, then lint/test/validate, then apply.
Run production changes through CI/CD or approved deployment workflow.

Quick Commands

# Declarative
atlas schema apply --env local

# Versioned
atlas migrate diff add_change --env local
atlas migrate lint --env local --latest 1
atlas migrate apply --env local

# Integrity
atlas migrate validate --env local
atlas migrate status --env local

Reference Map

core-workflows.md Use for environment config, schema-as-code patterns, declarative vs versioned workflows, baselining, and ORM provider loading.
safety-and-quality.md Use for lint analyzers, transaction modes, schema tests, pre-execution checks, and CI patterns.
atlas-v1-1-features.md Use for Atlas v1.1 coverage (released on 2026-02-03), including security as code, declarative data, new drivers/platform support, Slack integration, schema exporters, and MySQL TLS.
cli-agent-gaps.md Use for Atlas CLI capabilities and edge cases agents often miss: planning workflows, migration directory maintenance commands, URL/TLS pitfalls, feature availability, and version policy constraints.

Guardrails

Keep credentials out of source files; prefer Atlas data sources and input variables.
Require explicit review for destructive or data-dependent migrations.
Fail loudly on unsupported drivers, missing dev URLs, or unknown environment names.

More from this repository

same repository

brief-best-practices

alleneubank/claude-code

Use when creating, reviewing, or updating a BRIEF.md (the quality law for a surface), defining what "good"/shippable means, or setting up a verified autonomous loop.

2026-06-1751

tilt

alleneubank/claude-code

Use when checking deployment health, investigating errors, reading logs, or working with Tiltfiles. Queries Tilt resource status, logs, and manages dev environments.

2026-06-1051

tiltup

alleneubank/claude-code

Use when starting tilt, debugging Tiltfile errors, or bootstrapping a dev environment. Starts Tilt in zmx, monitors bootstrap to healthy state, fixes Tiltfile bugs without hard-coding or fallbacks.

2026-06-1051

git-best-practices

alleneubank/claude-code

Use when creating commits, managing branches, opening PRs, or rewriting history. Not for non-git implementation tasks or repo-specific release policy decisions.

2026-05-2951

git-rebase-sync

alleneubank/claude-code

Use when syncing a feature branch onto the latest origin base branch via git rebase.

2026-05-2951

git-worktree-tidy

alleneubank/claude-code

Fetch latest from origin, prune remote-tracking refs, delete stale local branches and worktrees, and fast-forward important branches. Use when tidying up a worktree-based repo layout.

2026-05-2951

name	atlas-best-practices
description	Use when working with atlas.hcl, Atlas CLI commands, schema HCL/SQL files, or migration planning and reviews, including Atlas v1.1 security, data, and exporter capabilities.

Atlas Best Practices

Atlas supports declarative and versioned schema workflows. Keep this file minimal and load only the reference file needed for the current task.

Workflow Selection

Use declarative workflow when desired schema state is the source of truth.
Use versioned workflow when migration files are required for auditing and staged deployments.
Use baseline workflow when onboarding an existing database.

Default Execution Flow

Confirm the target env in atlas.hcl.
Confirm dev is configured and isolated from production.
Plan first, then lint/test/validate, then apply.
Run production changes through CI/CD or approved deployment workflow.

Quick Commands

# Declarative
atlas schema apply --env local

# Versioned
atlas migrate diff add_change --env local
atlas migrate lint --env local --latest 1
atlas migrate apply --env local

# Integrity
atlas migrate validate --env local
atlas migrate status --env local

Reference Map

core-workflows.md Use for environment config, schema-as-code patterns, declarative vs versioned workflows, baselining, and ORM provider loading.
safety-and-quality.md Use for lint analyzers, transaction modes, schema tests, pre-execution checks, and CI patterns.
atlas-v1-1-features.md Use for Atlas v1.1 coverage (released on 2026-02-03), including security as code, declarative data, new drivers/platform support, Slack integration, schema exporters, and MySQL TLS.
cli-agent-gaps.md Use for Atlas CLI capabilities and edge cases agents often miss: planning workflows, migration directory maintenance commands, URL/TLS pitfalls, feature availability, and version policy constraints.

Guardrails

Keep credentials out of source files; prefer Atlas data sources and input variables.
Require explicit review for destructive or data-dependent migrations.
Fail loudly on unsupported drivers, missing dev URLs, or unknown environment names.