TS JS Validation
Testing & Qualityts-js-validationTS JS Validation is an Agent Skill for testing & quality published in the invertase/react-native-firebase repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Validate React Native Firebase changes by running the CI-equivalent prepare, TypeScript, lint, Jest, formatting, and compare-types scripts. Use before handoff, commit, or push when package sources, native bridge code, or docs changed.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/invertase/react-native-firebase/blob/HEAD/.agents/skills/ts-js-validation/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/ts-js-validation, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
React Native Firebase TS/JS Validation
Scope
Use this skill to validate changes in the React Native Firebase monorepo before handoff, commit, or push.
It runs the same static-analysis and compile/test commands CI uses for the Lint, TypeScript, Jest, docs, and compare-types jobs — not a narrowed JS-only subset.
Triggers
Use this skill when the user asks for:
- testing TS or JS changes
- validating TypeScript or JavaScript edits before commit or handoff
- running the standard validation pass for RNFB
- checking whether package changes compile and pass Jest
- formatting and linting before push
- CI-equivalent validation before publication
Out-of-scope boundaries
Do not use this skill for:
- release validation that requires the full platform, emulator, Detox, or packaging matrix (see validation checklist § e2e)
- migrating a package from JavaScript to TypeScript; use the TypeScript refactor or migration skills instead
Defaults
- Default tool or method: run the canonical command sequence below from the repository root
- Fallback when default fails: stop, inspect the failure, fix issues in the current change set when authorized, then rerun the failed command and any later commands
- Why this default exists: the sequence mirrors CI Lint + TypeScript + Jest + docs + compare-types gates
Command sequence
Run these root package.json scripts in order. Canonical checklist: validation-checklist.md. Agent allowlist (no improvisation): agent-command-policy.md. OKF bundle wins if this skill disagrees.
yarn lerna:prepareyarn tsc:compileyarn tsc:compile:consumeryarn reference:apiyarn lint— CI Lint job (lint:js+lint:android+lint:ios:check). Whenlint:androidreformats Java, commit the formatter output and rerun until exit 0.- When
docs/**changed:yarn lint:markdownthenyarn lint:spellcheck— CI docs job yarn lint:js --fixthenyarn lint:jswhen step 5 reported ESLint issues only (optional shortcut before re-running fullyarn lint)yarn tests:jestyarn format:js— inspect diff; rerunyarn lintif formatting touched filesyarn compare:types
Gotchas
- Forbidden:
yarn workspace … prepare,cd packages/<pkg> && yarn prepare/build,yarn jet,npx jet— see agent command policy. On failure, fix product code and re-run the same canonical command. yarn lintis not optional when native Java or iOS sources are in the diff —lint:jsalone does not match CI.yarn lint:spellcheckis not optional whendocs/**is in the diff —lint:markdownalone does not match CI.yarn format:jswrites changes acrosspackages/**/*.{js,ts,tsx}. Check the diff after formatting and do not revert user changes.- Run commands from the repository root so workspace resolution, root
tsconfig.json, and Jest configuration are consistent. yarn lerna:preparemay rebuild or refresh package artifacts needed before TypeScript or tests run.yarn compare:typesinstalls dependencies under.github/scripts/compare-typesbefore running the type parity comparison. Keep it last.- If validation is slow, keep the command running rather than replacing it with a narrower command unless the user explicitly narrows validation.
Workflow
- Confirm the task scope and note changed packages, native paths, or docs.
- Check whether the worktree has unrelated dirty files if the current task includes code edits or commit preparation.
- Run the command sequence from the repository root.
- If
yarn lint:androidoryarn format:jschanges files, include those changes and rerunyarn lintbefore continuing. - If a command fails:
- stop before running later commands
- identify whether the failure belongs to the current changes, pre-existing repo state, or missing local setup
- fix current-change failures when authorized, then rerun the failed command and continue the remaining sequence
- Return a concise result with the commands run, pass/fail status, and any remaining blockers.
Validation loop
- Run the command sequence.
- If validation fails because of current changes and fixing is in scope, fix the issue and rerun the failed command plus all later commands.
- If validation fails for unrelated or environment-specific reasons, stop and report the blocker with the command that failed and the shortest useful error summary.
- Only report success when every applicable command in the sequence completes successfully.
Output format
Use this template:
# TS/JS Validation
## Summary
- passed | failed | blocked
- one-sentence validation verdict
## Commands
- `yarn lerna:prepare`: passed | failed | not run
- `yarn tsc:compile`: passed | failed | not run
- `yarn tsc:compile:consumer`: passed | failed | not run
- `yarn reference:api`: passed | failed | not run
- `yarn lint`: passed | failed | not run
- `yarn lint:markdown`: passed | failed | not run | n/a
- `yarn lint:spellcheck`: passed | failed | not run | n/a
- `yarn tests:jest`: passed | failed | not run
- `yarn format:js`: passed | failed | changed files
- `yarn compare:types`: passed | failed | not run
## Findings
- failing suite, compiler error, or setup blocker if any
## Next actions
1. next required action, only if validation did not fully pass
Constraints
- Keep responses factual and grounded in command output.
- Do not skip
yarn lintor docs lint rows when the diff requires them. - Do not claim validation passed unless
compare:typesran after any formatting changes. - Do not revert unrelated local changes.
- Avoid broad refactors while fixing validation failures.
Additional resources
Load files only when needed:
okf-bundle/testing/validation-checklist.md— full validation command list including e2e, coverage, and CI job mapping- Read
package.jsonif command names or script definitions need to be confirmed. - Read affected package
type-test.tsor nearby__tests__/files only when a failure needs package-specific diagnosis.