Community写作与编辑github.com

Jamie-BitFlight/data-transformation

当需要使用 dasel v3 修改、转换或变换结构化数据时使用——包括原地修改、格式转换、批量操作、数组操作、对象构建以及 JSON、YAML、TOML、XML、CSV、HCL、INI 间的合并模式

data-transformation 是什么?

该技能提供了一套使用 dasel v3 进行结构化数据转换的完整工作流。它涵盖了原地修改、格式间转换(如 JSON 转 YAML、YAML 转 TOML)、数组追加与批量更新、对象合并与重组,以及条件转换等典型场景。Dasel v3 不再使用 `put` 和 `delete` 子命令,所有修改均通过赋值表达式与 `--root` 输出完整文档的方式实现。该技能适用于通过管道处理的命令行环境,并强制要求安全写入模式——将输出写入临时文件再重命名,以避免因重定向到同一输入文件而导致的数据丢失。

兼容平台~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 写作与编辑 skills: steipete/notion, langchain-ai/langchain, bytedance/podcast-generation · View all 6 →

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

文档

使用 Dasel v3 进行数据转换

<when_to_use>

当以下情况时激活此技能:

  • 修改配置文件中的值(YAML, TOML, JSON, XML, HCL, INI)
  • 在数据格式之间转换(JSON 转 YAML, TOML 转 JSON 等)
  • 批量更新数组元素(价格、版本、标志)
  • 追加、移除或重塑数据结构
  • 合并对象或从现有数据中构建新结构

</when_to_use>

安全规则

绝对不要将输出重定向到同一个输入文件。 这会在 dasel 读取之前截断文件,导致数据丢失:

# 错误——会破坏输入
cat config.yaml | dasel -i yaml --root 'port = 9090' > config.yaml

# 正确——先写入临时文件,然后重命名
cat config.yaml | dasel -i yaml --root 'port = 9090' > config_tmp.yaml && mv config_tmp.yaml config.yaml

覆盖前务必验证。 先预览转换输出,再重定向:

# 预览
cat config.yaml | dasel -i yaml --root 'server.port = 9090'
# 应用
cat config.yaml | dasel -i yaml --root 'server.port = 9090' > config_tmp.yaml && mv config_tmp.yaml config.yaml

核心修改语法

在 dasel v3 中,put 和 delete 子命令已不存在。所有修改都使用带 --root 的赋值表达式来输出完整文档。

设置值

# 输出更改了一个字段的完整文档
cat config.yaml | dasel -i yaml --root 'server.port = 9090'

# 数值、布尔值和字符串赋值
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"'

设置嵌套值

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

原地修改(安全模式)

# 单个字段更新
cat config.yaml | dasel -i yaml --root 'server.port = 9090' > config_tmp.yaml && mv config_tmp.yaml config.yaml

# 多个字段——使用分号链接
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

格式转换

通过管道传递 dasel 并使用不同的输入/输出格式标志:

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

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

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

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

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

数组操作

追加到数组

# 在数组末尾添加元素
echo '[1,2,3]' | dasel -i json --root '[$this..., 4]'
# 输出: [1, 2, 3, 4]

# 向数组追加对象
cat data.json | dasel -i json --root 'items = [$root.items..., {"name": "new", "value": 42}]'

使用 each 批量更新

# 将所有价格乘以 1.1(增加 10%)
cat data.json | dasel -i json --root 'items.each(price = price * 1.1)'

# 为所有元素设置一个标志
cat data.json | dasel -i json --root 'users.each(active = true)'

# 将所有值递增
echo '[1,2,3]' | dasel -i json --root 'each($this = $this + 1)'

过滤后转换

# 只获取活跃用户,然后提取名字
cat data.json | dasel -i json 'users.filter(active == true).map(name)'

对象操作

通过展开合并

# 向现有对象添加新键
cat base.json | dasel -i json --root '{ $root..., "newKey": "value" }'

# 合并两个对象
cat base.json | dasel -i json --root '{ $root..., "extra": true, "version": 2 }'

通过重建删除字段

由于 v3 没有 delete 命令,通过构建仅包含所需键的新对象来移除字段:

# 只保留 "name" 和 "email",丢弃其他所有内容
echo '{"name":"a","email":"b","password":"c"}' | dasel -i json --root '{ name, email }'

通过重建重命名字段

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

多步骤转换

使用变量赋值和分号进行复杂操作:

# 将中间结果存储在变量中,然后转换
cat data.json | dasel -i json '$active = users.filter(active == true); $active.map(name)'

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

条件转换

# 根据条件设置值
cat data.json | dasel -i json --root 'if(count > 5) { status = "many" } else { status = "few" }'

转换模式

关于详细按用例的转换模式(配置更新、批量处理、格式迁移、数据重塑、错误处理),请参阅 转换模式。

参考

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).

相关技能