AGENT SKILL

liquibase-expert

Use when implementing liquibase functionality with production-grade patterns and safeguards.

License 许可
MIT
最近更新
2026-04-11
Stars
★ 3
Forks
0

01 前言 Front Matter

name
liquibase-expert
metadata
{ "hermes": { "tags": [ "codex-agent", "general" ], "source": "codex-field-kit/general" } }
description
Use when implementing liquibase functionality with production-grade patterns and safeguards.

03 SKILL.md 正文

Liquibase Expert

Focus Areas

  • Understanding of changeSets and changeLogs
  • Managing database migrations with Liquibase
  • Implementing database version control
  • Best practices for rollback and change tracking
  • Support for multiple database types
  • Integration with CI/CD pipelines
  • XML, JSON, and YAML format support for changeLogs
  • Custom preconditions and change types
  • Liquibase command-line and Maven plugin usage
  • Generating and applying diff reports

Approach

  • Define changeSets with unique identifiers
  • Use contexts and labels for environment segregation
  • Ensure changeLogs are idempotent
  • Keep changeSets small and focused
  • Write rollback scripts for all changes
  • Use Liquibase properties files for configuration
  • Validate database schema before and after changes
  • Automate Liquibase execution in build processes
  • Test migrations in a staging environment
  • Document changes in changeLogs for clarity

Quality Checklist

  • ChangeSets are correctly formatted and validated
  • Schema changes are reversible with rollback scripts
  • ChangeLogs are organized and maintainable
  • Operations are atomic to prevent partial updates
  • Consistent naming conventions are followed
  • All database types supported by the project are tested
  • Build and deployment processes include Liquibase commands
  • Diff reports are generated and reviewed
  • Database is always in a known state post-migration
  • Backups are verified before applying changes

Output

  • Well-organized changeLogs in chosen format (XML, JSON, or YAML)
  • Validated and tested changeSets ready for deployment
  • Rollback procedures for all changeSets
  • Documentation of changeSets and their purposes
  • Consistent and automated migration process
  • Integration with existing CI/CD pipelines
  • Regularly tested backup and restore procedures
  • Verified Liquibase property configurations
  • Manual and automated testing results
  • Audit trails for all database changes

04 同仓库更多 Skills

0xharryriddle
0xharryriddle/codex-field-kit

vercel-react-best-practices

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

前端开发
★ 3
0xharryriddle
0xharryriddle/codex-field-kit

swarm-planner

[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.

★ 3
0xharryriddle
0xharryriddle/codex-field-kit

super-swarm-spark

Only to be triggered by explicit super-swarm-spark commands.

★ 3
0xharryriddle
0xharryriddle/codex-field-kit

role-creator

Create and install Codex custom agent roles in ~/.codex/config.toml, generate role config files, enforce supported keys, and guide users through required role inputs (model, reasoning effort, developer_instructions).

★ 3
0xharryriddle
0xharryriddle/codex-field-kit

read-github

Read and search GitHub repository documentation via gitmcp.io MCP service. **WHEN TO USE:** - User provides a GitHub URL - User mentions a specific repo in owner/repo format - User asks "what does this repo do?", "read the docs for X repo", or similar - User wants to search code or docs within a repo

Skill与智能体开发
★ 3
0xharryriddle
0xharryriddle/codex-field-kit

planner

Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.

★ 3