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

Frappe Ops Upgrades

by Impertio-Studio in Impertio-Studio/Frappe_Claude_Skill_Package

A skill your agent uses when upgrading Frappe/ERPNext between major versions (v14 to v15, v15 to v16), troubleshooting failed migrations, or planning rollback.

MITAuto-check: notesDevelopment

Install Frappe Ops Upgrades

skills CLI
$ npx skills add Impertio-Studio/Frappe_Claude_Skill_Package --skill frappe-ops-upgrades -a claude-code

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

GitHub CLI
$ gh skill install Impertio-Studio/Frappe_Claude_Skill_Package frappe-ops-upgrades --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/Impertio-Studio/Frappe_Claude_Skill_Package.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/source/ops/frappe-ops-upgrades .claude/skills/frappe-ops-upgrades && 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
frappe-ops-upgrades
GitHub stars
189
Token cost
~3.3k tokens
SKILL.md length
1,035 words
Files
6 (incl. references)
Skills in repo
61
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when upgrading Frappe/ERPNext between major versions (v14 to v15, v15 to v16), troubleshooting failed migrations, or planning rollback.

  • Works in 8 steps: Full backup — bench --site mysite backup… → Test on staging — Clone production to a… → Check breaking changes — Review the… → …
  • Upgrading Frappe/ERPNext between major versions (v14 to v15
  • SKILL.md covers Quick Reference: Upgrade…, Decision Tree: Upgrade Strategy, Pre-Upgrade Checklist and Standard Upgrade Process, plus 5 more sections
  • Calls git, pip and yarn

What it does

Frappe Ops Upgrades is an agent skill from Impertio-Studio/Frappe_Claude_Skill_Package. Use when upgrading Frappe/ERPNext between major versions (v14 to v15, v15 to v16), troubleshooting failed migrations, or planning rollback. Prevents broken upgrades from skipped patches, incompatible customizations, and missing pre-upgrade checks. Covers version upgrade paths, bench update, migrate command, patch troubleshooting, rollback procedures, breaking changes per version. Keywords: upgrade, migration, v14, v15, v16, bench update, bench migrate, rollback, patches, breaking changes, update failed, bench…

Its SKILL.md is about 3.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `references/anti-patterns.md`, `references/breaking-changes.md` and `references/examples.md`). Compatibility notes: Claude Code, Claude.ai Projects, Claude API. Frappe v14-v16.

It sits in Development, covering Code migrations. It works with Python. The repository describes itself as: 60 deterministic Claude AI skills for Frappe Framework & ERPNext v14-v16 development and operations. The licence is MIT.

