Skip to content
Back to skills

ngautopilot

ASecurity

Use when an AI coding agent needs NgAutoPilot routing, version-aware Angular guidance, frontend quality gates, skill catalog maintenance, plugin bundle validation, or safe agent adapter installation.

  • 4 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added October 2, 2026
developmentjavascripttypescriptgojavabashangulartestingapifrontendsecurity

Works with

  • cli
  • api

Security analysis

A100/100

Pro scans all 20 files and shows the line behind each finding

Scanned October 2, 2026

npx -y skills add janpereira-dev/ngAutoPilot --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of ngautopilot?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for ngautopilot
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/janpereira-dev-ngautopilot/badge)](https://www.skillsdirectory.com/skills/janpereira-dev-ngautopilot)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: ngautopilot
description: Use when an AI coding agent needs NgAutoPilot routing, version-aware Angular guidance, frontend quality gates, skill catalog maintenance, plugin bundle validation, or safe agent adapter installation.
---

# NgAutoPilot

## Purpose

Use this root skill as the public entry point for NgAutoPilot. It explains how to approach a repository with the NgAutoPilot catalog, packs, adapters, plugin bundles, and validation gates.

NgAutoPilot is an agent-agnostic engineering toolkit for bounded Angular, TypeScript, JavaScript, frontend, and quality work. It is not an autopatcher, framework, runtime dependency, or replacement for tests and review.

## When to Use

Use this skill when:

- You are installing or using NgAutoPilot in an agent workspace.
- You need to choose an NgAutoPilot pack, adapter, or plugin bundle.
- You are maintaining the skill catalog, marketplace manifests, adapters, or bundle sync.
- You are doing Angular, frontend, TypeScript, JavaScript, RxJS, testing, quality, or upgrade work and need version-aware routing.
- You need a safe default workflow before selecting a more specific NgAutoPilot skill.

## Inputs Expected

- User goal and affected area
- Repository stack and framework versions
- Package manager and available scripts
- Installed agent adapter or target agent
- Requested pack or plugin, if any
- Current validation requirements

## Operating Model

Follow this loop:

```txt
Inspect repository -> detect stack and versions -> select smallest relevant skill -> assess compatibility and risk -> make the smallest reversible change -> validate with repository scripts -> report evidence and residual risk
```

Prefer focused packs over loading the full catalog. Every focused pack includes `ngautopilot-core` automatically.

## Core Routing

Start with these concepts:

| Need | Use |
| --- | --- |
| General workflow | `core.autopilot-orchestrator` |
| Project shape and stack | `core.project-intake`, `core.stack-version-detection` |
| Skill selection | `core.skill-router` |
| Version safety | `core.compatibility-router` |
| Change risk | `core.risk-assessment` |
| Angular upgrades | `angular.upgrades.angular-upgrade-orchestrator` |
| Angular 21 to 22 | `angular.versioning.angular-21-to-22-index` |
| Quality work | `quality.fundamentals.quality-decision-matrix` |

## Installation Entry Points

Use the CLI for bounded installation:

```bash
npm exec --package=ngautopilot -- ngautopilot adapters
npm exec --package=ngautopilot -- ngautopilot packs
npm exec --package=ngautopilot -- ngautopilot install --agent opencode --pack ngautopilot-angular-foundations --dry-run
```

Use marketplace/plugin discovery for browsing. Do not treat marketplace bundles as pack selection.

## Maintenance Rules

- Preserve separation between source skills in `skills/` and distributable bundles in `plugins/`.
- Update source skills first, then sync plugin bundles.
- Do not invent Angular compatibility data, APIs, CLI commands, or validation results.
- Keep Angular upgrade hops separate from modernization work.
- Prefer the smallest reversible change.
- Do not add dependencies unless required by the task.

## Validation

Use repository scripts that match the changed area:

```bash
npm run skills:validate
npm run skills:catalog
npm run security:scan
npm run release:validate
```

For Skill Lab changes, also run:

```bash
npm run skill-lab:validate
npm run skill-lab:test
npm run skill-lab:ci
```

## Do

- Inspect before editing.
- Route through the smallest useful skill.
- Validate source and plugin bundles together when skill content changes.
- Report exact commands run and outcomes.
- Call out residual risks and unavailable checks.

## Do Not

- Do not broadly refactor when a narrow fix works.
- Do not move or rename large skill trees without a migration plan.
- Do not mix multiple Angular major hops into one validation gate.
- Do not publish, commit, or open pull requests unless explicitly requested.
- Do not treat `npx skills add janpereira-dev/ngAutoPilot` as focused pack installation.

## Expected Output

When this skill is used, return:

1. Selected NgAutoPilot entry point or focused skill.
2. Compatibility and risk notes.
3. Files changed or inspected.
4. Validation commands and results.
5. Remaining risks or next safe step.

Files in this skill

  • .claude-plugin/marketplace.json6.7 KB
  • .markdownlint.json83 B
  • .vscode/settings.json50 B
  • AGENTS.md1.3 KB
  • CHANGELOG.es.md13.8 KB
  • CHANGELOG.md15.7 KB
  • CODE_OF_CONDUCT.es.md2.4 KB
  • CODE_OF_CONDUCT.md2.3 KB
  • CONTRIBUTING.es.md4.7 KB
  • CONTRIBUTING.md9.2 KB
  • README.es.md11.7 KB
  • ROADMAP.es.md1.8 KB
  • ROADMAP.md1.5 KB
  • SECURITY.es.md2.1 KB
  • SECURITY.md2 KB
  • SKILL.md4.2 KB
  • adapters/native-instructions.template.md1.7 KB
  • adapters/native-layouts.json2.8 KB
  • agent-plugins.config.json887 B
  • assets/catalog-map.es.svg4.1 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…