skills.rest
aswin-dev-debug
aswin-dev-debugCOMMUNITY
Explore all skills by this author →
𝕏@Aswin_Ashu9301GitHub

zeus-change-control

Classifies, gates, and reviews code changes for the Zeus Lightning wallet repository.

Updated Sep 2, 2026
Search Tags:#code review#pull request#commit conventions#change management#contribution guidelines#ci checks#bitcoin wallet
One-click install
npx skills add https://github.com/aswin-dev-debug/Ai-Finance-analyzer --skill zeus-change-control-aswin-dev-debug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: zeus-change-control
Source: https://github.com/aswin-dev-debug/Ai-Finance-analyzer/tree/main/lib/zeus-contrib/zeus/.claude/skills/zeus-change-control
Command: npx skills add https://github.com/aswin-dev-debug/Ai-Finance-analyzer --skill zeus-change-control-aswin-dev-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Contributing to Zeus, a React Native Bitcoin/Lightning wallet, involves strict unwritten maintainer rules, change classification gates, and review conventions that are easy to violate, causing PR rejections, reverts, or even user fund loss. ## Core Features & Use Cases - Change Classification & Gates: Categorizes changes as funds-touching, storage-touching, UI-only, docs-only, dependency, or locales, and states the approval gate each requires before coding and before merge. - PR & Commit Conventions: Documents the mandatory PR template sections, commit message prefix style, ACK/tACK/NACK review vocabulary, and the four CI checks that run on every pull request. - Incident-Backed Rules: Explains the four maintainer non-negotiables (storage gating, revert-first near releases, no payment-path refactors, manual two-platform testing) with the real incidents that motivated them. - Use Case: Before opening a PR that edits locale files or touches the keychain settings blob, consult this Skill to learn that only locales/en.json may be edited and that storage changes require maintainer sign-off plus a written migration plan. ## Quick Start Ask how to classify and submit a change to the Zeus wallet, for example what approval is needed before editing storage migrations or payment code.

Frequently Asked Questions about zeus-change-control

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

FAQPage Schema
How do I submit a pull request to the Zeus Lightning wallet?▼

Fill in every section of the PR template without deleting it, run yarn verify locally, and manually test on both iOS and Android. First-time contributors submitting features or UI changes must attach screenshot or video evidence or the PR is closed within 24 hours.

What approval is needed to change storage or keychain code in Zeus?▼

Any change touching the zeus-settings-v2 blob, keychain keys, storage/index.ts, or migrations requires maintainer sign-off plus a written migration plan before coding begins. This gate exists because a bad write can brick wallets or leak seeds with no server-side undo.

Which CI checks run on Zeus pull requests?▼

Exactly four checks run on PRs: Test (jest), Lint (eslint plus the styles test), Prettier, and Typescript Check, all mirrored locally by yarn verify. CI never builds or launches the mobile app, which is why manual two-platform testing is mandatory.

Can I edit translation files other than en.json in Zeus?▼

No, only locales/en.json may be edited in-repo. The other 33 locale files are managed through Transifex, and PRs modifying them directly are rejected; request a translator role on Transifex instead.

What do ACK, tACK, and NACK mean in Zeus code review?▼

ACK means full approval with code reviewed and changes tested, usually citing a commit hash. tACK means tested without full review, cACK means conceptual agreement, and NACK recommends against merging and must include detailed reasoning.

Why was my Zeus PR reverted shortly after merging?▼

Zeus follows a revert-first policy near releases: regressions found during release testing are reverted the same day rather than forward-fixed under pressure. Check git log for a revert PR referencing your change and re-land the fix properly later.

Related Skills

Explore More Software Engineering Skills→
calvingitcalvingit

flutter-setting-up-on-macos

Configures macOS development tools for Flutter targeting iOS and macOS via flutter doctor and flutter devices.

Community
Intermediate
ShawnRnShawnRn
1

github-release

Automate SmartDash Android release publishing via GitHub Actions workflows.

Community
Advanced
pantheon-orgpantheon-org
1

pr-iteration

Iteratively fix lint, typecheck, test, and build failures until CI passes.

Official
Intermediate
AIAsysAIAsys
21

open-source-contribution

Standardize open source contribution workflows for issue reporting, claiming, and pull requests.

Official
Intermediate