CommunityEscrita e Ediçãogithub.com

Jamie-BitFlight/data-transformation

Use when modifying, converting, or transforming structured data with dasel v3 — in-place mutations, format conversion, batch operations, array manipulation, object construction, and merge patterns across JSON, YAML, TOML, XML, CSV, HCL, INI

O que é data-transformation?

data-transformation is a Claude Code agent skill that use when modifying, converting, or transforming structured data with dasel v3 — in-place mutations, format conversion, batch operations, array manipulation, object construction, and merge patterns across JSON, YAML, TOML, XML, CSV, HCL, INI.

Funciona com~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/Jamie-BitFlight/claude_skills/tree/main/plugins/dasel/skills/data-transformation

Installed? Explore more Escrita e Edição skills: steipete/notion, obra/writing-skills, obra/executing-plans · View all 6 →

Perguntar na sua IA favorita

Abre um novo chat com esta habilidade de agente já pré-carregada.

Documentação

Data Transformation with Dasel v3

<when_to_use>

Activate this skill when:

  • Modifying values in config files (YAML, TOML, JSON, XML, HCL, INI)
  • Converting between data formats (JSON to YAML, TOML to JSON, etc.)
  • Batch-updating array elements (prices, versions, flags)
  • Appending, removing, or reshaping data structures
  • Merging objects or constructing new structures from existing data

</when_to_use>

Safety Rules

NEVER redirect output to the same input file. This truncates the file before dasel reads it, resulting in data loss:

# WRONG — destroys input
cat config.yaml | dasel -i yaml --root 'port = 9090' > config.yaml

# CORRECT — write to temp, then rename
cat config.yaml | dasel -i yaml --root 'port = 9090' > config_tmp.yaml && mv config_tmp.yaml config.yaml

Always verify before overwriting. Preview the transformation output first, then redirect:

# Preview
cat config.yaml | dasel -i yaml --root 'server.port = 9090'
# Apply
cat config.yaml | dasel -i yaml --root 'server.port = 9090' > config_tmp.yaml && mv config_tmp.yaml config.yaml

Core Modification Syntax

In dasel v3, put and delete subcommands do not exist. All modifications use assignment expressions with --root to output the full document.

Set a Value

# Output full document with one field changed
cat config.yaml | dasel -i yaml --root 'server.port = 9090'

# Numeric, boolean, and string assignments
echo '{"count": 1}' | dasel -i json --root 'count = 42'
echo '{"enabled": false}' | dasel -i json --root 'enabled = true'
echo '{"name": "old"}' | dasel -i json --root 'name = "new"'

Set Nested Values

cat config.yaml | dasel -i yaml --root 'database.connection.host = "db.example.com"'
cat config.yaml | dasel -i yaml --root 'database.connection.port = 5432'

In-Place Modification (Safe Pattern)

# Single field update
cat config.yaml | dasel -i yaml --root 'server.port = 9090' > config_tmp.yaml && mv config_tmp.yaml config.yaml

# Multiple fields — chain with semicolons
cat config.yaml | dasel -i yaml --root 'server.port = 9090; server.host = "0.0.0.0"' > config_tmp.yaml && mv config_tmp.yaml config.yaml

Format Conversion

Pipe through dasel with different input/output format flags:

# JSON to YAML
cat data.json | dasel -i json -o yaml > data.yaml

# YAML to TOML
cat config.yaml | dasel -i yaml -o toml > config.toml

# JSON to XML
cat data.json | dasel -i json -o xml > data.xml

# TOML to JSON
cat config.toml | dasel -i toml -o json > config.json

# CSV to JSON
cat data.csv | dasel -i csv -o json > data.json

Array Operations

Append to Array

# Add element to end of array
echo '[1,2,3]' | dasel -i json --root '[$this..., 4]'
# Output: [1, 2, 3, 4]

# Append object to array
cat data.json | dasel -i json --root 'items = [$root.items..., {"name": "new", "value": 42}]'

Batch Update with each

# Multiply all prices by 1.1 (10% increase)
cat data.json | dasel -i json --root 'items.each(price = price * 1.1)'

# Set a flag on all elements
cat data.json | dasel -i json --root 'users.each(active = true)'

# Increment all values
echo '[1,2,3]' | dasel -i json --root 'each($this = $this + 1)'

Filter Then Transform

# Get only active users, then extract names
cat data.json | dasel -i json 'users.filter(active == true).map(name)'

Object Operations

Merge via Spread

# Add new key to existing object
cat base.json | dasel -i json --root '{ $root..., "newKey": "value" }'

# Merge two objects
cat base.json | dasel -i json --root '{ $root..., "extra": true, "version": 2 }'

Field Deletion via Reconstruction

Since v3 has no delete command, remove fields by constructing a new object with only the desired keys:

# Keep only "name" and "email", drop everything else
echo '{"name":"a","email":"b","password":"c"}' | dasel -i json --root '{ name, email }'

Field Rename via Reconstruction

echo '{"old_name": "value"}' | dasel -i json --root '{ "new_name": old_name }'

Multi-Step Transformations

Use variable assignment and semicolons for complex operations:

# Store intermediate result in variable, then transform
cat data.json | dasel -i json '$active = users.filter(active == true); $active.map(name)'

# Multiple variables
cat data.json | dasel -i json '$a = items.filter(price > 100); $b = $a.map(name); $b'

Conditional Transformation

# Set value based on condition
cat data.json | dasel -i json --root 'if(count > 5) { status = "many" } else { status = "few" }'

Transformation Patterns

For detailed per-use-case transformation patterns (config updates, batch processing, format migration, data reshaping, error handling), see Transformation Patterns.

References

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

