technology-modify

Name: technology-modify
Availability: InStock
Author: oogdz

Automates changes to per-technology coding standards with controlled migration and rollback workflows.

Updated Apr 2, 2026

Search Tags:#rollback #standards #conventions #service #modify #per-tech

Ready to run

npx skills add https://github.com/oogDZ/2 --skill technology-modify

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: technology-modify
Source: https://github.com/oogDZ/2/tree/main/.claude/skills/technology-modify
Command: npx skills add https://github.com/oogDZ/2 --skill technology-modify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates and governs changes to technology-specific coding standards, ensuring consistent adoption across services and teams.

Core Features & Use Cases

Create, update, or rollback per-tech standards for a given technology stack.
Enforce conventions, deactivation of deprecated standards, and service onboarding alignment.
Use Case: When introducing a new tech (e.g., a framework) you add a new standard and migrate existing services with a safe rollback.

Quick Start

Run /technology-modify <tech-name> [--scenario A|B|C|D] to start a standard change workflow.

Frequently Asked Questions about technology-modify

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

FAQPage Schema

How do I update coding standards and conventions across multiple services?▼

You update coding standards across multiple services by applying per-tech conventions through a controlled workflow that enforces consistent adoption and alignment.

What is the safest way to rollback per-tech standards after a failed migration?▼

Rolling back per-tech standards is handled through a controlled workflow with explicit safeguards and deprecation handling. This ensures safe reversion of convention changes across affected services.

How do I onboard a new service to existing technology conventions?▼

Service onboarding aligns new services with existing per-tech coding standards and conventions. The workflow applies explicit steps to ensure the service adheres to the required technology stack rules.

When should I deactivate or deprecate outdated coding standards?▼

You should deprecate outdated coding standards when they no longer apply to your current technology stack. The workflow handles deactivation safely, ensuring deprecated conventions are removed without breaking existing services.

Can I enforce a new framework standard and migrate existing services safely?▼

Yes, you can enforce a new framework standard and migrate existing services by initiating a standard change workflow. This process includes explicit steps and safeguards to ensure a safe transition with rollback options.