When your agent uses it

  • Upgrading Frappe/ERPNext between major versions (v14 to v15
  • Troubleshooting failed migrations
  • Planning rollback

Example prompts

  • “/frappe-ops-upgrades”

Requirements

  • Python 3
  • Node.js
  • Compatibility (from SKILL.md): Claude Code, Claude.ai Projects, Claude API. Frappe v14-v16.

Workflow steps

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

  1. Full backup — bench --site mysite backup --with-files
  2. Test on staging — Clone production to a staging bench and test there first
  3. Check breaking changes — Review the breaking changes section below
  4. Audit custom apps — Run custom apps against new version's API changes
  5. Check Python/Node versions — v15 requires Node 18+; v16 requires Node 24+, Python 3.14+
  6. Disable scheduler — bench --site mysite scheduler disable
  7. Check pending jobs — bench --site mysite ready-for-migration
  8. Read release notes — Check GitHub release notes for each version

What it can do on your machine

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

    • git
    • pip
    • yarn

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

  • Network

    No URLs in SKILL.md. Its commands use git, pip and yarn, which can reach the network depending on how they are called.

    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.

  • Compatibility

    Claude Code, Claude.ai Projects, Claude API. Frappe v14-v16.

    From compatibility in the SKILL.md frontmatter.

Context cost

Frappe Ops Upgrades loads about 3.3k tokens when it runs, and up to ~8.6k if it reads all its reference files. Until then it costs about 152 tokens; SKILL.md has 1,035 words of instructions outside code blocks.

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

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteRuns commands with sudoSKILL.md:274
    bench start  # or: sudo bench restart (production)

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 Impertio-Studio/Frappe_Claude_Skill_Package at commit 36cfa80, republished under its MIT licence (© Impertio-Studio). 1,035 words, ~3,305 tokens.

Download SKILL.mdSave it as .claude/skills/frappe-ops-upgrades/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
frappe-ops-upgrades
description
Use when upgrading Frappe/ERPNext between major versions (v14 to v15, v15 to v16), troubleshooting failed migrations, or planning rollback. Prevents broken upgrades from skipped patches, incompatible customizations, and missing pre-upgrade checks. Covers version upgrade paths, bench update, migrate command, patch troubleshooting, rollback procedures, breaking changes per version. Keywords: upgrade, migration, v14, v15, v16, bench update, bench migrate, rollback, patches, breaking changes, update failed, bench update error, migration error, patches failing, rollback after upgrade..
compatibility
Claude Code, Claude.ai Projects, Claude API. Frappe v14-v16.
license
MIT
metadata.author
OpenAEC-Foundation
metadata.version
2.0

Version Upgrades

Complete guide for upgrading Frappe/ERPNext between major versions, handling failed migrations, and rolling back safely.

Versions: v14 → v15 → v16

Quick Reference: Upgrade Commands

TaskCommand
Full updatebench update
Update specific appbench update --pull --app erpnext
Switch branchbench switch-to-branch version-15 frappe erpnext
Run migrations onlybench --site mysite migrate
Check migration readinessbench --site mysite ready-for-migration
Backup before upgradebench --site mysite backup
Restore from backupbench --site mysite restore /path/to/backup.sql.gz
Re-run failed patchAdd #YYYY-MM-DD suffix in patches.txt

Decision Tree: Upgrade Strategy

Need to upgrade?
├── Single minor version bump (e.g., v15.10 → v15.20)?
│   └── YES → Run `bench update` directly
├── Major version jump (e.g., v14 → v15)?
│   ├── Have custom apps?
│   │   ├── YES → Test on staging FIRST, check breaking changes
│   │   └── NO → Follow standard upgrade path
│   └── Multiple major versions (v14 → v16)?
│       └── ALWAYS upgrade one version at a time: v14 → v15 → v16
└── Production environment?
    ├── YES → ALWAYS test on staging clone first
    └── NO → Proceed with standard upgrade

Pre-Upgrade Checklist

ALWAYS complete these steps before ANY major version upgrade:

  1. Full backup — bench --site mysite backup --with-files
  2. Test on staging — Clone production to a staging bench and test there first
  3. Check breaking changes — Review the breaking changes section below
  4. Audit custom apps — Run custom apps against new version's API changes
  5. Check Python/Node versions — v15 requires Node 18+; v16 requires Node 24+, Python 3.14+
  6. Disable scheduler — bench --site mysite scheduler disable
  7. Check pending jobs — bench --site mysite ready-for-migration
  8. Read release notes — Check GitHub release notes for each version

Standard Upgrade Process

Step-by-Step
bash
# 1. Backup all sites
bench backup-all-sites

# 2. Switch to target version branch
bench switch-to-branch version-15 frappe erpnext

# 3. Update (pulls code, installs deps, builds, migrates)
bench update

# 4. Verify
bench --site mysite migrate  # if not done by update
bench version                # confirm versions
What bench update Executes (In Order)
  1. Backup all sites
  2. Pull latest code for all apps (git pull)
  3. Install Python requirements (pip install)
  4. Install Node requirements (yarn install)
  5. Build static assets (bench build)
  6. Run migrations on all sites (bench migrate)
  7. Restart bench processes

v14 → v15 Breaking Changes

Environment Requirements
Requirementv14v15
Node.jsv14+v18+
Python packagingsetup.pypyproject.toml
Backend Breaking Changes
  • db.set() removed — Use doc.db_set() instead
  • db.sql() parameters removed — as_utf8 and formatted no longer accepted
  • db.set_value() for Singles — Use frappe.db.set_single_value() instead
  • job_name deprecated — Use job_id parameter in enqueue()
  • frappe.new_doc() arguments — parent_doc, parentfield, as_dict MUST be keyword args
  • frappe.get_installed_apps() — No longer accepts sort or frappe_last args
  • Method override order reversed — Last override now takes precedence
  • Timezone functions renamed — convert_utc_to_user_timezone → convert_utc_to_system_timezone
Frontend Breaking Changes
  • Vue 2 → Vue 3 — All Vue components MUST be migrated
  • Window globals removed — get_today → frappe.datetime.get_today, user → frappe.session.user
  • this in Client Scripts — Local scope access no longer supported
  • Image lazy loading — Replace website-image-lazy class with native loading="lazy"
Security Changes
  • Server Scripts disabled by default — Enable: bench set-config -g server_script_enabled 1
  • "Desk User" role added — Replaces "All" role for desk user permissions
  • currentsite.txt removed — Use bench use sitename or FRAPPE_SITE env var
Removed Features
  • Event Streaming moved to separate app
  • Cordova support removed
  • setup.py removed (use pyproject.toml)
  • --make_copy and --restore build flags removed (use --hard-link)

See breaking-changes.md for the complete list.

v15 → v16 Breaking Changes

Environment Requirements
Requirementv15v16
Node.jsv18+v24+
Python3.10+3.14+
Backend Breaking Changes
  • Default sort order changed — creation instead of modified for all list queries
  • has_permission hooks — MUST return explicit True; None no longer accepted
  • frappe.get_doc(doctype, name, field=value) — No longer updates values
  • DB commits in document hooks — No longer allowed to prevent data integrity issues
  • frappe.sendmail(now=True) — No longer commits transactions implicitly
  • db.get_value() for Singles — Now returns proper types instead of strings
  • State-changing methods require POST — /api/method/logout, /api/method/upload_file, etc.
Separated Modules (Install Separately)
  • Energy Points → frappe/eps
  • Newsletter → frappe/newsletter
  • Backup Integrations → frappe/offsite_backups
  • Blog → frappe/blog
Frontend Breaking Changes
  • Report/Dashboard/Page JS evaluated as IIFEs (no global scope pollution)
  • Awesome Bar redesigned, moved to sidebar (Cmd+K)
  • List view right sidebar removed
  • /apps endpoint deprecated; /app reroutes to /desk
Configuration Changes
  • Site config cached for up to one minute (changes not immediate)
  • Country field requires valid ISO 3166 ALPHA-2 code
  • bench version output format changed to "plain" (use -f legacy for old format)
  • override_doctype hook classes MUST inherit from the overridden class

See breaking-changes.md for the complete list.

Patch System

How Patches Work

Patches are one-off data migration scripts that run during bench migrate. They are defined in each app's patches.txt file.

patches.txt Format [v14+]
ini
[pre_model_sync]
# Runs BEFORE schema sync — use for data prep
myapp.patches.v15_0.prepare_data_for_migration

[post_model_sync]
# Runs AFTER schema sync — use for data that needs new schema
myapp.patches.v15_0.migrate_data_to_new_fields
Show full SKILL.md (416 more words)Show less
Patch Execution Rules
  • Patches run in the order defined in patches.txt
  • Each patch runs exactly ONCE — tracked in the __patches table
  • To re-run a patch, append a date comment: myapp.patches.v15_0.fix #2025-03-20
  • One-off statements: execute:frappe.delete_doc('Page', 'old_page', ignore_missing=True)
Writing a Patch
python
# myapp/patches/v15_0/migrate_field_data.py
import frappe

def execute():
    # ALWAYS reload if you need the NEW schema
    frappe.reload_doc("module_name", "doctype", "doctype_name")

    # Perform data migration
    frappe.db.sql("""
        UPDATE `tabSales Invoice`
        SET new_field = old_field
        WHERE old_field IS NOT NULL
    """)
Debugging Stuck Patches
bash
# Check which patches have run
bench --site mysite console
>>> frappe.db.sql("SELECT * FROM __patches WHERE patch LIKE '%stuck_patch%'")

# Remove a patch record to force re-run
>>> frappe.db.sql("DELETE FROM __patches WHERE patch = 'myapp.patches.v15_0.broken_patch'")
>>> frappe.db.commit()

# Then re-run migrate
bench --site mysite migrate

Rollback Procedure

Immediate Rollback (Within Hours)
bash
# 1. Stop all processes
bench stop

# 2. Restore database from pre-upgrade backup
bench --site mysite restore /path/to/pre-upgrade-backup.sql.gz \
  --with-public-files /path/to/files.tar \
  --with-private-files /path/to/private-files.tar

# 3. Switch back to previous version branch
bench switch-to-branch version-14 frappe erpnext

# 4. Install old dependencies
bench setup requirements

# 5. Build old assets
bench build

# 6. Start bench
bench start  # or: sudo bench restart (production)
Critical Rules for Rollback
  • ALWAYS keep pre-upgrade backups for at least 7 days
  • NEVER run bench migrate after restoring to old branch — schema is already correct
  • ALWAYS restore files alongside database — file references may break otherwise
  • NEVER attempt rollback after users have created new data on the upgraded version

Frappe Packages: Moving Customizations Between Sites

Frappe Packages (v14+) are lightweight UI-built applications — bundles of Custom Module Defs distributed as .tar.gz tarballs. For Custom Fields, Property Setters, and DocPerms on standard DocTypes, use Fixtures instead.

Quick Reference: Package vs Fixtures vs App
MechanismUse WhenCLI Command
PackageUI-built DocTypes, Scripts, Web PagesUI only (Package Import/Release)
FixturesCustom Fields, Property Setters, DocPermsbench --site mysite export-fixtures
Frappe AppFull development workflow, CI/CD, testsbench get-app, bench install-app
Package Workflow (UI-Based)
  1. Create a Package document → assign Custom Module Defs to it
  2. Create a Package Release → exports to [bench]/sites/[site]/packages/ as [package]-[version].tar.gz
  3. On target site, create Package Import → attach tarball, check Activate
  4. System migrates data like an app migration; use Force to overwrite existing files
Fixtures Workflow (CLI-Based)
python
# hooks.py — define what to export
fixtures = [
    "Custom Field",
    "Property Setter",
    {"dt": "Client Script", "filters": [["module", "=", "My Module"]]}
]
bash
# Export fixtures to JSON in your app
bench --site mysite export-fixtures --app myapp

# Fixtures auto-sync on: bench --site mysite migrate

NEVER use Packages to modify standard/core DocTypes — use a Frappe App with Fixtures.

See frappe-packages.md for the complete reference including decision trees, limitations, and best practices.

Custom App Compatibility Checks

Before upgrading, audit each custom app:

  1. Check deprecated APIs — Search for removed functions listed in breaking changes
  2. Check setup.py — Must migrate to pyproject.toml for v15+
  3. Check Vue components — Must be Vue 3 compatible for v15+
  4. Check patches.txt — Ensure patches use [pre_model_sync]/[post_model_sync] sections [v14+]
  5. Check hooks.py — Verify no removed hooks are used
  6. Run tests — bench --site test_site run-tests --app myapp

Decision Tree: In-Place vs Fresh Install

Choosing upgrade strategy:
├── Small site (< 10 GB database)?
│   └── In-place upgrade is usually fine
├── Large site (> 50 GB database)?
│   ├── Many custom apps? → Fresh install + data migration
│   └── Standard apps only? → In-place with extended downtime window
├── Skipping multiple versions (v13 → v15)?
│   └── ALWAYS fresh install — sequential upgrades are too risky
└── Critical production with zero-downtime requirement?
    └── Fresh install on parallel server + DNS switch

Version Differences Summary

Featurev14v15v16
Python packagingsetup.pypyproject.tomlpyproject.toml
Vue versionVue 2Vue 3Vue 3
Node.js minimumv14v18v24
Python minimum3.83.103.14
Server ScriptsEnabledDisabled defaultDisabled default
Default sortmodifiedmodifiedcreation
patches.txt sectionsYesYesYes
Workspace sidebarNoNoYes
Separated modules—Event StreamingBlog, Newsletter, EPS

Reference Files

FileContents
examples.mdComplete upgrade workflow examples
anti-patterns.mdCommon upgrade mistakes and fixes
breaking-changes.mdDetailed breaking changes per version
frappe-packages.mdPackages, fixtures, and moving customizations between sites

© Impertio-Studio, MIT. 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 5 other files (references) in skills/source/ops/frappe-ops-upgrades of Impertio-Studio/Frappe_Claude_Skill_Package.

  • SKILL.md
  • references/.gitkeep
  • references/anti-patterns.md
  • references/breaking-changes.md
  • references/examples.md
  • references/frappe-packages.md

Open the folder on GitHubat commit 36cfa80

Compare with similar skills

Frappe Ops Upgrades 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.

Frappe Ops Upgrades compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Frappe Ops Upgrades this skillImpertio-Studio/Frappe_Claude_Skill_Package189—~3.3kAutomated safety check: NotesMIT
jscpd Code Migration Trackerkucherenko/jscpd6.4k—~5kAutomated safety check: PassMIT
RustPython Stdlib UpgradeRustPython/RustPython22k—~876Automated safety check: PassMIT
Code Migrationanthropics/code-migration-kit-with-claude-code748—~983Automated safety check: PassCustom licence
Saleor Port Changessaleor/saleor23k—~969Automated safety check: PassBSD-3-Clause
Ast Grepbanteg/crimson185—~541Automated safety check: PassNone

Similar skills

  • jscpd Code Migration Tracker

    kucherenko/jscpd

    Measures a code port between languages or frameworks with jscpd's function-level comparison, porting tests before code and tracking what is left unmatched.

    6.4k GitHub stars~5k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • RustPython Stdlib Upgrade

    RustPython/RustPython

    Upgrades a Python standard library module from CPython into RustPython with update_lib, then triages and marks the tests that still fail.

    22k GitHub stars~876 tokensUpdated today
    DevelopmentAuto-check passed

  • Code Migration

    anthropics/code-migration-kit-with-claude-code

    Official

    Run a large-scale language migration with the six-step process: create the map and the rules, stress-test the rules, translate everything, compile, run it, match behavior.

    748 GitHub stars~983 tokensUpdated 3 mo ago
    DevelopmentAuto-check passed

  • Saleor Port Changes

    saleor/saleor

    Forward-ports or backports a single PR or branch onto the currently checked-out Saleor branch, handling GraphQL version markers and migration numbering along the way.

    23k GitHub stars~969 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Ast Grep

    banteg/crimson

    Use ast-grep for Python structural code exploration, mechanical codemods, and rule maintenance in this repo.

    185 GitHub stars~541 tokensUpdated today
    DevelopmentAuto-check passed

  • Documenso Upgrade Migration

    jeremylongshore/tons-of-skills-marketplace

    Manage Documenso API version upgrades and SDK migrations. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~1.8k tokensUpdated today
    DevelopmentAuto-check passed

More from Impertio-Studio/Frappe_Claude_Skill_Package

All 61 skills in this repo

  • Frappe Ops Website Deploy

    Impertio-Studio/Frappe_Claude_Skill_Package

    Deploy HTML/CSS websites to ERPNext/Frappe (v15/v16) as Web Pages via the REST API.

    189 GitHub stars~2.5k tokensUpdated 23 days ago
    Auto-check passed

  • Frappe Agent Architect

    Impertio-Studio/Frappe_Claude_Skill_Package

    A skill your agent uses when designing multi-app Frappe architectures, deciding whether to split functionality into separate apps, or implementing cross-app communication patterns.

    189 GitHub stars~2.8k tokensUpdated 23 days ago
    Auto-check passed

  • Frappe Agent Debugger

    Impertio-Studio/Frappe_Claude_Skill_Package

    A skill your agent uses when debugging Frappe errors, using bench console for live inspection, analyzing tracebacks, or reading Frappe log files.

    189 GitHub stars~2.9k tokensUpdated 23 days ago
    Auto-check passed

  • Frappe Agent Interpreter

    Impertio-Studio/Frappe_Claude_Skill_Package

    A skill your agent uses when receiving vague or unclear ERPNext/Frappe development requests that need interpretation.

    189 GitHub stars~3.2k tokensUpdated 23 days ago
    Auto-check passed

  • Frappe Agent Migrator

    Impertio-Studio/Frappe_Claude_Skill_Package

    A skill your agent uses when migrating a Frappe app between major versions, detecting breaking API changes, or resolving post-migration errors.

    189 GitHub stars~2.8k tokensUpdated 23 days ago
    Auto-check: notes

  • Frappe Agent Validator

    Impertio-Studio/Frappe_Claude_Skill_Package

    A skill your agent uses when reviewing or validating Frappe/ERPNext code against best practices and common pitfalls.

    189 GitHub stars~2.8k tokensUpdated 23 days ago
    Auto-check passed

Works with

Categories

Questions about Frappe Ops Upgrades

What does Frappe Ops Upgrades do?

A skill your agent uses when upgrading Frappe/ERPNext between major versions (v14 to v15, v15 to v16), troubleshooting failed migrations, or planning rollback. Frappe Ops Upgrades is an agent skill from Impertio-Studio/Frappe_Claude_Skill_Package. Use when upgrading Frappe/ERPNext between major versions (v14 to v15, v15 to v16), troubleshooting failed migrations, or planning rollback.

When should I use Frappe Ops Upgrades?

Frappe Ops Upgrades fits situations like: upgrading Frappe/ERPNext between major versions (v14 to v15; troubleshooting failed migrations; planning rollback.

How do I install Frappe Ops Upgrades in Claude Code?

Run `npx skills add Impertio-Studio/Frappe_Claude_Skill_Package --skill frappe-ops-upgrades -a claude-code`. Or copy the skill folder (skills/source/ops/frappe-ops-upgrades in Impertio-Studio/Frappe_Claude_Skill_Package) into .claude/skills/frappe-ops-upgrades in your project. Claude Code loads it when a task matches its description.

How do I install Frappe Ops Upgrades in Codex?

Run `npx skills add Impertio-Studio/Frappe_Claude_Skill_Package --skill frappe-ops-upgrades -a codex`. Or copy the skill folder (skills/source/ops/frappe-ops-upgrades in Impertio-Studio/Frappe_Claude_Skill_Package) into .agents/skills/frappe-ops-upgrades in your project. Codex loads it when a task matches its description.

Can I use Frappe Ops Upgrades 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 Impertio-Studio/Frappe_Claude_Skill_Package --skill frappe-ops-upgrades -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/frappe-ops-upgrades, .gemini/skills/frappe-ops-upgrades, .github/skills/frappe-ops-upgrades and .opencode/skills/frappe-ops-upgrades in your project.

What does Frappe Ops Upgrades need to run?

Going by SKILL.md and its folder, Frappe Ops Upgrades needs the command-line tools its instructions call (git, pip and yarn). Our summary lists: Python 3; Node.js. Compatibility (from SKILL.md): Claude Code, Claude.ai Projects, Claude API. Frappe v14-v16..

Does Frappe Ops Upgrades access the network?

SKILL.md contains no URLs. Its commands use git and pip, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Frappe Ops Upgrades safe to install?

Our automated static check of SKILL.md found notes only (runs commands with sudo), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Frappe Ops Upgrades use?

Frappe Ops Upgrades is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Frappe Ops Upgrades use?

About 3.3k tokens (SKILL.md is roughly 13k 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 5.3k tokens, read only when the agent opens those files.

What are the alternatives to Frappe Ops Upgrades?

Skills that share tags, products or a category with Frappe Ops Upgrades: jscpd Code Migration Tracker (kucherenko/jscpd, 6.4k stars), RustPython Stdlib Upgrade (RustPython/RustPython, 22k stars), Code Migration (anthropics/code-migration-kit-with-claude-code, 748 stars) and Saleor Port Changes (saleor/saleor, 23k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Frappe Ops Upgrades?

Impertio-Studio (a GitHub organization) maintains it in Impertio-Studio/Frappe_Claude_Skill_Package, which has 189 GitHub stars. The repository holds 61 skills in this directory. The repository was last updated on September 17, 2026.

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