Skip to content

πŸ” Duplicate Resource ReviewΒ #1347

@github-actions

Description

@github-actions

Summary

How to Use This Report

Review each group below. If the resources are intentionally separate, check the box to mark them as accepted. These will be excluded from future reports.


Potential Duplicates

Group 1: MCP Server Expert Agents β€” 10 Language-Specific Agents with Near-Identical Purpose

  • Reviewed β€” these are intentionally separate
Resource Type Description
agents/csharp-mcp-expert.agent.md Agent Expert assistant for developing Model Context Protocol (MCP) servers in C#
agents/python-mcp-expert.agent.md Agent Expert assistant for developing Model Context Protocol (MCP) servers in Python
agents/typescript-mcp-expert.agent.md Agent Expert assistant for developing Model Context Protocol (MCP) servers in TypeScript
agents/go-mcp-expert.agent.md Agent Expert assistant for building Model Context Protocol (MCP) servers in Go using the official SDK.
agents/kotlin-mcp-expert.agent.md Agent Expert assistant for building Model Context Protocol (MCP) servers in Kotlin using the official SDK.
agents/java-mcp-expert.agent.md Agent Expert assistance for building Model Context Protocol servers in Java using reactive streams, the official MCP Java SDK, and Spring Boot integration.
agents/ruby-mcp-expert.agent.md Agent Expert assistance for building Model Context Protocol servers in Ruby using the official MCP Ruby SDK gem with Rails integration.
agents/swift-mcp-expert.agent.md Agent Expert assistance for building Model Context Protocol servers in Swift using modern concurrency features and the official MCP Swift SDK.
agents/php-mcp-expert.agent.md Agent Expert assistant for PHP MCP server development using the official PHP SDK with attribute-based discovery
agents/rust-mcp-expert.agent.md Agent Expert assistant for Rust MCP server development using the rmcp SDK with tokio async runtime

