removing-packages

Remove software packages and associated BuildStream elements from the Bluefin image.

134|27|Updated Nov 16, 2025

Search Tags:#dependency management #system configuration #buildstream #package removal #bluefin os #element deletion

Ready to run

npx skills add https://github.com/projectbluefin/dakota --skill removing-packages

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: removing-packages
Source: https://github.com/projectbluefin/dakota/tree/main/.opencode/skills/removing-packages
Command: npx skills add https://github.com/projectbluefin/dakota --skill removing-packages

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a systematic process to safely remove software packages and their associated configurations from the Bluefin operating system image, preventing build failures and orphaned components.

Core Features & Use Cases

Guided Package Removal: A step-by-step checklist ensures all related files, dependencies, and configurations are addressed.
Dependency Management: Identifies and helps resolve reverse dependencies to maintain build integrity.
Use Case: When a specific software package is no longer needed or is being replaced, this Skill guides you through the complete removal process, from deleting element files to cleaning up patches and workflow configurations.

Quick Start

Use the removing-packages skill to remove the 'example-package' from the Bluefin image.

Frequently Asked Questions about removing-packages

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I safely remove packages from a Bluefin OS image without breaking the build?▼

Safely removing packages from a Bluefin OS image requires a systematic checklist covering element file deletion, reverse dependency checks, source alias cleanup, and Renovate configuration updates to prevent build failures and orphaned components.

What is the process for deleting BuildStream elements during package removal?▼

Deleting BuildStream elements involves identifying specific element files, resolving reverse dependencies, updating dependency stacks, and cleaning associated static files and patches to maintain system configuration integrity.

What steps are needed to clean up source aliases and Renovate configurations after removing software?▼

Cleaning up source aliases and tracking Renovate configurations after software removal ensures no orphaned references remain in the build system, preventing future build errors and maintaining dependency management accuracy.

Can I use this package removal process for any software in the Bluefin image?▼

This package removal process applies to any software being replaced or no longer needed in the Bluefin image, guiding complete removal from deleting element files to resolving reverse dependencies and workflow configurations.

What happens if I don't check reverse dependencies before removing a package from Bluefin?▼

Failing to check reverse dependencies before package removal breaks build integrity, as other BuildStream elements may rely on the removed software, leading to orphaned components and failed builds.