New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Ef Core Migrations

by jihadkhawaja in jihadkhawaja/Egroo

Handle EF Core schema changes in Egroo. An agent skill from jihadkhawaja/Egroo.

Apache-2.0Auto-check passedDatabases

Install Ef Core Migrations

skills CLI
$ npx skills add jihadkhawaja/Egroo --skill ef-core-migrations -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jihadkhawaja/Egroo ef-core-migrations --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jihadkhawaja/Egroo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/ef-core-migrations .claude/skills/ef-core-migrations && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
ef-core-migrations
GitHub stars
178
Token cost
~673 tokens
SKILL.md length
265 words
Files
1
Skills in repo
3
Repo updated
First seen
Licence
Apache-2.0

At a glance

Handle EF Core schema changes in Egroo. An agent skill from jihadkhawaja/Egroo.

  • Works in 3 steps: Add a migration for the change. → Update the database with that migration. → Verify the solution still builds and the…
  • Changing entity properties
  • SKILL.md covers When to Use, Required Rule, Commands and What Counts As A Schema Change, plus 2 more sections
  • Calls dotnet

What it does

Ef Core Migrations is an agent skill from jihadkhawaja/Egroo. Handle EF Core schema changes in Egroo. Use for: adding or changing entity properties, owned types, relationships, indexes, table mappings, naming conventions, or anything in DataContext/OnModelCreating that changes the PostgreSQL schema. Covers when to add a migration, how to update the database, and what to verify afterwards.

Its SKILL.md is about 670 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Databases. It works with PostgreSQL. The repository describes itself as: A refined social platform for humans and AI agents. Private by default. Yours by design. The licence is Apache-2.0.

When your agent uses it

  • Changing entity properties
  • Naming conventions
  • Anything in DataContext/OnModelCreating that changes the PostgreSQL schema

Example prompts

  • “/ef-core-migrations”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Add a migration for the change.
  2. Update the database with that migration.
  3. Verify the solution still builds and the relevant tests still pass.

What it can do on your machine

Read from SKILL.md and the folder at commit a69d04b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • dotnet

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Ef Core Migrations loads about 673 tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 265 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~87
When it runs · the whole SKILL.md, loaded when a task matches
~673

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jihadkhawaja/Egroo at commit a69d04b, republished under its Apache-2.0 licence (© jihadkhawaja). 265 words, ~673 tokens.

Download SKILL.mdSave it as .claude/skills/ef-core-migrations/SKILL.md (or your agent's skills folder).
name
ef-core-migrations
description
Handle EF Core schema changes in Egroo. Use for: adding or changing entity properties, owned types, relationships, indexes, table mappings, naming conventions, or anything in DataContext/OnModelCreating that changes the PostgreSQL schema. Covers when to add a migration, how to update the database, and what to verify afterwards.
argument-hint
Describe the schema change (e.g. "add user public key columns", "new channel index", "rename owned type column")

EF Core Migrations — Egroo Schema Workflow

When to Use

  • Adding, removing, or renaming entity properties that are persisted to the database
  • Changing User, Channel, Message, agent, or other EF Core entity mappings
  • Modifying DataContext, OnModelCreating, owned entities, indexes, constraints, or relationships
  • Updating table or column naming behavior
  • Any change where the runtime model and the database schema would otherwise drift

Required Rule

If a change affects the EF Core schema, you must:

  1. Add a migration for the change.
  2. Update the database with that migration.
  3. Verify the solution still builds and the relevant tests still pass.

Do not leave entity/model changes without a matching migration.

Commands

Run from the repository root:

powershell
.\scripts\add-migration.ps1 "<MigrationName>"
.\scripts\update-database.ps1

Migrations target src/Egroo.Server.

What Counts As A Schema Change

  • New persisted properties on shared/server entities
  • Removed persisted properties
  • Property type changes
  • New DbSet<> entries
  • Relationship changes (HasOne, HasMany, FKs, join tables)
  • Index changes
  • Owned type changes
  • Table/column naming changes
  • Required/optional changes that affect generated columns or constraints

These do not usually require a migration by themselves:

  • [NotMapped] properties only
  • Pure UI/view-model changes
  • Comments, logging, or behavior-only service changes

Verification Checklist

  • dotnet build src/Egroo.slnx --configuration Debug
  • dotnet test src/Egroo.Server.Test/Egroo.Server.Test.csproj --verbosity normal when server behavior changed
  • Confirm the migration files are present under src/Egroo.Server/Migrations/
  • Confirm DataContextModelSnapshot reflects the new schema

Egroo-Specific Notes

  • The repo uses lowercase naming conventions. Expect generated database names to end up lowercase.
  • Prefer the provided PowerShell scripts instead of ad hoc EF commands so the right project/startup wiring is used.
  • If a change touches shared models but should not persist, keep it [NotMapped] or otherwise excluded from the EF model.

© jihadkhawaja, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .github/skills/ef-core-migrations of jihadkhawaja/Egroo.

Open the folder on GitHubat commit a69d04b

Compare with similar skills

Ef Core Migrations next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Ef Core Migrations compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Ef Core Migrations this skilljihadkhawaja/Egroo178—~673Automated safety check: PassApache-2.0
Backend Test WorkerCorrectRoadH/OpenTickly307—~1.3kAutomated safety check: PassAGPL-3.0
Diagnose Cloud SessionFreakStudioCN/mpy-hardware-extension154—~809Automated safety check: NotesCustom licence
Add Oliphaunt Extensionf0rr0/oliphaunt106—~1.7kAutomated safety check: PassMIT
DB AdminEliasOulkadi/shokunin114—~2kAutomated safety check: NotesMIT
Postgresql Table Designynulihao/AgentSkillOS61815 repos~4kAutomated safety check: PassNone

Similar skills

  • Backend Test Worker

    CorrectRoadH/OpenTickly

    Build and verify real-Postgres Go tests and thin transport smoke for tracking behavior.

    307 GitHub stars~1.3k tokensUpdated yesterday
    DatabasesAuto-check passed

  • Diagnose Cloud Session

    FreakStudioCN/mpy-hardware-extension

    用户报告 Blockless 扩展在云端实测时出问题（卡死/灰屏/跳步/构建失败），但本地复现不了、日志不在本地文件里时，用这个从云端托管数据库拉真实 session 定位症状与根因 / Use when a user reports an in-product Blockless bug from live cloud-backend testing and the real session…

    154 GitHub stars~809 tokensUpdated 12 days ago
    DatabasesAuto-check: notes

  • Add Oliphaunt Extension

    f0rr0/oliphaunt

    Add, update, or remove an Oliphaunt PostgreSQL contrib or external extension, including source pins, build recipes, target support, SDK metadata, release products, carrier identities, and package…

    106 GitHub stars~1.7k tokensUpdated today
    DatabasesAuto-check passed

  • DB Admin

    EliasOulkadi/shokunin

    PostgreSQL database administration — backup/restore (pgdump, PITR, WAL archiving), health monitoring (connections, bloat, cache hit ratio, dead tuples), connection pooling (PgBouncer), replication…

    114 GitHub stars~2k tokensUpdated 5 days ago
    DatabasesAuto-check: notes

  • Postgresql Table Design

    ynulihao/AgentSkillOS

    Design a PostgreSQL-specific schema. An agent skill from ynulihao/AgentSkillOS.

    618 GitHub starsUsed in 15 repos~4k tokens
    DatabasesAuto-check passed

  • Postgres Patterns

    ThibautBaissac/rails_ai_agents

    PostgreSQL database patterns for query optimization, schema design, indexing, and security.

    665 GitHub starsUsed in 7 repos~922 tokens
    DatabasesAuto-check passed

More from jihadkhawaja/Egroo

  • Agent Framework

    jihadkhawaja/Egroo

    Build, extend, and debug AI agents in Egroo using the Microsoft Agent Framework (C .NET).

    178 GitHub stars~1.9k tokensUpdated 6 mo ago
    Auto-check passed

  • Mudblazor Theming

    jihadkhawaja/Egroo

    Apply consistent Material Design UI theming in Egroo using MudBlazor.

    178 GitHub stars~1.6k tokensUpdated 6 mo ago
    Auto-check passed

Works with

Categories

Questions about Ef Core Migrations

What does Ef Core Migrations do?

Handle EF Core schema changes in Egroo. An agent skill from jihadkhawaja/Egroo. Ef Core Migrations is an agent skill from jihadkhawaja/Egroo. Handle EF Core schema changes in Egroo.

When should I use Ef Core Migrations?

Ef Core Migrations fits situations like: changing entity properties; naming conventions; anything in DataContext/OnModelCreating that changes the PostgreSQL schema.

How do I install Ef Core Migrations in Claude Code?

Run `npx skills add jihadkhawaja/Egroo --skill ef-core-migrations -a claude-code`. Or copy the skill folder (.github/skills/ef-core-migrations in jihadkhawaja/Egroo) into .claude/skills/ef-core-migrations in your project. Claude Code loads it when a task matches its description.

How do I install Ef Core Migrations in Codex?

Run `npx skills add jihadkhawaja/Egroo --skill ef-core-migrations -a codex`. Or copy the skill folder (.github/skills/ef-core-migrations in jihadkhawaja/Egroo) into .agents/skills/ef-core-migrations in your project. Codex loads it when a task matches its description.

Can I use Ef Core Migrations in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jihadkhawaja/Egroo --skill ef-core-migrations -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ef-core-migrations, .gemini/skills/ef-core-migrations, .github/skills/ef-core-migrations and .opencode/skills/ef-core-migrations in your project.

What does Ef Core Migrations need to run?

Going by SKILL.md and its folder, Ef Core Migrations needs the command-line tools its instructions call (dotnet).

Does Ef Core Migrations access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Ef Core Migrations safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Ef Core Migrations use?

Ef Core Migrations is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Ef Core Migrations use?

About 673 tokens (SKILL.md is roughly 2.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Ef Core Migrations?

Skills that share tags, products or a category with Ef Core Migrations: Backend Test Worker (CorrectRoadH/OpenTickly, 307 stars), Diagnose Cloud Session (FreakStudioCN/mpy-hardware-extension, 154 stars), Add Oliphaunt Extension (f0rr0/oliphaunt, 106 stars) and DB Admin (EliasOulkadi/shokunin, 114 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ef Core Migrations?

jihadkhawaja (a GitHub user) maintains it in jihadkhawaja/Egroo, which has 178 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on March 26, 2026.

Source: jihadkhawaja/Egroo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.