dx-optimizer
PassAudited by ClawScan on May 9, 2026.
Overview
This instruction-only skill is aligned with developer-experience optimization, but it can steer the agent to change build, test, and workflow automation settings, so users should review proposed changes.
This skill appears safe to install as an instruction-only DX assistant. Use it with normal engineering safeguards: review diffs, test build and workflow changes, and be especially careful with pre-commit hooks, CI/CD configuration, release automation, or environment setup changes that could affect other developers.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The agent may propose or make changes that affect local builds, test behavior, developer tooling, or team workflow automation.
The skill directs the agent to make implementation changes, not just provide advice. That is consistent with a DX optimizer, but it can lead to edits in build, testing, tooling, or workflow files.
4. Implement comprehensive developer experience enhancements
Review all generated diffs and avoid applying CI/CD, hook, release, or migration automation changes without normal code review and testing.
A poor automation or CI/CD change could slow developers, block commits, or affect shared build and deployment workflows.
Workflow automation and CI/CD changes can propagate across a team or pipeline. The behavior is disclosed and purpose-aligned, but mistakes could affect more than one local task.
Workflow automation: - Pre-commit hooks - Code generation - Boilerplate reduction - Script automation - Tool integration - CI/CD optimization - Environment setup - Onboarding automation
Apply these changes incrementally, test them locally and in CI, and document any new hooks or automation for the team.