
Capacitor Plugin Upgrade V6 To V7
- 362 installs
- 57 repo stars
- Updated July 13, 2026
- cap-go/capgo-skills
capacitor-plugin-upgrade-v6-to-v7 is an agent skill that walks developers through upgrading a Capacitor plugin from v6 to v7 APIs without breaking native compile steps or runtime bridge calls.
About
capacitor-plugin-upgrade-v6-to-v7 is a Capgo-maintained Claude skill for maintainers of Capacitor plugins—not full app upgrades—who must move `@capacitor/*` peer dependencies and native projects from v6 to v7. The skill injects a live `package.json` snapshot, locates `example-app`, `ios`, and `android` paths, and follows a 6-step procedure: confirm peer ranges, apply v7 migration notes, update the example app, run `npm install`, sync, and verify builds. It explicitly scopes out non-Capacitor plugins and other major versions. Use it when a plugin still targets Capacitor 6 and CI or local builds fail after bumping Capacitor core to 7.
- v6-to-v7 Capacitor plugin breaking changes
- Native project and Gradle/Xcode alignment steps
- TypeScript import and method signature updates
- Third-party plugin replacement or fork guidance
- Build, device test, and rollback checklist
Capacitor Plugin Upgrade V6 To V7 by the numbers
- 362 all-time installs (skills.sh)
- Ranked #350 of 1,039 Mobile Development skills by installs in the Skillselion catalog
- Data as of Aug 1, 2026 (Skillselion catalog sync)
npx skills add https://github.com/cap-go/capgo-skills --skill capacitor-plugin-upgrade-v6-to-v7Add your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 362 |
|---|---|
| repo stars | ★ 57 |
| Last updated | July 13, 2026 |
| Repository | cap-go/capgo-skills ↗ |
How do you migrate a Capacitor plugin from v6 to v7?
Upgrade Capacitor plugins and app dependencies from v6 to v7 APIs without breaking native compile or runtime bridge calls.
Who is it for?
Capacitor plugin maintainers bumping `@capacitor/core` and native bridge code from v6 to v7 with agent-guided checks.
Skip if: Full Capacitor app upgrades, non-Capacitor npm packages, or jumps to Capacitor versions other than 6→7.
When should I use this skill?
The user says their Capacitor plugin targets v6 and must migrate to v7, or native iOS/Android builds break after a Capacitor 7 bump.
What you get
Updated package.json peer ranges, migrated native iOS/Android projects, synced example app, and verified Capacitor 7 compile/runtime bridge.
- updated package.json
- migrated native projects
- verified example-app build
By the numbers
- Follows a documented 6-step v6→v7 migration procedure
- Allowed tools include Bash node snapshots and find for native paths
Files
Capacitor Plugin Upgrade v6 to v7
Upgrade a Capacitor plugin from version 6 to version 7.
When to Use This Skill
- User says the plugin targets Capacitor 6 and must move to v7
- User wants the exact v6 to v7 migration path
- User needs v7-specific native and package updates
Live Project Snapshot
Plugin and Capacitor package snapshot: !node -e "const fs=require('fs');if(!fs.existsSync('package.json'))process.exit(0);const pkg=JSON.parse(fs.readFileSync('package.json','utf8'));const out=['package.name='+(pkg.name||''),'package.version='+(pkg.version||'')];for(const section of ['peerDependencies','dependencies','devDependencies']){for(const [name,version] of Object.entries(pkg[section]||{})){if(name.startsWith('@capacitor/'))out.push(section+'.'+name+'='+version)}}console.log(out.join('\n'))"
Example and native project paths: !find . -maxdepth 3 \( -path './example-app' -o -path './ios' -o -path './android' \)
Procedure
1. Start from the injected snapshot and confirm the current Capacitor peer dependency range in package.json. 2. Update the peer dependency range to Capacitor 7. 3. Review the v6 to v7 migration notes before editing native files. 4. Update the example app if it exists. 5. Run npm install. 6. Sync and verify the example or test app.
Error Handling
- If the example app breaks, fix the plugin API or native bridge before moving on.
- If iOS fails, verify the deployment target for Capacitor 7.
- If Android fails, verify the Gradle and Java requirements for Capacitor 7.
{
"version": "1.0.0",
"organization": "Capgo",
"date": "March 2026",
"abstract": "Version-specific guide for upgrading a Capacitor plugin from v6 to v7.",
"triggers": [
"capacitor plugin 6 to 7",
"upgrade plugin to capacitor 7",
"v6 to v7 plugin migration",
"capacitor plugin upgrade v7"
],
"references": [
"https://capacitorjs.com/docs"
]
}
Related skills
How it compares
Use this skill for plugin-package v6→v7 migrations; use Capacitor official app migration guides when upgrading an entire consumer app rather than a publishable plugin.
FAQ
Does capacitor-plugin-upgrade-v6-to-v7 upgrade full Capacitor apps?
No. capacitor-plugin-upgrade-v6-to-v7 targets Capacitor plugin repositories only. The skill description explicitly excludes app-wide upgrades, other major Capacitor versions, and non-Capacitor packages.
What files does the Capacitor v6 to v7 skill inspect first?
capacitor-plugin-upgrade-v6-to-v7 runs a Node snapshot of package.json for `@capacitor/*` peer, dependency, and devDependency ranges, then searches for `./example-app`, `./ios`, and `./android` paths before editing native projects.