Agent skill

Django Run Migrations

by fossasia in fossasia/eventyay

Steps for generating and applying Django migrations. An agent skill from fossasia/eventyay.

Apache-2.0Auto-check passedBackend & APIs

Install Django Run Migrations

skills CLI
$ npx skills add fossasia/eventyay --skill django-run-migrations -a claude-code

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

GitHub CLI
$ gh skill install fossasia/eventyay django-run-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/fossasia/eventyay.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/django-run-migrations .claude/skills/django-run-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
django-run-migrations
GitHub stars
1.7k
Token cost
~433 tokens
SKILL.md length
238 words
Files
4 (incl. references, assets)
Skills in repo
21
Repo updated
First seen
Licence
Apache-2.0

At a glance

Steps for generating and applying Django migrations. An agent skill from fossasia/eventyay.

  • Works in 3 steps: Navigate to the app context: cd app/ → Generate the required migration… → Execute and apply the generated…
  • Tasks that involve Backend development
  • SKILL.md covers When to use, Steps, Validation and Gotchas, plus 1 more section
  • Calls python

What it does

Django Run Migrations is an agent skill from fossasia/eventyay. Steps for generating and applying Django migrations

Its SKILL.md is about 430 tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files and assets (for example `assets/migration-review-template.md`, `references/migration-safety-guide.md` and `tests/migration-scenarios.md`).

It sits in Backend & APIs, covering Backend development. It works with Django. The repository describes itself as: Open Source Event Management, Ticketing and Checkins, Talks and Schedules, Video and Interpretations, Badges, Exhibitions and more https://eventyay.com. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Backend development

Example prompts

  • “Use the django-run-migrations skill to step for generating and applying Django migrations. An agent skill from fossasia/eventyay”
  • “/django-run-migrations”

Requirements

  • Python 3

Workflow steps

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

  1. Navigate to the app context: cd app/
  2. Generate the required migration definitions by running: python manage.py makemigrations
  3. Execute and apply the generated migration file to the DB safely: python manage.py migrate

What it can do on your machine

Read from SKILL.md and the folder at commit 286485c. 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:

    • python

    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

Django Run Migrations loads about 433 tokens when it runs, and up to ~574 if it reads all its reference files. Until then it costs about 18 tokens; SKILL.md has 238 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~18
When it runs · the whole SKILL.md, loaded when a task matches
~433
With references · SKILL.md plus every file in references/, read only if the agent opens them
~574

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 fossasia/eventyay at commit 286485c, republished under its Apache-2.0 licence (© fossasia). 238 words, ~433 tokens.

Download SKILL.mdSave it as .claude/skills/django-run-migrations/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
django-run-migrations
description
Steps for generating and applying Django migrations

When to use

Use this skill continuously after modifying any models.py schema logic to apply the changes to the database.

Steps

  1. Navigate to the app context: cd app/
  2. Generate the required migration definitions by running: python manage.py makemigrations
  3. Execute and apply the generated migration file to the DB safely: python manage.py migrate

Validation

  1. Verify that the terminal explicitly outputs "Applying..." states and succeeds without tracebacks.
  2. Quickly review the auto-generated .py migration output to ensure logical alignment with your model edits.

Gotchas

  • Do not manually edit auto-generated migration files unless executing an explicitly necessary, advanced requirement (i.e. complex data backfill operations). Never rewrite migrations that have already been applied to a shared or production database; instead, create a new migration for any additional schema changes.

Tips

If your changes in Django models don't cause a change in the actual database schema, you don't need to create a migration at all.

Typical changes that do not affect the DB schema include:

  • choices
  • verbose_name
  • help_text

In these cases:

  • Do not run makemigrations just to capture these metadata-only changes.
  • Do not edit existing migration files that may already have been applied. The only safe exception is in a narrowly scoped, pre-merge situation where a migration has never been applied to any shared or production database and you are cleaning up that pending migration before it lands. Otherwise, always create a new migration to capture real schema changes.

© fossasia, 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

SKILL.md and 3 other files (references, assets) in .agents/skills/django-run-migrations of fossasia/eventyay.

  • SKILL.md
  • assets/migration-review-template.md
  • references/migration-safety-guide.md
  • tests/migration-scenarios.md

Open the folder on GitHubat commit 286485c

Compare with similar skills

Django Run 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.

Django Run Migrations compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Django Run Migrations this skillfossasia/eventyay1.7k—~433Automated safety check: PassApache-2.0
Saleor Django Schema Migrationsaleor/saleor23k—~1kAutomated safety check: PassBSD-3-Clause
Django Access Reviewgetsentry/skills1k3 repos~2.6kAutomated safety check: NotesApache-2.0
Silk Profilerbaserow/baserow6.1k—~2.9kAutomated safety check: PassCustom licence
Arch Wikiahmedemad3/arch-wiki250—~5.1kAutomated safety check: PassNone
Run Testsnetboxlabs/netbox-branching155—~1.2kAutomated safety check: PassCustom licence