Jamie-BitFlight/agentskill-kaizen-meta-docs

Agentskill kaizen plugin documentation index. Load when needing to read about cross-platform notes, improvement plans, or DuckDB integration.

Jamie-BitFlight/bash-51-features

Bash 5.1 release features and improvements with practical examples. Use when working with Bash 5.1 features, epoch time variables, redirection enhancements, or when user asks about Bash 5.1 changes, new features, or version-specific capabilities.

Jamie-BitFlight/bash-52-features

Bash 5.2 release features and improvements with practical examples. Use when working with Bash 5.2 features, variable handling enhancements, readline improvements, or when user asks about Bash 5.2 changes, new features, or version-specific capabilities.

Jamie-BitFlight/bash-53-features

Bash 5.3 release features and improvements with practical examples. Use when working with Bash 5.3 features, new command substitution, GLOBSORT, loadable builtins, or when user asks about Bash 5.3 changes, new features, or version-specific capabilities.

Jamie-BitFlight/bash-development

This skill should be used when the user asks to "write a bash script", "create a shell script", "implement bash function", "parse arguments in bash", "handle errors in bash", or mentions bash development, shell scripting, script templates, or modern bash patterns.

Jamie-BitFlight/bash-lint

This skill should be used when the user asks to "lint bash script", "run shellcheck", "format shell script", "use shfmt", "fix shellcheck errors", or mentions shell script linting, formatting, code quality, or pre-commit hooks for bash.

Jamie-BitFlight/bash-logging

This skill should be used when the user asks to "add logging to bash script", "colorize output", "implement log levels", "CI/CD sections", "terminal colors in bash", or mentions logging functions, emoji output, collapsible CI sections, or shlocksmith.

Jamie-BitFlight/bash-portability

This skill should be used when the user asks about "POSIX compatibility", "portable shell scripts", "cross-shell compatibility", "bashisms", "shebang selection", or mentions writing scripts that work on different shells (bash, sh, dash, zsh) or different systems.

Jamie-BitFlight/bash-testing

This skill should be used when the user asks to "test bash script", "write shell tests", "use shunit2", "use shellspec", "create test suite for bash", or mentions unit testing, test frameworks, mocking, or test-driven development for shell scripts.

Jamie-BitFlight/brainstorming-skill

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or when users request help with ideation, marketing, and strategic planning. Explores user intent, requirements, and design before implementation using research-validated prompt patterns.

Jamie-BitFlight/clang-format

Configure clang-format code formatting. Use when: user mentions clang-format or .clang-format, analyzing code style/patterns, creating/modifying formatting config, troubleshooting formatting, brace styles/indentation/spacing/alignment/pointer alignment, or codifying conventions.

Jamie-BitFlight/commitlint

When setting up commit message validation for a project. When project has commitlint.config.js or .commitlintrc files. When configuring CI/CD to enforce commit format. When extracting commit rules for LLM prompt generation. When debugging commit message rejection errors.

Jamie-BitFlight/conventional-commits

When writing a git commit message. When task completes and changes need committing. When project uses semantic-release, commitizen, git-cliff. When choosing between feat/fix/chore/docs types. When indicating breaking changes. When generating changelogs from commit history.

Jamie-BitFlight/dasel-reference

Use when querying, modifying, or converting JSON, YAML, TOML, XML, CSV, HCL, or INI with dasel v3. Complete reference for selectors, functions, conditionals, variables, spread operator, type casting, and format-specific patterns.

Jamie-BitFlight/data-exploration

Use when exploring unknown structured data files with dasel v3 — discover schema, list keys, find nested values, sample arrays, identify data types across JSON, YAML, TOML, XML, CSV, HCL, INI formats

Jamie-BitFlight/delegate

Decompose substantive work into phases, dispatch each phase to a sub-agent, and adjudicate what comes back. Use whenever a request asks for implementation, investigation, a fix, a review, or any change to files — including small ones — and whenever you are about to read source or run a diagnostic yourself instead of handing it off. Also use when a report from a sub-agent needs judging, when a phase needs re-dispatching, or when a user names one instance of a pattern. Does not apply when your own prompt begins "Your ROLE_TYPE is sub-agent." — then follow references/sub-agent-contract.md instead.

Jamie-BitFlight/enterprise-hibernate-hbm

Dasel v3 query patterns for Hibernate .hbm.xml mapping files — entity-table binding, Java property-to-column extraction, one-to-many set/list/bag relationship tracing, many-to-one foreign key discovery, batch scanning across 60+ HBM files. Use when querying Hibernate ORM class mappings, extracting schema metadata from Java persistence layer, or auditing entity-column relationships in enterprise legacy codebases.

Jamie-BitFlight/enterprise-installanywhere

Dasel v3 query patterns for InstallAnywhere .iap_xml installer definitions — use when querying action sequences, discovering variables, resolving platform conditions, navigating panels, or comparing installer variants. Files are 2.5+ MB, 65,000+ lines — too large for context reads, requires structural dasel queries.

Jamie-BitFlight/enterprise-maven-pom

Dasel v3 selector patterns for Maven POM XML files — use when querying dependency versions, filtering by groupId or scope, extracting module hierarchy from parent POMs, or detecting version conflicts across enterprise multi-module Java projects. Load this skill when working with pom.xml files using dasel.

Jamie-BitFlight/enterprise-spring-xml

Dasel v3 selectors for Spring bean factory XML — use when querying any Spring ApplicationContext XML for bean discovery, dependency wiring, JMS destination mapping, property injection extraction, or cross-bean reference tracing. Load this skill before writing dasel selectors against Spring bean XML files (applicationContext.xml, *_beans.xml, spring-*.xml).

Habilidades Relacionadas