Results for “strings”

Takes an app from hardcoded strings to a localized, continuously translated one with i18next (Locize optional): stack detection, config, wrapping strings in t(), key extraction, Locize sync, and AI translation. Use when the user asks to add or set up i18n, internationalization, localization, translations, or multi-language support, including phrasings like "add i18n", "internationalize my app", "make my app multilingual", "make my app translatable", "localize my app", "find hardcoded strings", "wrap my strings", and library-specific ones like "set up i18next", "add react-i18next", "use next-i18next". Also use when the user names languages they want to support ("I want German and French", "support more languages"), when an app already has i18next but strings are still hardcoded, or when translations need to move to a managed backend. Do not use for translating or reviewing strings in a project whose i18n is already set up.

The English summary is being prepared. Showing the original description.

Extracts ASCII and Unicode strings from a binary and classifies them into investigative categories: URLs, IPs, file paths, registry keys, mutexes, commands, and API names, prioritizing the analyst's attention. Activates for requests to extract strings, classify strings output, or pull human-readable artifacts from a sample.

The English summary is being prepared. Showing the original description.

Understand compiled Go and Rust programs even when function names have been removed. Use runtime clues, recovered metadata, and error strings to identify important functions and trace application logic with language-specific reverse engineering methods.

• Analyzing Go binaries with function names removed
• Investigating Rust releases through panic strings
• Recovering Go function names from metadata

Recovers obfuscated strings and resolves dynamically loaded APIs in malware: reversing XOR/stack-string/encoding schemes and mapping API-hash lookups back to function names. Activates for requests to deobfuscate strings, decode stack strings, or resolve API hashing in a binary.

The English summary is being prepared. Showing the original description.

Survey all user-facing strings in a codebase — map coverage and find gaps. Use when asked "what user-facing strings do we have", "map our copy coverage", or "find hardcoded strings".

The English summary is being prepared. Showing the original description.

Convert chat messages into template strings for local model runtimes such as Ollama or llama.cpp. Optionally route queries among a few registered intents using embeddings, numerical representations of meaning, without calling a model.

• Preparing prompt strings for Ollama
• Formatting conversations for a local model
• Routing queries among a few intents

Analyze executable files and libraries with IDA Pro. Inspect pseudocode, strings, function calls, and data flow, then add meaningful names and comments and produce a Markdown report documenting findings and analysis steps.

• Investigating executable files and libraries
• Tracing processing from strings and function calls
• Organizing analysis with comments and meaningful names

Inspect executable files from the command line with radare2, starting with file details, strings, and imported functions. Trace code through disassembly, compare binaries, automate inspections, or apply explicitly requested patches with verification.

• Inspecting an unfamiliar executable file
• Finding the function that uses an error message
• Comparing two versions of a binary

Inspect compiled programs in Binary Ninja using strings, function references, and intermediate representations—views of program logic at different levels. Trace data flow and report findings with addresses, supporting evidence, confidence, and reproduction steps.

• Tracing function calls and data flow in Binary Ninja
• Cross-checking findings from other disassemblers
• Automating binary analysis with the Python API

Analyzes one .NET project to plan integration tests for an Oracle-to-PostgreSQL migration. Identifies database access methods, prioritizes migration risks, and documents test cases, seed data, and coverage, including empty strings, NULL values, and timezone behavior.

• Identifying database access methods that need integration tests
• Prioritizing tests for Oracle-specific behavior
• Planning checks for empty strings, NULL values, and timezones

Review and refine source-code comments and documentation attached to functions or other declarations. The skill removes redundant explanations, checks outdated TODOs, and preserves concise, evidence-based reasons and constraints that maintainers cannot readily infer from the code.

• Cleaning up redundant code comments
• Reviewing TODO and FIXME markers
• Checking documentation when changing code

Analyze Go malware binaries in Ghidra by extracting build metadata, function names, dependencies, and relevant strings. Use GoResolver to help recover obscured names and organize functions so analysts can focus their reverse engineering work.

• Investigating the structure of a Go malware sample
• Recovering function names from stripped or obfuscated binaries
• Identifying embedded Go modules and dependencies

Update cmux interface text across supported languages and audit the results. The workflow identifies changed messages, prepares translation entries, and checks for missing translations, plural forms, and placeholders that insert values into text.

• Translating new interface and settings text
• Finding translation gaps after English edits
• Checking plural forms and placeholders

Prepare and check a game's localization, from extracting text and briefing translators to checking missing translations and display limits. It also covers cultural review, voice recording preparation, right-to-left layouts, and release quality checks.

• Find hardcoded text and prepare translation tables
• Check missing translations and placeholder mismatches
• Prepare translator briefs and voice recording scripts

Write and troubleshoot n8n expressions, the formulas that pass and transform data between workflow steps. Covers field references, webhook inputs, dates, strings, and choosing between expressions and Code nodes for data transformations.

• Fixing expression syntax errors
• Using webhook data in downstream steps
• Formatting dates and strings

Review newly added comments, docstrings, and changelog entries so future readers can understand the current code. Revise development history, redundant explanations, and unclear shorthand while preserving constraints that the code cannot explain on its own.

• Review comments before committing
• Check prose added across a branch
• Clarify function documentation for future readers

Create and maintain code comments, API specifications, documentation sites, and user guides. Apply consistent formats, document parameters and errors, validate code examples, and report which parts of the code have been documented.

• Add explanations to public functions and classes
• Create API specifications and reference pages
• Build a documentation site

Recover failed writes of large files or code containing special characters by placing content in a temporary Python script. Use raw strings or Base64 encoding, then check that the output file exists and has content.

• Retrying writes that fail with unknown errors
• Writing TypeScript or TSX containing template literals
• Saving long text with Unicode or special characters

Build boolean and X-ray search strings to source candidates. Use when asked to build a boolean search, source candidates on LinkedIn/Google, write an X-ray search, or find people with specific skills. Produces ready-to-paste boolean strings (with synonyms, must-haves, and exclusions), X-ray variants for LinkedIn/GitHub, and a refinement plan to widen or narrow the result set.

The English summary is being prepared. Showing the original description.

MSA2dist calculates pairwise distances between all sequences of a DNAStringSet or a AAStringSet using a custom score matrix and conducts codon based analysis. It uses scoring matrices to be used in these pairwise distance calcualtions which can be adapted to any scoring for DNA or AA characters. E.g. by using literal distances MSA2dist calculates pairwise IUPAC distances.

The English summary is being prepared. Showing the original description.

Write docstrings for PyTorch functions and methods following PyTorch conventions. Use when writing or updating docstrings in PyTorch code.

The English summary is being prepared. Showing the original description.

Fix password/secret authentication failures caused by trailing newlines when creating Google Cloud secrets (or similar) with bash here-strings. Use when: (1) Password authentication fails with correct password, (2) Secret created with `<<< "value"` syntax, (3) Error like "password authentication failed" or "invalid token" despite correct value. Bash here-strings (`<<<`) add a trailing newline that corrupts secrets.

The English summary is being prepared. Showing the original description.

Generate comprehensive documentation for undocumented or poorly documented codebases. Use when a user asks to document code, add JSDoc/docstrings, create README files, generate architecture docs, explain what a codebase does, produce onboarding guides, or document internal APIs. Works with any language.

The English summary is being prepared. Showing the original description.

Write concise docstrings for functions. Use when a junior developer needs help describing inputs, outputs, and errors.

The English summary is being prepared. Showing the original description.