Similar skills

  • Generates and splits Django schema migrations for Saleor with manage.py makemigrations, enforcing one new model or one field change per migration file.

    23k GitHub stars~1k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Django Access Review

    getsentry/skills

    Official

    Django access control and IDOR security review. An agent skill from getsentry/skills.

    1k GitHub starsUsed in 3 repos~2.6k tokens
    Backend & APIsAuto-check: notes
  • Silk Profiler

    baserow/baserow

    Investigate backend performance using Django Silk profiling data.

    6.1k GitHub stars~2.9k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Arch Wiki

    ahmedemad3/arch-wiki

    Scans any project codebase for new/changed modules, endpoints, middleware, infrastructure, Docker topologies, SQL queries, or permissions and updates docs/architecture/architecture.json.

    250 GitHub stars~5.1k tokensUpdated 21 days ago
    Backend & APIsAuto-check passed
  • Run Tests

    netboxlabs/netbox-branching

    Run the netboxbranching plugin's Django test suite against a local NetBox checkout.

    155 GitHub stars~1.2k tokensUpdated 2 days ago
    Backend & APIsAuto-check passed
  • Add or change a CLIST Django management command, including arguments, resource selection, EventLog monitoring, or cron and Healthchecks wiring.

    439 GitHub stars~848 tokensUpdated 6 days ago
    Backend & APIsAuto-check passed

More from fossasia/eventyay

All 21 skills in this repo
  • Stripe Projects

    fossasia/eventyay

    A skill your agent uses when the user wants to provision infrastructure or third-party services using Stripe Projects.

    1.7k GitHub starsUsed in 5 repos~2k tokens
    Auto-check: notes
  • Stripe Apps

    fossasia/eventyay

    A skill your agent uses when building, modifying, or reviewing a Stripe App — or when the user describes something that implies one (e.g.

    1.7k GitHub starsUsed in 1 repo~3.6k tokens
    Auto-check passed
  • Connect Recommend

    fossasia/eventyay

    A skill your agent uses when the user asks about Stripe Connect configuration, charge patterns, Dashboard access, or how to get started with Connect, is building a marketplace, platform…

    1.7k GitHub starsUsed in 1 repo~5.9k tokens
    Auto-check: warnings
  • Django Run Locally

    fossasia/eventyay

    Steps for initiating the Django development server without Docker

    1.7k GitHub stars~411 tokensUpdated today
    Auto-check passed
  • Docker Deployment

    fossasia/eventyay

    Docker Compose, container services, deployment. An agent skill from fossasia/eventyay.

    1.7k GitHub stars~574 tokensUpdated today
    Auto-check: notes
  • Stripe Best Practices

    fossasia/eventyay

    Guides Stripe integration decisions across development and test environment planning (separate sandboxes vs the shared test mode sandbox), API selection (Checkout Sessions vs PaymentIntents)…

    1.7k GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed

Works with

Categories

Questions about Django Run Migrations

What does Django Run Migrations do?

Steps for generating and applying Django migrations. An agent skill from fossasia/eventyay. Django Run Migrations is an agent skill from fossasia/eventyay.

When should I use Django Run Migrations?

Django Run Migrations fits situations like: tasks that involve Backend development.

How do I install Django Run Migrations in Claude Code?

Run `npx skills add fossasia/eventyay --skill django-run-migrations -a claude-code`. Or copy the skill folder (.agents/skills/django-run-migrations in fossasia/eventyay) into .claude/skills/django-run-migrations in your project. Claude Code loads it when a task matches its description.

How do I install Django Run Migrations in Codex?

Run `npx skills add fossasia/eventyay --skill django-run-migrations -a codex`. Or copy the skill folder (.agents/skills/django-run-migrations in fossasia/eventyay) into .agents/skills/django-run-migrations in your project. Codex loads it when a task matches its description.

Can I use Django Run 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 fossasia/eventyay --skill django-run-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/django-run-migrations, .gemini/skills/django-run-migrations, .github/skills/django-run-migrations and .opencode/skills/django-run-migrations in your project.

What does Django Run Migrations need to run?

Going by SKILL.md and its folder, Django Run Migrations needs the command-line tools its instructions call (python). Our summary lists: Python 3.

Does Django Run 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 Django Run 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 Django Run Migrations use?

Django Run 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 Django Run Migrations use?

About 433 tokens (SKILL.md is roughly 1.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 141 tokens, read only when the agent opens those files.

What are the alternatives to Django Run Migrations?

Skills that share tags, products or a category with Django Run Migrations: Saleor Django Schema Migration (saleor/saleor, 23k stars), Django Access Review (getsentry/skills, 1k stars), Silk Profiler (baserow/baserow, 6.1k stars) and Arch Wiki (ahmedemad3/arch-wiki, 250 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Django Run Migrations?

fossasia (a GitHub organization) maintains it in fossasia/eventyay, which has 1,701 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 11, 2026.

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