deepgram-python-maintaining-sdk

Name: deepgram-python-maintaining-sdk
Availability: InStock
Author: Deepgram

Regenerate Fern-based Python SDKs and reconcile manual patches.

456|139|Updated May 12, 2021

Search Tags:#documentation #python-sdk #regeneration #patch-management #sdk-maintenance #fern #freeze-classification

Ready to run

npx skills add https://github.com/deepgram/deepgram-python-sdk --skill deepgram-python-maintaining-sdk

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deepgram-python-maintaining-sdk
Source: https://github.com/deepgram/deepgram-python-sdk/tree/main/.agents/skills/deepgram-python-maintaining-sdk
Command: npx skills add https://github.com/deepgram/deepgram-python-sdk --skill deepgram-python-maintaining-sdk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured workflow to maintain Fern-generated Python SDKs, enabling regeneration, patch reconciliation, and proper handling of freeze status decisions to keep the repository aligned with generator outputs.

Core Features & Use Cases

Automates the Fern-based SDK regeneration process and applies patch strategies to ensure manual edits are preserved where needed.
Documents and enforces the repository’s regeneration workflow, including .fernignore management, unfreeze/reapply patches, and generator releases.
Use cases include preparing for a new Fern release, reconciling diffs after regen, and classifying files as permanently or temporarily frozen.

Quick Start

Regenerate the Deepgram Python SDK with Fern for the repository, review diffs, and re-apply or adjust patches while updating .fernignore as needed.

Frequently Asked Questions about deepgram-python-maintaining-sdk

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

FAQPage Schema

How do I regenerate a Fern Python SDK without losing manual patches?▼

To regenerate a Fern Python SDK without losing manual patches, run the regeneration workflow and reapply patch rules guided by the .fernignore file to preserve manual edits in the generated codebase.

What is .fernignore used for in SDK maintenance?▼

The .fernignore file is used during Fern SDK regeneration to classify files as permanently or temporarily frozen, ensuring manual patches survive regeneration and maintaining a clean repository.

How do I reconcile diffs after a new Fern generator release?▼

Reconciling diffs after a Fern generator release involves reviewing the changes, re-applying or adjusting patches, and updating .fernignore rules to ensure deterministic releases and compatibility with the developer workflow.

When do I need to use a Fern-based SDK regeneration workflow?▼

You need a Fern-based SDK regeneration workflow when preparing for a new Fern release, reconciling codebase diffs after regeneration, or managing freeze status decisions for generated files.

Can I use this patch management workflow for non-Fern generated SDKs?▼

This patch management workflow applies specifically to Fern-driven Python SDKs where most files are generated and manual patches must survive regeneration through guided patch rules and freeze classification.

Why are my manual edits disappearing after regenerating my Python SDK?▼

Manual edits disappear after Python SDK regeneration when patch rules and .fernignore configurations are not properly applied, requiring structured patch reconciliation to preserve frozen files during the generation process.