noyara-merge-ready
Skill1 starsChanged 3 months agoMITView on GitHub
Prepare a Noyara change or branch for the maintainer's final review. Use when asked to make work merge-ready, review a branch, prepare a pull request, or complete verification before handoff.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- eas-hostingSkill
- expo-native-uiSkill
- expo-routerSkill
- expo-uiSkill
- expo-upgradeSkill
- humanizerSkill
- papercutsSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Read AGENTS.md and the files touched by the change.
- Very specific: line 13
Use development as the normal comparison branch.
- Distinctive: line 18
Check only issues supported by the diff and surrounding call paths:
- Distinctive: line 31
Add one focused regression check for non-trivial logic or a reproduced bug.
- Distinctive: line 32
Do not refactor adjacent code or add speculative infrastructure.
- Very specific: line 36
Run npm run check until it passes.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Noyara Merge Ready
Take the current work to a verified handoff. Never merge, push, publish, or open a pull request unless the user explicitly asks.
1. Establish scope
- Read
AGENTS.mdand the files touched by the change. - Use
developmentas the normal comparison branch. Use another base only when the user names it or the work is a promotion betweendevelopment,preview, andmain. - Review committed, staged, unstaged, and relevant untracked files. Preserve pre-existing user changes.
2. Review the change
Check only issues supported by the diff and surrounding call paths:
- Unnecessary complexity, unused scaffolding, duplicated helpers, and unrelated edits.
- Expo SDK 57, Expo Router, React Native, and
@expo/uicorrectness. Consult the matching official Expo skill and versioned documentation. - iOS, Android, and web behavior, including accessibility, localization boundaries, and platform-specific fallbacks.
- Privacy and security: embedded secrets, unsafe
EXPO_PUBLIC_values, permissions, deep links, untrusted input, and data loss. - Release quality: logs, TODOs, generated artifacts, documentation, and CI coverage.
Trace callers before proposing a bug fix. Reject theoretical findings that do not apply to the current product or change.
3. Fix verified findings
- Fix blockers and clear correctness issues with the smallest coherent change.
- Add one focused regression check for non-trivial logic or a reproduced bug.
- Do not refactor adjacent code or add speculative infrastructure.
4. Verify
- Run
npm run checkuntil it passes. - For user-visible changes, exercise every affected platform available locally and capture screenshots when useful.
- State any platform that was not tested. Never report an unrun check as passing.
- Re-read the final diff and run
git diff --check.
5. Hand off
Report:
- what changed and why;
- exact automated and manual verification performed;
- untested platforms or remaining maintainer decisions;
- whether the branch is ready for final review.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

