Skip to content
TrustedSkillsbeta
Back to all skills

Angular Best Practices Rules Reviewer

Checked
alfredoperez·vlatest·frontend

Helps with Angular, best practices as part of building frontend UIs and user experiences workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add alfredoperez/angular-best-practices --skill angular-best-practices-rules-reviewer -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

alfredoperez

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned alfredoperez/angular-best-practices at a499a47861.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
a499a47861
Manifest
.claude/skills/angular-best-practices-rules-reviewer/SKILL.md
Scanned
5 files, 589 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

The Angular Best Practices Rules Reviewer skill analyzes codebases to identify violations of established Angular development standards and community guidelines. It provides actionable feedback on module structure, component organization, and adherence to the framework's recommended patterns.

When to use it

  • Before committing changes to ensure new components follow team-specific or official Angular conventions.
  • During code reviews to catch architectural drift or anti-patterns in existing modules.
  • When integrating third-party libraries to verify they align with your project’s strict style guide.
  • To automate linting workflows that go beyond basic syntax checking into semantic best practices.

Key capabilities

  • Detects deviations from official Angular documentation and community-accepted patterns.
  • Reviews module imports, dependency injection strategies, and component lifecycles.
  • Identifies potential performance bottlenecks caused by inefficient change detection or data binding.
  • Enforces consistent naming conventions and file structures across the application.

Example prompts

  • "Review this new customer dashboard component for adherence to Angular best practices."
  • "Analyze the entire src/app folder and list any violations of standard module organization."
  • "Check my service layer for proper dependency injection patterns and identify any circular dependencies."

Tips & gotchas

Ensure your project is fully built or at least has a valid configuration file, as the reviewer needs context to understand the application's architecture. This skill complements but does not replace static analysis tools like ESLint; use it specifically for high-level architectural and pattern compliance.