the signals and their derived score are provisional and subject to change.
validate manually before sharing.
6d3169bead57ea8d7ee307b988e1b7da485ddd91b8b896d6f5e7ceedd56607c7a72f2bade9f69f0dAuthored: 2 months ago (Wed, 10 Jun 2026 06:34:31 +0000)Match: Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>b50ea34e28dea1993af2dd0d0c222337fababc12Authored: 2 months ago (Mon, 8 Jun 2026 13:19:03 +0000)Match: Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>958a94d1398817c14c47fd1d64f8619d77464afaAuthored: 2 months ago (Mon, 8 Jun 2026 09:01:16 +0000)Match: Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>71c9b898cb4ca201db6efdaf1bfdead2ce30048aAuthored: 2 months ago (Sat, 6 Jun 2026 06:55:44 +0000)Match: Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>af91cf5aa8a5c6cd0a1a35a2a31d6df1e0743e11Authored: 3 months ago (Sat, 23 May 2026 23:59:03 +0000)Match: Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>f6c3aa6954f70ee196140c1e613daf9ebe42c58aAuthored: 3 months ago (Thu, 21 May 2026 14:28:26 +0000)Match: Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>0e091b55df80721a622c82a2cf39043047bfb5b4Authored: 3 months ago (Thu, 21 May 2026 07:06:29 +0000)Match: Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>ece8bae11241e579d7a675ee93b01242eee825d8Authored: 3 months ago (Wed, 20 May 2026 09:18:28 +0000)Match: Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>83b71b93c3220e0ebf66014b7e2bb5cd443d3a47Authored: 5 months ago (Tue, 31 Mar 2026 03:40:21 +0000)Match: Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>2450a60e12b9707f71d603092207485decc9d127Authored: 5 months ago (Tue, 17 Mar 2026 07:23:14 +0000)Match: Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>dd0077c320778a9c0c46de601aab6157f47ac06aAuthored: 5 months ago (Tue, 10 Mar 2026 01:36:57 +0000)Match: Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>c7882c14c4b25e37bdfdaa3ae1e539e740a85c1bAuthored: 6 months ago (Thu, 26 Feb 2026 09:41:37 +0000)Match: Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>142593a03c6c6ef856ebe04f381019f1f8ebd3dbAuthored: 6 months ago (Fri, 13 Feb 2026 02:57:03 +0000)Match: Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>3e4182eaa9851b661f005fabd299255371516794Authored: 6 months ago (Mon, 2 Feb 2026 15:15:17 +0000)Match: Copilot3e4182eaa9851b661f005fabd299255371516794Authored: 6 months ago (Mon, 2 Feb 2026 15:15:17 +0000)Match: Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>10b0c2d9143ebcb0687f5774c8c6d173acefec49Authored: 7 months ago (Thu, 8 Jan 2026 03:48:34 +0000)Match: Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>de0faf6dcb333ae430d1f5e85c95303c8081cbebAuthored: 8 months ago (Fri, 5 Dec 2025 08:51:02 +0000)Match: Copilotde0faf6dcb333ae430d1f5e85c95303c8081cbebAuthored: 8 months ago (Fri, 5 Dec 2025 08:51:02 +0000)Match: Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>760b58745a1b377d4008825a3d4c157d8a1bd590Authored: 8 months ago (Wed, 3 Dec 2025 05:40:34 +0000)Match: Copilot.cursorTool: cursor.cursorTool: cursor.junieTool: junie.junieTool: junie.claude/CLAUDE.mdTool: claude-code
You are an expert in TypeScript, Angular, and scalable web application development. You write functional, maintainable, performant, and accessible code following Angular and TypeScript best practices.
## TypeScript Best Practices
- Use strict type checking
- Prefer type inference when the type is obvious
- Avoid the `any` type; use `unknown` when type is uncertain
## Angular Best Practices
- Always use standalone components over NgModules
- Must NOT set `standalone: true` inside Angular decorators. It'.claudeTool: claude-code.claudeTool: claude-code.claudeTool: claude-code.claudeTool: claude-code.claudeTool: claude-code.claudeTool: claude-code.claudeTool: claude-code.gemini/GEMINI.mdTool: gemini
You are an expert in TypeScript, Angular, and scalable web application development. You write functional, maintainable, performant, and accessible code following Angular and TypeScript best practices.
## TypeScript Best Practices
- Use strict type checking
- Prefer type inference when the type is obvious
- Avoid the `any` type; use `unknown` when type is uncertain
## Angular Best Practices
- Always use standalone components over NgModules
- Must NOT set `standalone: true` inside Angular decorators. It'.geminiTool: gemini.geminiTool: geminiAGENTS.mdTool: agents-mdYou are an expert in TypeScript, Angular, and scalable web application development. You write functional, maintainable, performant, and accessible code following Angular and TypeScript best practices.
## TypeScript Best Practices
- Use strict type checking
- Prefer type inference when the type is obvious
- Avoid the `any` type; use `unknown` when type is uncertain
## Angular Best Practices
- Always use standalone components over NgModules
- Must NOT set `standalone: true` inside Angular decorators. It's.vscode/mcp.jsonTool: unspecified{
"servers": {
"angular-cli": {
"command": "npx",
"args": [
"-y",
"@angular/cli",
"mcp"
]
},
"eslint": {
"type": "stdio",
"command": "npx",
"args": [
"@eslint/mcp@latest"
]
}
}
}.cursor/mcp.jsonTool: unspecified{
"mcpServers": {
"angular-cli": {
"command": "npx",
"args": [
"-y",
"@angular/cli",
"mcp"
]
},
"eslint": {
"command": "npx",
"args": [
"@eslint/mcp@latest"
],
"env": {}
}
}
}.junie/mcp.jsonTool: unspecified{
"mcpServers": {
"angular-cli": {
"command": "npx",
"args": [
"-y",
"@angular/cli",
"mcp"
]
},
"eslint": {
"command": "npx",
"args": [
"@eslint/mcp@latest"
],
"env": {}
}
}
}.claude/.mcp.jsonTool: unspecified{
"mcpServers": {
"angular-cli": {
"command": "npx",
"args": [
"-y",
"@angular/cli",
"mcp"
]
},
"eslint": {
"command": "npx",
"args": [
"@eslint/mcp@latest"
],
"env": {}
}
}
}.agents/skills/create-pr/SKILL.mdTool: unspecified---
name: create-pr
description: Prepare or create an NG-ZORRO pull request using the repository template. Use when asked to open, draft, summarize, or create a PR for branch changes.
---
# NG-ZORRO Pull Request
Prepare a PR from the whole branch delta, not only the working tree or most recent commit. Inspect the current branch, remotes, its probable base, `git log <base>..HEAD`, and `git diff <base>...HEAD`. Use a user-specified base when present; otherwise infer it from repository state and flag uncerta.agents/skills/commit-msg/SKILL.mdTool: unspecified---
name: commit-msg
description: Generate a conventional commit message for staged NG-ZORRO changes. Use when asked for a commit message, a git commit title, or a summary of staged changes.
---
# NG-ZORRO Commit Message
Generate a commit message from the change that will actually be committed. Inspect `git status --short`, `git diff --cached --stat`, `git diff --cached`, and recent commit subjects before drafting it. If nothing is staged, say so; include unstaged changes only when the user asks.
Follow .agents/skills/version-release/SKILL.mdTool: unspecified---
name: version-release
description: NG-ZORRO/ng-zorro-antd repository release workflow. Use this skill whenever the user mentions 发版, 发布版本, release, release PR, stage-release, 升级版本号, changelog 发布准备, Azure publish, 部署官网, GitHub Release, or asks to prepare or execute an NG-ZORRO version release. This skill is project-specific and should be preferred over generic npm publish guidance.
---
# NG-ZORRO Version Release Guide
## Scope
This skill is for the real release pr.agents/skills/issue-reply/SKILL.mdTool: unspecified---
name: issue-reply
description: Triage and draft replies for NG-ZORRO GitHub issues. Use when asked to review, answer, label, close, or maintain issues.
---
# NG-ZORRO Issue Reply
First read the issue body, labels, linked issues or pull requests, and discussion. Classify the report as a reproducible bug, feature request, usage question, duplicate, or insufficient/invalid report. Check existing component documentation, APIs, demos, issues, and changelog entries before deciding that functionality is abse.agents/skills/changelog-collect/SKILL.mdTool: unspecified---
name: changelog-collect
description: Collect and draft NG-ZORRO changelog entries between releases or branches. Use when asked to compare release ranges, collect PR changes, or prepare changelog content before release staging.
---
# NG-ZORRO Changelog Collection
Use this skill to analyze a release range and prepare a reviewable changelog draft. Use `version-release` for version bumps, release branches, Azure publishing, and writing the final release files.
Establish the range from the requested tags .agents/skills/test-review/SKILL.mdTool: unspecified---
name: test-review
description: Review the value of NG-ZORRO tests. Use when asked whether a test should be kept, rewritten, or removed, especially for duplicated coverage or implementation-detail assertions.
---
# NG-ZORRO Test Review
Review tests for the public contract they protect; this is a review task, not a request to add tests or change production code. Inspect the relevant issue, documentation, demos, implementation, and nearby Vitest specifications as needed. Do not run tests unless the user .agents/skills/feature-sync/SKILL.mdTool: unspecified---
name: feature-sync
description: Sync an Ant Design React component or feature into NG-ZORRO. Use when checking or porting upstream APIs, behavior, styles, demos, documentation, or tests.
---
# Ant Design React Sync
Turn upstream functionality into an Angular implementation that fits NG-ZORRO's public API and maintenance model. Follow the repository's `AGENTS.md` first; it is the source of truth for the current Angular coding standards and global quality requirements.
## Establish the Upstream Contrac.agentsTool: unspecified.agentsTool: unspecified.agentsTool: unspecified.agentsTool: unspecified.agentsTool: unspecified.agentsTool: unspecified.agentsTool: unspecified.windsurfTool: devin.github/copilot-instructions.mdTool: github-copilot
You are an expert in TypeScript, Angular, and scalable web application development. You write functional, maintainable, performant, and accessible code following Angular and TypeScript best practices.
## TypeScript Best Practices
- Use strict type checking
- Prefer type inference when the type is obvious
- Avoid the `any` type; use `unknown` when type is uncertain
## Angular Best Practices
- Always use standalone components over NgModules
- Must NOT set `standalone: true` inside Angular decorators. It'none