ux-task-to-phrase

Synchronize pending UX copy from Markdown task files into Phrase localization CSVs.

1|Updated May 21, 2020
One-click install
npx skills add https://github.com/ahandsel/debugging_log --skill ux-task-to-phrase
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ux-task-to-phrase
Source: https://github.com/ahandsel/debugging_log/tree/main/skills/ux-task-to-phrase
Command: npx skills add https://github.com/ahandsel/debugging_log --skill ux-task-to-phrase

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates manual data entry errors and synchronization delays when moving UX copy from design tasks into localization files, ensuring your Phrase data stays perfectly aligned with your task documentation.

Core Features & Use Cases

  • Automated CSV Updates: Automatically updates English copy and tag CSV files based on pending TODO items in your task Markdown files.
  • Safe Workflow: Validates project, branch, and tag metadata before applying changes and provides a ready-to-run push command for the user to execute after review.
  • Use Case: When a developer finishes implementing a new feature, they can use this skill to instantly push all pending UX copy from their task document into the project's localization data files without manually editing CSVs.

Quick Start

Use the ux-task-to-phrase skill to process the pending UX copy in the file tasks/473-delete-kintone-onetime-sync.md.

Frequently Asked Questions about ux-task-to-phrase

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

FAQPage Schema
How do I sync UX copy from Markdown tasks to Phrase localization CSVs?

To sync UX copy from Markdown to Phrase, this skill processes pending task files to update English copy and tag metadata. It validates project IDs and key prefixes before generating shell commands for repository synchronization.

What is the best way to automate updating English copy in Phrase CSV files?

Automating English copy updates in Phrase CSV files is handled by parsing Markdown task documents for pending TODO items. The skill enforces strict validation against project ID references to prevent manual data entry errors.

Can I use local Markdown files to push UX copy directly to Phrase data?

Yes, you can use local Markdown files to push UX copy to Phrase data. The skill requires local file system access to read tasks and update CSVs, outputting a ready-to-run push command for you to execute after review.

How does validation work when synchronizing task documentation to localization files?

Validation when synchronizing task documentation to localization files works by checking project, branch, and tag metadata against project ID references and key prefixes. This ensures safe workflow execution before applying any CSV changes.

Do I need to manually edit CSVs after generating UX copy from task documents?

No, you do not need to manually edit CSVs after generating UX copy from task documents. The skill automatically updates the files and provides a shell command for repository synchronization, allowing you to review before final execution.

What happens if project ID references or key prefixes do not match during CSV updates?

If project ID references or key prefixes do not match during CSV updates, the strict validation process halts the synchronization. This prevents misaligned data from being written to your Phrase localization files.