菜单
Database and data management conventions for all projects using databases. Covers schema migrations, backup strategy, data lifecycle, index management, and connection pooling. Applied when designing, implementing, or reviewing database interactions.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Scan a project for missing best-practice areas and implement the top recommendation for each gap (linting, unit testing) — installs tools, writes configs, verifies, and commits. Pass 'recommend' to stop after writing recommendations without implementing (replaces the old do-recommend skill).
Implement a focused code change. Use this skill as the wrapper for any implementation work so the Maverick workflow report captures what was done and so the agent applies the project's coding standards before editing. Intended to be invoked once per task from inside a do-issue-* or do-epic phase, not standalone.
Audit a codebase for security risks in one of two modes. In full-audit mode it scans the entire codebase and writes a findings report to docs/security-audit.md (run as part of do-init or on demand). In update mode it reviews only a diff plus the code it could impact, returning a structured findings list as a pre-push gate for do-issue-solo and do-issue-guided. Covers secrets exposure, dependency vulnerabilities, authentication and authorisation patterns, input validation, transport security, and common OWASP risks.
Create, restructure, or update technical documentation. Handles greenfield projects, refactoring non-compliant docs, and incremental updates after code changes.
Work on a multi-story GitHub epic end-to-end. Builds a DAG from the child stories, groups them into waves, runs waves in parallel via per-story worktrees, ejects PRs that fail agent-code-review for human handling, and propagates blocks to downstream stories. Requires git worktrees.
Initialise a project for use with Maverick — verifies the GitHub App, installs the CLI if needed, writes the project config with integration tracking, scaffolds docs, generates project skills, runs an initial cybersecurity audit, then commits the changes and opens a PR.
| name | mav-bp-database-management |
| description | Database and data management conventions for all projects using databases. Covers schema migrations, backup strategy, data lifecycle, index management, and connection pooling. Applied when designing, implementing, or reviewing database interactions. |
| user-invocable | false |
| disable-model-invocation | true |
Maverick's hard rules for schema migrations, environment isolation, and data safety.
WHERE/JOIN/ORDER BY/GROUP BY clauses; remove unused indexes.DROP/RENAME/type changes require the expand-backfill-contract pattern: deploy code that stops using the column first, then migrate.Check for docs/maverick/skills/database-management/SKILL.md. If present, read it — it wins on specifics (library, config, conventions). If missing, proceed with these standards and note the gap in your summary.
When reviewing code, flag these patterns:
| Pattern | Issue | Fix |
|---|---|---|
| Raw SQL without parameterised queries | SQL injection risk | Use parameterised queries or ORM |
| Manual schema change (ad-hoc DDL) | Unreproducible, untracked change | Create a migration file |
| Editing an already-applied migration | Breaks migration history | Write a new migration |
| No index on columns used in WHERE/JOIN | Performance degradation at scale | Add appropriate index |
| Opening connection per request (no pooling) | Connection exhaustion | Use connection pool |
| Hardcoded connection string | Security risk, environment coupling | Use environment variables or secrets manager |
| Missing down migration | Cannot revert in development | Add reversible down operation |
| Production data in seed files | Data leak, privacy violation | Use synthetic data only |
DROP TABLE or DROP COLUMN without staged rollout | Breaks running application | Stage the change: remove code references first |
| No transaction wrapping for multi-step migration | Partial application on failure | Wrap in transaction where the database supports it |