Pre Commit
wellwelwel/poku
Run the mandatory pre-commit checks for the poku repository before staging a commit.
Quick-reference for running Ignite UI for Angular test suites.
Install Igniteui Angular Testing
$ npx skills add IgniteUI/igniteui-angular --skill igniteui-angular-testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install IgniteUI/igniteui-angular igniteui-angular-testing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/IgniteUI/igniteui-angular.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/igniteui-angular-testing .claude/skills/igniteui-angular-testing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "igniteui-angular-testing" agent skill from https://github.com/IgniteUI/igniteui-angular/tree/master/.agents/skills/igniteui-angular-testing into .claude/skills/igniteui-angular-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "igniteui-angular-testing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/IgniteUI/igniteui-angular/tree/master/.agents/skills/igniteui-angular-testingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add IgniteUI/igniteui-angular --skill igniteui-angular-testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install IgniteUI/igniteui-angular igniteui-angular-testing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/IgniteUI/igniteui-angular.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/igniteui-angular-testing .agents/skills/igniteui-angular-testing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "igniteui-angular-testing" agent skill from https://github.com/IgniteUI/igniteui-angular/tree/master/.agents/skills/igniteui-angular-testing into .agents/skills/igniteui-angular-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "igniteui-angular-testing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add IgniteUI/igniteui-angular --skill igniteui-angular-testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install IgniteUI/igniteui-angular igniteui-angular-testing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/IgniteUI/igniteui-angular.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/igniteui-angular-testing .cursor/skills/igniteui-angular-testing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "igniteui-angular-testing" agent skill from https://github.com/IgniteUI/igniteui-angular/tree/master/.agents/skills/igniteui-angular-testing into .cursor/skills/igniteui-angular-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "igniteui-angular-testing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/IgniteUI/igniteui-angular.git --path .agents/skills/igniteui-angular-testing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add IgniteUI/igniteui-angular --skill igniteui-angular-testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install IgniteUI/igniteui-angular igniteui-angular-testing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/IgniteUI/igniteui-angular.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/igniteui-angular-testing .gemini/skills/igniteui-angular-testing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "igniteui-angular-testing" agent skill from https://github.com/IgniteUI/igniteui-angular/tree/master/.agents/skills/igniteui-angular-testing into .gemini/skills/igniteui-angular-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "igniteui-angular-testing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install IgniteUI/igniteui-angular igniteui-angular-testingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add IgniteUI/igniteui-angular --skill igniteui-angular-testing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/IgniteUI/igniteui-angular.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/igniteui-angular-testing .github/skills/igniteui-angular-testing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "igniteui-angular-testing" agent skill from https://github.com/IgniteUI/igniteui-angular/tree/master/.agents/skills/igniteui-angular-testing into .github/skills/igniteui-angular-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "igniteui-angular-testing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add IgniteUI/igniteui-angular --skill igniteui-angular-testing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install IgniteUI/igniteui-angular igniteui-angular-testing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/IgniteUI/igniteui-angular.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/igniteui-angular-testing .opencode/skills/igniteui-angular-testing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "igniteui-angular-testing" agent skill from https://github.com/IgniteUI/igniteui-angular/tree/master/.agents/skills/igniteui-angular-testing into .opencode/skills/igniteui-angular-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "igniteui-angular-testing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
igniteui-angular-testing- GitHub stars
- 599
- Token cost
- ~950 tokens
- SKILL.md length
- 341 words
- Files
- 1
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Quick-reference for running Ignite UI for Angular test suites.
- Works in 8 steps: Working on a grid component? → Use the… → Working on a non-grid component or… → Iterating quickly during development? →… → …
- An agent needs to run
- SKILL.md covers Prerequisites, Test Runner, Choosing the Right Command and Karma Configs, plus 2 more sections
- Calls npm
What it does
Igniteui Angular Testing is an agent skill from IgniteUI/igniteui-angular. Quick-reference for running Ignite UI for Angular test suites. Covers the full test run (test:lib), grid-specific suites (grid, tree-grid, hierarchical-grid, pivot-grid), non-grid tests, watch mode, and auxiliary test suites (schematics, styles, i18n). Use when an agent needs to run, select, or understand the test infrastructure. Do NOT use for building — use igniteui-angular-build instead. Do NOT use for linting — use igniteui-angular-linting instead.
Its SKILL.md is about 950 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Frontend & Design, covering Internationalization, Linting and formatting and Test generation. It works with Angular and npm. The repository describes itself as: Ignite UI for Angular is a complete library of Angular UI components with the fastest grids and charts, dock manager, and more.
When your agent uses it
- An agent needs to run
- Understand the test infrastructure
- Building — use igniteui-angular-build instead
- Linting — use igniteui-angular-linting instead
Example prompts
- “/igniteui-angular-testing”
Requirements
- Node.js
Workflow steps
8 steps, taken from the first numbered list in SKILL.md.
- Working on a grid component? → Use the matching grid command (test:lib:grid, test:lib:tgrid, test:lib:hgrid, or test:lib:pgrid).
- Working on a non-grid component or directive? → Use test:lib:others.
- Iterating quickly during development? → Use test:lib:watch.
- Edited a migration or schematic? → Use test:schematics. Build first only if you also need to validate compiled output.
- Running performance tests? → Build first (build:lib or at least build:styles), then use test:lib:perf.
- Changed Sass theme logic? → Use test:styles.
- Changed i18n resource strings? → Use test:i18n.
- Final verification before marking work complete? → Use test:lib (full suite).
What it can do on your machine
Read from SKILL.md and the folder at commit 436e825. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Igniteui Angular Testing loads about 950 tokens when it runs. Until then it costs about 121 tokens; SKILL.md has 341 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 341 words (~950 tokens).
“Quick-reference card for the core test commands for the main igniteui-angular library plus schematics, styles, and i18n suites.”
- name
- igniteui-angular-testing
- user-invocable
- true
Files
Just SKILL.md in .agents/skills/igniteui-angular-testing of IgniteUI/igniteui-angular.
Open the folder on GitHubat commit 436e825
Compare with similar skills
Igniteui Angular Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Igniteui Angular Testing this skillIgniteUI/igniteui-angular | 599 | — | ~950 | Automated safety check: Pass | Custom licence | |
| Pre Commitwellwelwel/poku | 1.2k | — | ~728 | Automated safety check: Pass | MIT | |
| Cometchat Angular V5 Migrationcometchat/cometchat-skills | 129 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Stylelintmanagedcode/dotnet-skills | 486 | — | ~1.7k | Automated safety check: Pass | MIT | |
| UI OnlyOutThisLife/brooklyn-skills | 198 | — | ~364 | Automated safety check: Pass | MIT | |
| Frontend Build Timing Auditopenops-cloud/openops | 1.1k | — | ~2.3k | Automated safety check: Pass | Custom licence |
Similar skills
Cometchat Angular V5 Migration
cometchat/cometchat-skills
Upgrade an Angular app from CometChat UI Kit v4 → v5 (@cometchat/chat-uikit-angular ^4 → ^5).
Stylelint
managedcode/dotnet-skills
Use Stylelint in .NET repositories that ship CSS, SCSS, or other stylesheet assets alongside web frontends.
UI Only
OutThisLife/brooklyn-skills
While iterating on UI, do not waste time on tsc, lint, typecheck, format, full test suites, commit, or push until the user likes how it looks and works.
Frontend Build Timing Audit
openops-cloud/openops
Detects and diagnoses chunk-evaluation timing bugs in the Vite/rolldown production build of react-ui (works-in-dev / broken-in-build i18n regressions, missing UI labels, module-scope t()…
Sanity Best Practices
robotostudio/turbo-start-sanity
Sanity development best practices for schema design, GROQ queries, TypeGen, Visual Editing, images, Portable Text, Studio structure, localization, migrations, Sanity Functions, Blueprints, and…
More from IgniteUI/igniteui-angular
All 9 skills in this repoIgniteui Angular Build
IgniteUI/igniteui-angular
Quick-reference for building the core Ignite UI for Angular library and related packages.
Igniteui Angular Linting
IgniteUI/igniteui-angular
Quick-reference for linting the core Ignite UI for Angular library.
Igniteui Angular Generate From Image Design
IgniteUI/igniteui-angular
Implements Angular application views from design images using Ignite UI Angular components.
Igniteui Angular Theming
IgniteUI/igniteui-angular
Generates and customizes Ignite UI for Angular themes including color palettes, typography, elevations, and component-level styles using the Sass theming system and the igniteui-theming MCP server.
Igniteui Angular Figma To App
IgniteUI/igniteui-angular
Builds Angular views from Figma designs with Ignite UI for Angular, supporting Indigo.Design kits, third-party kits, and plain frames.
Igniteui Angular Components
IgniteUI/igniteui-angular
Covers all non-grid Ignite UI for Angular UI components: application scaffolding and setup, form controls (inputs, combos, selects, date/time pickers, calendar, checkbox, radio, switch, slider)…
Related
Categories
Questions about Igniteui Angular Testing
What does Igniteui Angular Testing do?
Quick-reference for running Ignite UI for Angular test suites. Igniteui Angular Testing is an agent skill from IgniteUI/igniteui-angular. Quick-reference for running Ignite UI for Angular test suites.
When should I use Igniteui Angular Testing?
Igniteui Angular Testing fits situations like: an agent needs to run; understand the test infrastructure; building — use igniteui-angular-build instead; linting — use igniteui-angular-linting instead.
How do I install Igniteui Angular Testing in Claude Code?
Run `npx skills add IgniteUI/igniteui-angular --skill igniteui-angular-testing -a claude-code`. Or copy the skill folder (.agents/skills/igniteui-angular-testing in IgniteUI/igniteui-angular) into .claude/skills/igniteui-angular-testing in your project. Claude Code loads it when a task matches its description.
How do I install Igniteui Angular Testing in Codex?
Run `npx skills add IgniteUI/igniteui-angular --skill igniteui-angular-testing -a codex`. Or copy the skill folder (.agents/skills/igniteui-angular-testing in IgniteUI/igniteui-angular) into .agents/skills/igniteui-angular-testing in your project. Codex loads it when a task matches its description.
Can I use Igniteui Angular Testing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add IgniteUI/igniteui-angular --skill igniteui-angular-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/igniteui-angular-testing, .gemini/skills/igniteui-angular-testing, .github/skills/igniteui-angular-testing and .opencode/skills/igniteui-angular-testing in your project.
What does Igniteui Angular Testing need to run?
Going by SKILL.md and its folder, Igniteui Angular Testing needs the command-line tools its instructions call (npm). Our summary lists: Node.js.
Does Igniteui Angular Testing access the network?
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Igniteui Angular Testing safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Igniteui Angular Testing use?
Igniteui Angular Testing has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Igniteui Angular Testing use?
About 950 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Igniteui Angular Testing?
Skills that share tags, products or a category with Igniteui Angular Testing: Pre Commit (wellwelwel/poku, 1.2k stars), Cometchat Angular V5 Migration (cometchat/cometchat-skills, 129 stars), Stylelint (managedcode/dotnet-skills, 486 stars) and UI Only (OutThisLife/brooklyn-skills, 198 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Igniteui Angular Testing?
IgniteUI (a GitHub organization) maintains it in IgniteUI/igniteui-angular, which has 599 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 6, 2026.
Source: IgniteUI/igniteui-angular on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.