openspec-apply-change

Automates OpenShift change tasks with CLI-based management and optional smoke testing.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/aditrioka/nearyou-id --skill openspec-apply-change-aditrioka
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/aditrioka/nearyou-id/tree/main/.claude/skills/openspec-apply-change
Command: npx skills add https://github.com/aditrioka/nearyou-id --skill openspec-apply-change-aditrioka

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the implementation of tasks from an OpenSpec change, streamlining the process and reducing manual effort.

Core Features & Use Cases

  • Task Implementation: Automates the selection, status checking, and execution of tasks from an OpenSpec change.
  • Contextual Information: Provides necessary architectural and design context for implementation.
  • Progress Tracking: Tracks and reports the progress of task implementation.
  • Verification and Review: Ensures that all tasks are completed correctly and ready for code review.
  • Smoke Testing: Optionally performs smoke testing for runtime impact changes.
  • Manual Verification: Requires manual verification for UI changes and backend runtime without smoke scripts.

Quick Start

Apply the changes for the 'example-change' by running: /opsx:apply example-change

Frequently Asked Questions about openspec-apply-change

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

FAQPage Schema
How do I automate OpenSpec task implementation for code changes?

Automating OpenSpec task implementation is done by applying a dedicated Skill that handles task selection, status checking, and execution. It streamlines applying code changes by providing architectural context and tracking implementation progress.

Do I need the OpenSpec CLI to automate task execution?

Yes, the OpenSpec CLI is required for task management. The automation Skill depends on the CLI to select, check the status of, and execute tasks defined within an OpenSpec change.

Can I run smoke tests automatically after implementing OpenSpec changes?

Yes, you can optionally perform smoke testing for runtime impact changes automatically. This verifies that backend modifications work correctly before moving to the manual code review phase.

When is manual verification required for OpenSpec task automation?

Manual verification is required for UI changes and backend runtime changes that lack smoke scripts. This ensures visual interfaces and untested backend modifications function correctly before final code review.

What is the best way to track OpenSpec change implementation progress?

Tracking OpenSpec implementation progress is handled automatically by the automation Skill. It reports the status of task execution and provides contextual information to ensure all tasks are ready for code review.