packmind: Skill for Claude Code

.claude/skills/how-to-write-typeorm-migrations-in-packmind/SKILL.md

how-to-write-typeorm-migrations-in-packmind is a skill for Claude Code from PackmindHub/packmind. It costs 99 tokens per session (1,398 once invoked), scanned A, original, Apache-2.0.

A guide for writing TypeORM migration files in the Packmind monorepo, a repository containing multiple related packages. These files record database structure changes such as new tables, columns, and links between tables.

In plain words
What is it for?
Use it when creating or changing database tables, columns, or foreign-key relationships in Packmind.
Why use it?
It helps keep database changes versioned, consistently logged, and reversible if a change needs to be undone.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is PackmindHub/packmind's own configuration. It tells Claude Code how to work on packmind itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything packmind configures →

Reuse

Borrowing it

Nothing to install: this file belongs to PackmindHub/packmind. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/PackmindHub/packmind/main/.claude/skills/how-to-write-typeorm-migrations-in-packmind/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/PackmindHub/packmind

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for how-to-write-typeorm-migrations-in-packmind

README.md
[![agentmods](https://agentmods.dev/badge/skills/packmindhub/packmind/how-to-write-typeorm-migrations-in-packmind/github.svg)](https://agentmods.dev/skills/packmindhub/packmind/how-to-write-typeorm-migrations-in-packmind)
Your own site
<a href="https://agentmods.dev/skills/packmindhub/packmind/how-to-write-typeorm-migrations-in-packmind"><img src="https://agentmods.dev/badge/skills/packmindhub/packmind/how-to-write-typeorm-migrations-in-packmind/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for how-to-write-typeorm-migrations-in-packmind

Your own site · 80×15
<a href="https://agentmods.dev/skills/packmindhub/packmind/how-to-write-typeorm-migrations-in-packmind"><img src="https://agentmods.dev/badge/skills/packmindhub/packmind/how-to-write-typeorm-migrations-in-packmind.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 99 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,398 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium MCP Rug Pull · line 30
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00099 $0.01398
Opus 5 $0.00049 $0.00699
Sonnet 5 $0.00020 $0.00280
Haiku 4.5 $0.00010 $0.00140

Measured 9d ago against content hash eb11a7420316, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

how-to-write-typeorm-migrations-in-packmind scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/how-to-write-typeorm-migrations-in-packmind/SKILL.md · 193 lines

How it starts

The opening of the file, as written. The whole thing — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Write TypeORM migrations in the Packmind monorepo to manage database schema changes effectively while ensuring proper logging and rollback capabilities.

When to Use

  • When you need to create new database tables
  • When adding or modifying columns in existing tables
  • When creating or updating foreign key relationships
  • When making any database schema changes that need to be version controlled

Context Validation Checkpoints

  • Have you identified the exact database schema changes needed?
  • Do you know the TypeORM column types for all fields?
  • Have you planned the rollback strategy (down method)?
  • Are you familiar with the shared migration utilities in @packmind/shared?

Recipe Steps

Step 1: Create Migration File Using TypeORM CLI

IMPORTANT: Always create migration files using the TypeORM CLI command. Never create migration files manually. The CLI automatically generates a timestamp prefix and sets up the basic structure.

# Create new migration file (TypeORM will automatically add timestamp)
npx typeorm migration:create packages/migrations/src/migrations/DescriptiveName

Step 2: Set Up Basic Migration Structure with Logging

Implement the migration class with PackmindLogger for comprehensive logging. Include try-catch blocks and log start, progress, completion, and any errors.

import { MigrationInterface, QueryRunner } from 'typeorm';
import { PackmindLogger, LogLevel } from '@packmind/shared';

export class YourMigrationName1234567890 implements MigrationInterface {
  private readonly logger = new PackmindLogger(
    'YourMigrationName1234567890',
    LogLevel.DEBUG,
  );

  public async up(queryRunner: QueryRunner): Promise<void> {
    this.logger.info('Starting migration: YourMigrationName');
    
    try {
      // Your migration logic here
      this.logger.info('Migration YourMigrationName completed successfully');
    } catch (error) {
      this.logger.error('Migration YourMigrationName failed', {
        error: error.message,
      });
      throw error;
    }
  }

  public async down(queryRunner: QueryRunner): Promise<void> {
    this.logger.info('Starting rollback: YourMigrationName');
    
    try {
      // Your rollback logic here
      this.logger.info('Rollback YourMigrationName completed successfully');
    } catch (error) {
      this.logger.error('Rollback YourMigrationName failed', {
        error: error.message,
      });
      throw error;
    }
  }
}

Read the full file on GitHub · 193 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 193 lines · 99 tokens per session scan A eb11a7420316

Subscribe to this mod's changes

how-to-write-typeorm-migrations-in-packmind is a skill published in the GitHub repository PackmindHub/packmind (310 stars, last pushed today), licensed Apache-2.0. It adds 99 tokens to every session and 1,398 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories