lint-resources

Validate Android string resource naming conventions in strings.xml files.

1|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/oscardlfr/AndroidCommonDoc --skill lint-resources
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint-resources
Source: https://github.com/oscardlfr/AndroidCommonDoc/tree/main/skills/lint-resources
Command: npx skills add https://github.com/oscardlfr/AndroidCommonDoc --skill lint-resources

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the validation of string resource naming conventions in Android projects, preventing naming issues that can cause UI merging conflicts.

Core Features & Use Cases

  • Naming Convention Validation: Checks for snake_case, prefixes, duplicates, and Swift sync consistency.
  • Project-wide Scanning: Validates all strings.xml files within the project or specified modules.
  • Swift Sync Verification: Ensures Compose keys align with .xcstrings files for parity.
  • Error/Warning Reporting: Reports errors and warnings for quick troubleshooting.

Quick Start

Run the lint-resources skill on your project to check string resources.

Frequently Asked Questions about lint-resources

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

FAQPage Schema
How do I validate string resource naming conventions in an Android project?

You can validate string resource naming conventions by running an automated script on your project root to check `strings.xml` files for snake_case formatting, prefixes, duplicates, and Swift sync consistency.

What is Swift sync verification for Android string resources?

Swift sync verification ensures Compose keys align with `.xcstrings` files for parity. It checks that your Compose keys match the Swift localization files to prevent UI merging conflicts.

Can I check string resources for a specific module instead of the whole project?

Yes, you can scope the validation to a specific module. The script executes on the project root by default but supports optional scoping to target individual modules.

How do I prevent UI merging conflicts caused by string resource naming issues?

Prevent UI merging conflicts by running automated resource file checks before merging UI changes. The validation reports errors and warnings for duplicates and naming inconsistencies for quick troubleshooting.

Does the string resource validation support custom naming rules and strict checking?

Yes, the validation supports custom naming rules and optional strict checking. You can configure the script to enforce specific naming conventions and format the output for your project needs.