sf-audit-translate

Audit multilingual projects for translation consistency and i18n SEO compliance.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/diane-defores/shipflow --skill sf-audit-translate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sf-audit-translate
Source: https://github.com/diane-defores/shipflow/tree/main/skills/sf-audit-translate
Command: npx skills add https://github.com/diane-defores/shipflow --skill sf-audit-translate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill audits translation consistency, completeness, and technical correctness in multilingual projects, preventing internationalization issues.

Core Features & Use Cases

  • Translation Quality Assessment: Checks for missing, inconsistent, or erroneous translation entries across locales.
  • Technical i18n Audit: Validates lang attributes, hreflang tags, canonical URLs, and locale-specific SEO setups.
  • Use Case: Before launching a new language, verify that all UI strings, meta tags, and URL slugs are properly translated and aligned for optimal user experience and search engine indexing.

Quick Start

Provide the project directory path to run a full multilingual audit and identify translation gaps and technical issues within the codebase.

Frequently Asked Questions about sf-audit-translate

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

FAQPage Schema
How do I audit translation consistency and completeness across multiple locale files?

To audit translation consistency, this Skill analyzes multilingual projects to locate missing, inconsistent, or erroneous translation entries across locale files. It scans entire repositories or specified files to identify localization gaps and ensure content completeness.

What is the best way to check hreflang tags and locale-specific SEO configurations?

The best way to check hreflang tags is through a technical i18n audit, which validates lang attributes, canonical URLs, and locale-specific SEO setups. This verifies that search engines properly index multilingual content.

How do I verify internationalization setup before launching a new language?

To verify internationalization setup before launching a new language, provide your project directory path to run a full multilingual audit. This confirms UI strings, meta tags, and URL slugs are properly translated and aligned for user experience.

Can I scan an entire repository for missing translation entries and i18n issues?

Yes, you can scan an entire repository for missing translation entries and i18n issues. The Skill applies across full project directories to locate and fix localization problems, ensuring a seamless international user experience.

Does this i18n audit require understanding of my project's specific locale file structure?

Yes, performing an effective i18n audit requires understanding of your project's i18n setup, locale files, and SEO meta configurations. This knowledge allows the Skill to accurately locate and fix technical localization issues.