// Use when you need to debug or extend a feature and the repo is too large for ad-hoc grepping.
Use this skill for any git work such as creating branches, staging changes, writing commit messages, pushing branches, or preparing pull requests. Delegates git execution to the git-specialist agent.
Pre-merge code review for Angular + TypeScript pull requests. Diffs current branch against a target branch, applies Angular-specific checklists (signals, RxJS, clean architecture, flurryx, TS strict), runs lint + tsc, and emits a tiered report (verbose for juniors, terse for seniors). Auto-loads project AGENTS.md rules. Use when user runs /cop-review, says "pre-merge review", "review before merging", "check my PR against <branch>", or invokes the merge-cop agent.
Signal-first reactive state management for Angular. Bridge RxJS streams into cache-aware stores, keyed resources, mirrored state, and replayable history. Use when generating or modifying Angular code that uses flurryx for state management, or when scaffolding new feature modules that follow the flurryx facade pattern.
Automatically extract reusable patterns from OpenCode sessions and save them as learned skills for future use.
evidence-first decision-gating for planning, design, architecture, and refactor requests with unresolved requirements, scope, constraints, facts, or tradeoffs. use when the next safe step is to ask exactly one dependency-safe question before proposing a plan or implementation, especially when critical decisions are not yet closed.
When adding values to any union type in a domains/models/ file
| name | learned-codemap-jump-navigation-angular |
| description | Use when you need to debug or extend a feature and the repo is too large for ad-hoc grepping. |
| version | 1.0.0 |
| source | continuous-learning |
| status | approved |
| learned_from | skills/learned/learned-codemap-jump-navigation-angular.md |
Extracted: 2026-02-24 Source: session extraction
Use codemaps as a jump-table to move from a user-facing screen to the code that wires it: routes -> providers -> facade/use-case -> ports/adapters -> stores/proxies.
This is optimized for repos that use:
routes.ts)*providers.ts)You need to debug or extend a feature and the repo is too large for ad-hoc grepping.
Start at the codemap index and follow the focused maps in order.
docs/CODEMAPS/INDEX.mddocs/CODEMAPS/ROUTING.md
loadChildren, loadComponent)provide*())docs/CODEMAPS/PROVIDERS.md
*providers.ts or *-service.providers.ts fileAppContext.*)docs/CODEMAPS/PUBLIC-APIS.md (ports + provider factories)docs/CODEMAPS/APPLICATION.md (facades + use-cases)docs/CODEMAPS/STATE.md (stores + session proxies)docs/CODEMAPS/LAYERS.mdRegenerate the maps before a deep investigation:
npm run codemaps:generate
docs/CODEMAPS/ARCHITECTURE.md, docs/CODEMAPS/MODULES.md, docs/CODEMAPS/FILES.md.