home / skills / partme-ai / full-stack-skills / upgradelink

upgradeLink skill

/skills/upgradeLink

This skill guides upgrade link creation, configuration, and best practices for reliable migrations and seamless system upgrades.

npx playbooks add skill partme-ai/full-stack-skills --skill upgradelink

Review the files below or copy the command above to add this skill to your agents.

Files (4)
SKILL.md
4.1 KB
---
name: upgradeLink
description: Provides comprehensive guidance for upgrade link management including upgrade link creation, configuration, and upgrade link best practices. Use when the user asks about upgrade links, needs to create upgrade links, configure upgrade processes, or manage upgrade links.
license: Complete terms in LICENSE.txt
---

## When to use this skill

Use this skill whenever the user wants to:
- Use UpgradeLink tool for system upgrades
- Understand UpgradeLink features and capabilities
- Perform version migrations
- Configure UpgradeLink settings
- Troubleshoot UpgradeLink issues
- Implement upgrade workflows
- Use UpgradeLink APIs or integrations
- Follow UpgradeLink best practices

## How to use this skill

This skill is organized to match the UpgradeLink official documentation structure (https://www.toolsetlink.com/upgrade/what-is-upgrade.html). When working with UpgradeLink:

1. **Identify the topic** from the user's request:
   - Getting started/快速开始 → `examples/getting-started/introduction.md` or `examples/getting-started/basic-usage.md`
   - Features/功能特性 → `examples/features/` directory
   - Advanced usage/高级用法 → `examples/advanced/` directory

2. **Load the appropriate example file** from the `examples/` directory:

   **Getting Started (快速开始) - `examples/getting-started/`**:
   - `examples/getting-started/introduction.md` - What is UpgradeLink
   - `examples/getting-started/basic-usage.md` - Basic usage examples

   **Features (功能特性) - `examples/features/`**:
   - `examples/features/` - Feature-specific examples

   **Advanced (高级) - `examples/advanced/`**:
   - `examples/advanced/` - Advanced usage examples

3. **Follow the specific instructions** in that example file for syntax, structure, and best practices

   **Important Notes**:
   - All examples follow UpgradeLink official documentation
   - Each example file includes key concepts, code examples, and key points
   - Always check the example file for best practices and common patterns

4. **Reference API documentation** in the `api/` directory when needed:
   - `api/` - API reference documentation

5. **Use templates** from the `templates/` directory:
   - `templates/` - Usage templates


### Doc mapping (one-to-one with official documentation)

- `examples/` → https://www.toolsetlink.com/upgrade/what-is-upgrade.html

## Examples and Templates

This skill includes detailed examples organized to match the official documentation structure. All examples are in the `examples/` directory (see mapping above).

**To use examples:**
- Identify the topic from the user's request
- Load the appropriate example file from the mapping above
- Follow the instructions, syntax, and best practices in that file
- Adapt the code examples to your specific use case

**To use templates:**
- Reference templates in `templates/` directory for common scaffolding
- Adapt templates to your specific needs and coding style

## API Reference

Detailed API documentation is available in the `api/` directory, organized to match the official UpgradeLink API documentation structure.

**To use API reference:**
1. Identify the API you need help with
2. Load the corresponding API file from the `api/` directory
3. Find the API signature, parameters, return type, and examples
4. Reference the linked example files for detailed usage patterns
5. All API files include links to relevant example files in the `examples/` directory

## Best Practices

1. **Follow official documentation**: Always refer to official UpgradeLink documentation
2. **Test upgrades**: Test upgrades in development environment first
3. **Backup data**: Always backup data before performing upgrades
4. **Version compatibility**: Check version compatibility requirements
5. **Error handling**: Implement proper error handling
6. **Logging**: Enable logging for troubleshooting
7. **Documentation**: Document upgrade procedures
8. **Rollback plan**: Have a rollback plan ready

## Resources

- **Official Website**: https://www.toolsetlink.com/
- **Documentation**: https://www.toolsetlink.com/upgrade/what-is-upgrade.html

## Keywords

UpgradeLink, upgrade, migration, version, toolsetlink, 升级, 迁移, 版本

Overview

This skill provides comprehensive guidance for managing upgrade links, including creation, configuration, testing, and operational best practices. It helps teams design safe upgrade workflows, integrate upgrade APIs, and handle version migrations with minimal downtime. Use it to standardize upgrade procedures and reduce upgrade-related risk.

How this skill works

The skill inspects upgrade requirements, maps source and target versions, and recommends concrete steps to create and configure upgrade links. It explains how to invoke upgrade APIs, set configuration options, and integrate upgrade steps into CI/CD pipelines. It also highlights testing, logging, rollback, and monitoring strategies for safe execution.

When to use it

  • Creating a new upgrade link for a product or component
  • Configuring upgrade behavior and rollout options
  • Designing or reviewing upgrade workflows and automation
  • Troubleshooting upgrade failures or migration issues
  • Preparing version compatibility checks and pre-upgrade validations
  • Integrating upgrade APIs into deployment pipelines

Best practices

  • Always test upgrades in an isolated development or staging environment before production
  • Perform full backups and verify restore processes prior to any upgrade
  • Validate version compatibility and run pre-upgrade health checks
  • Enable detailed logging and metrics for each upgrade step to ease troubleshooting
  • Design and document rollback plans and automated recovery steps
  • Use phased or canary rollouts to reduce blast radius and monitor for regressions

Example use cases

  • Create an upgrade link that migrates database schema and application code in two coordinated steps
  • Configure automated pre-checks that validate compatibility and free disk space before starting an upgrade
  • Integrate upgrade API calls into CI/CD to trigger staged rollouts after passing tests
  • Troubleshoot a failed upgrade by analyzing logs, reverting to backup, and replaying the upgrade in a test environment
  • Design a rollback plan that toggles traffic and restores previous artifacts when a post-upgrade issue is detected

FAQ

What should I check before creating an upgrade link?

Confirm target and source versions, verify compatibility matrices, ensure backups exist, and run environment health checks.

How do I minimize downtime during upgrades?

Use phased rollouts, canary deployments, database migrations designed for backward compatibility, and schedule during low-traffic windows.

When should I implement automated rollbacks?

Implement automated rollback when failure thresholds are met during a staged rollout or when critical health checks fail after deployment.