// Use when you are adding or updating a codemap generator for a frontend Angular repo.
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-generator-hygiene |
| description | Use when you are adding or updating a codemap generator for a frontend Angular repo. |
| version | 1.0.0 |
| source | continuous-learning |
| status | approved |
| learned_from | skills/learned/learned-codemap-generator-hygiene.md |
Extracted: 2026-02-24 Source: session extraction
Patterns for maintaining a codemap generator that stays useful over time.
You are adding or updating a codemap generator for a frontend Angular repo.
Prefer maps that answer:
Avoid volatile metrics and noisy diffs:
Do not introduce misleading subsystem names (for example "database" or "backend" in a frontend app).
If one generated file is wrong, fix the generator and regenerate the whole set. Do not partially delete generated outputs (INDEX + links will drift).
Use regex-based extraction when speed and determinism matter (no AST required):
// loadChildren targets
extractRegexAll(
content,
/loadChildren\s*:\s*\(\)\s*=>\s*import\(['\"]([^'\"]+)['\"]\)/g,
);
// providers attached to routes
extractRegexAll(content, /(provide[A-Za-z0-9_]+\(\))/g);