dable-encrypt

Generate database encryption changes from JIRA tickets and create pull requests.

Updated Sep 12, 2023
One-click install
npx skills add https://github.com/byunghak-dable/.dotfiles --skill dable-encrypt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dable-encrypt
Source: https://github.com/byunghak-dable/.dotfiles/tree/main/claude/.claude/skills/dable-encrypt
Command: npx skills add https://github.com/byunghak-dable/.dotfiles --skill dable-encrypt

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the complex process of encrypting database columns, ensuring data privacy and compliance with security standards.

Core Features & Use Cases

  • End-to-End Encryption Workflow: Manages the entire lifecycle from JIRA ticket parsing to DDL updates and code modifications.
  • Automated Code Changes: Integrates with GitHub to create pull requests for schema and application code updates.
  • Use Case: Encrypting sensitive user data like email addresses or personal identifiable information (PII) in a production database with minimal downtime and risk.

Quick Start

Initiate the encryption process for JIRA ticket 'PROJ-123' by running the dable-encrypt skill with the ticket ID.

Frequently Asked Questions about dable-encrypt

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

FAQPage Schema
How do I automate database column encryption from a JIRA ticket?

Database column encryption is automated by parsing a JIRA ticket ID to generate DDL, create db-cipher code modifications, and open a GitHub pull request for schema and application updates. This handles the full lifecycle from ticket to deployment.

Can I encrypt partial JSON fields in a database column or does it only support full column encryption?

Partial JSON field encryption is supported alongside full column encryption. The automation processes both encryption types by generating the necessary DDL updates and db-cipher modifications for the specific fields defined in the JIRA ticket.

What's the best way to manage DDL changes and code modifications for encrypting PII?

Managing DDL changes for encrypting PII is handled by parsing JIRA tickets, performing dependency analysis, generating migration scripts, and creating pull requests against specified GitHub repositories to ensure data privacy compliance with minimal risk.

Does this encryption workflow require manual dependency analysis before generating migration scripts?

Manual dependency analysis is not required before generating migration scripts. The encryption workflow automatically performs dependency analysis and generates the necessary migration scripting as part of the end-to-end process from JIRA ticket parsing to pull request creation.

When should I not use an automated JIRA-driven approach for database encryption?

An automated JIRA-driven approach for database encryption should be avoided when your project does not use GitHub for pull requests or lacks a JIRA ticketing system, as the workflow depends on parsing specific ticket IDs and committing code changes to repositories.