Why flagged: All 10 agents serve the same purpose ("Expert assistant for [developing/building] MCP servers in X") differentiated only by target language. The corresponding MCP Server Generator skills were accepted as intentionally separate (#981 Group 4), but these are agent-type resources covering MCP server development assistance β€” a separate resource type that warrants its own review. Additionally, many of these agents have direct companion instructions (see Group 2), raising the question of cross-type redundancy.


Group 2: MCP Server Instructions β€” 10 Language-Specific Instructions with Near-Identical Purpose

  • Reviewed β€” these are intentionally separate
Resource Type Description
instructions/go-mcp-server.instructions.md Instruction Best practices and patterns for building Model Context Protocol (MCP) servers in Go using the official github.com/modelcontextprotocol/go-sdk package.
instructions/java-mcp-server.instructions.md Instruction Best practices and patterns for building Model Context Protocol (MCP) servers in Java using the official MCP Java SDK with reactive streams and Spring integration.
instructions/kotlin-mcp-server.instructions.md Instruction Best practices and patterns for building Model Context Protocol (MCP) servers in Kotlin using the official io.modelcontextprotocol:kotlin-sdk library.
instructions/ruby-mcp-server.instructions.md Instruction Best practices and patterns for building Model Context Protocol (MCP) servers in Ruby using the official MCP Ruby SDK gem.
instructions/rust-mcp-server.instructions.md Instruction Best practices for building Model Context Protocol servers in Rust using the official rmcp SDK with async/await patterns
instructions/swift-mcp-server.instructions.md Instruction Best practices and patterns for building Model Context Protocol (MCP) servers in Swift using the official MCP Swift SDK package.
instructions/typescript-mcp-server.instructions.md Instruction Instructions for building Model Context Protocol (MCP) servers using the TypeScript SDK
instructions/php-mcp-server.instructions.md Instruction Best practices for building Model Context Protocol servers in PHP using the official PHP SDK with attribute-based discovery and multiple transport options
instructions/csharp-mcp-server.instructions.md Instruction Instructions for building Model Context Protocol (MCP) servers using the C# SDK
instructions/python-mcp-server.instructions.md Instruction Instructions for building Model Context Protocol (MCP) servers using the Python SDK

Why flagged: All 10 instructions provide "best practices for building MCP servers in X" differentiated only by target language. Each also has a corresponding Expert Agent (Group 1), making the agent+instruction pair for each language a potential cross-type redundancy. See also Group 1 for the related agents.


Group 3: GitHub Copilot SDK Instructions β€” 4 Language-Specific Instructions with Identical Structure

  • Reviewed β€” these are intentionally separate
Resource Type Description
instructions/copilot-sdk-csharp.instructions.md Instruction This file provides guidance on building C# applications using GitHub Copilot SDK.
instructions/copilot-sdk-go.instructions.md Instruction This file provides guidance on building Go applications using GitHub Copilot SDK.
instructions/copilot-sdk-nodejs.instructions.md Instruction This file provides guidance on building Node.js/TypeScript applications using GitHub Copilot SDK.
instructions/copilot-sdk-python.instructions.md Instruction This file provides guidance on building Python applications using GitHub Copilot SDK.

Why flagged: All 4 instructions share identical description structure ("This file provides guidance on building X applications using GitHub Copilot SDK.") and cover the same Copilot SDK topic for different languages. Same pattern as the accepted MCP Server Generator skills, but these are instructions β€” merits a review decision.


Group 4: Doublecheck β€” Agent + Skill with Near-Identical Functionality

  • Reviewed β€” these are intentionally separate
Resource Type Description
agents/doublecheck.agent.md Agent Interactive verification agent for AI-generated output. Runs a three-layer pipeline (self-audit, source verification, adversarial review) and produces structured reports with source links for human review.
skills/doublecheck/SKILL.md Skill Three-layer verification pipeline for AI output. Extracts verifiable claims, finds supporting or contradicting sources via web search, runs adversarial review for hallucination patterns, and produces a structured verification report with source links for human review.

Why flagged: Both resources describe the exact same three-layer verification pipeline for AI output, differ only in resource type (agent vs skill). This is a strong cross-type duplication signal β€” one may be redundant or they may serve complementary use cases.


Group 5: Implementation Plan β€” Agent + Skill Cross-Type Overlap

  • Reviewed β€” these are intentionally separate
Resource Type Description
agents/implementation-plan.agent.md Agent Generate an implementation plan for new features or refactoring existing code.
skills/create-implementation-plan/SKILL.md Skill Create a new implementation plan file for new features, refactoring existing code or upgrading packages, design, architecture or infrastructure.

Why flagged: Both resources create implementation plans for new features or refactoring. Note: the related agents group (planner.agent.md, plan.agent.md, task-planner.agent.md) is being tracked in open issue #1264 Group 2 β€” this specifically flags the agent-vs-skill cross-type overlap which is a separate dimension not covered there.


Group 6: Polyglot Test Agents β€” 8 Sub-Agents in the Same Pipeline

  • Reviewed β€” these are intentionally separate
Resource Type Description
agents/polyglot-test-generator.agent.md Agent Orchestrates comprehensive test generation using Research-Plan-Implement pipeline.
agents/polyglot-test-researcher.agent.md Agent Analyzes codebases to understand structure, testing patterns, and testability. Identifies source files, existing tests, build commands, and testing framework. Works with any language.
agents/polyglot-test-planner.agent.md Agent Creates structured test implementation plans from research findings. Organizes tests into phases by priority and complexity. Works with any language.
agents/polyglot-test-implementer.agent.md Agent Implements a single phase from the test plan. Writes test files and verifies they compile and pass. Calls builder, tester, and fixer agents as needed.
agents/polyglot-test-builder.agent.md Agent Runs build/compile commands for any language and reports results. Discovers build command from project files if not specified.
agents/polyglot-test-linter.agent.md Agent Runs code formatting/linting for any language. Discovers lint command from project files if not specified.
agents/polyglot-test-tester.agent.md Agent Runs test commands for any language and reports results. Discovers test command from project files if not specified.
agents/polyglot-test-fixer.agent.md Agent Fixes compilation errors in source or test files. Analyzes error messages and applies corrections.

Why flagged: All 8 agents share the "Polyglot Test" prefix and work together as a pipeline. They are likely intentionally separate sub-agents (each handling a distinct phase), but their tight coupling and shared naming convention warrants a review to confirm they are meant to coexist as an agentic workflow rather than being consolidated into fewer agents.


Group 7: ColdFusion Instructions β€” CFC vs CFM File Types

  • Reviewed β€” these are intentionally separate
Resource Type Description
instructions/coldfusion-cfc.instructions.md Instruction ColdFusion Coding Standards for CFC component and application patterns
instructions/coldfusion-cfm.instructions.md Instruction ColdFusion cfm files and application patterns

Why flagged: Both instructions cover ColdFusion coding standards and application patterns. They target different file types (.cfc components vs .cfm templates), but both describe "ColdFusion … application patterns." Could potentially be merged into a single ColdFusion instruction.


Group 8: Spring Boot to Azure Cosmos DB Migration Instructions β€” Two Source Databases, Same Target

  • Reviewed β€” these are intentionally separate
Resource Type Description
instructions/convert-cassandra-to-spring-data-cosmos.instructions.md Instruction Step-by-step guide for converting Spring Boot Cassandra applications to use Azure Cosmos DB with Spring Data Cosmos
instructions/convert-jpa-to-spring-data-cosmos.instructions.md Instruction Step-by-step guide for converting Spring Boot JPA applications to use Azure Cosmos DB with Spring Data Cosmos

Why flagged: Both instructions are "Step-by-step guides for converting Spring Boot X applications to use Azure Cosmos DB with Spring Data Cosmos" β€” identical structure and migration target, differing only in source data layer (Cassandra vs JPA). Different enough to be intentionally separate, but flagged for awareness.


Group 9: .NET MAUI vs .NET WPF Instructions β€” Same Pattern

  • Reviewed β€” these are intentionally separate
Resource Type Description
instructions/dotnet-maui.instructions.md Instruction .NET MAUI component and application patterns
instructions/dotnet-wpf.instructions.md Instruction .NET WPF component and application patterns

Why flagged: Both instructions share identical description structure (".NET X component and application patterns"). They target different UI frameworks (MAUI vs WPF), so they're likely intentionally separate, but the near-identical descriptions and overlapping component/application guidance scope warrants confirmation.


Group 10: Database Administrator Agents β€” PostgreSQL vs MS-SQL Same Template

  • Reviewed β€” these are intentionally separate
Resource Type Description
agents/postgresql-dba.agent.md Agent Work with PostgreSQL databases using the PostgreSQL extension.
agents/ms-sql-dba.agent.md Agent Work with Microsoft SQL Server databases using the MS SQL extension.

Why flagged: Both agents share an identical description template ("Work with X databases using the X extension.") targeting different database engines. Note: ms-sql-dba.agent.md is also flagged in open issue #1264 Group 6 for overlap with its companion instruction β€” this specifically flags the agent-to-agent pairing as a new dimension.


Group 11: Java Version Upgrade Instructions β€” Extended Family (New Member)

  • Reviewed β€” these are intentionally separate
Resource Type Description
instructions/java-11-to-java-17-upgrade.instructions.md Instruction Comprehensive best practices for adopting new Java 17 features since the release of Java 11.
instructions/java-17-to-java-21-upgrade.instructions.md Instruction Comprehensive best practices for adopting new Java 21 features since the release of Java 17.
instructions/java-21-to-java-25-upgrade.instructions.md Instruction Comprehensive best practices for adopting new Java 25 features since the release of Java 21.

Why flagged: java-17-to-java-21-upgrade and java-21-to-java-25-upgrade were previously accepted as intentionally separate in #981 Group 8. This group now includes the newly added java-11-to-java-17-upgrade instruction, which follows the exact same pattern. Flagging to confirm the same "intentionally separate" decision applies to the new addition.


Group 12: Arch Linux β€” Agent + Instruction + Triage Skill Triple Overlap

  • Reviewed β€” these are intentionally separate
Resource Type Description
agents/arch-linux-expert.agent.md Agent Arch Linux specialist focused on pacman, rolling-release maintenance, and Arch-community workflows.
instructions/arch-linux.instructions.md Instruction Guidance for Arch Linux administration, pacman workflows, and rolling-release best practices.
skills/arch-linux-triage/SKILL.md Skill Triage and resolve Arch Linux issues with pacman, systemd, and rolling-release breakages.

Why flagged: Three resource types (agent, instruction, skill) all covering Arch Linux administration with pacman and rolling-release workflows. The Linux Expert Agents+Instructions pairs are flagged in open #1264 Group 9, but this specifically highlights the three-way cross-type overlap for Arch Linux including the triage skill β€” a broader overlap pattern than previously flagged. Similar three-way overlaps exist for CentOS, Debian, and Fedora distributions.


Generated by Duplicate Resource Detector

Generated by Duplicate Resource Detector Β· β—·

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions