Skip to content

πŸ” Duplicate Resource ReviewΒ #1867

@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.


πŸ†• New Findings

Group 1: Mentoring Juniors β€” Agent + Skill with Near-Identical Socratic Approach (re-surfaced from #1480)

  • Reviewed β€” these are intentionally separate
Resource Type Description
agents/mentoring-juniors.agent.md Agent Socratic mentor for junior developers. Guides through questions, never gives direct answers. Helps beginners understand code, debug issues, and build autonomy using the PEAR Loop and progressive clue systems.
skills/mentoring-juniors/SKILL.md Skill Socratic mentoring for junior developers and AI newcomers. Guides through questions, never answers. Progressive clue systems, teaching techniques, and success metrics.

Why flagged: Both share the same name (mentoring-juniors), same Socratic guiding approach (questions only, never direct answers), same target audience (junior devs), and similar progressive clue/hint systems. The core behaviour is packaged as both an agent and a skill. Previously flagged in #1076 and #1480, then inadvertently dropped from later reports without being formally accepted.


Group 2: Quality Playbook β€” Agent + Skill with Near-Identical Six-Phase Audit

  • Reviewed β€” these are intentionally separate
Resource Type Description
agents/quality-playbook.agent.md Agent Run a complete quality engineering audit on any codebase. Orchestrates six phases β€” explore, generate, review, audit, reconcile, verify β€” each in its own context window for maximum depth. Finds the 35% of real defects that structural code review alone cannot catch.
skills/quality-playbook/SKILL.md Skill Run a complete quality engineering audit on any codebase. Derives behavioral requirements, generates spec-traced functional tests, runs a three-pass code review, executes a multi-model spec audit (Council of Three), and produces a consolidated bug report with TDD-verified patches. Finds the 35% of real defects that structural code review alone cannot catch.

Why flagged: Both share the same name (quality-playbook), the same opening claim ("Run a complete quality engineering audit on any codebase"), and the distinctive "35% of real defects" statistic. They describe the same audit methodology packaged as an agent and a skill, with the skill providing more detailed step descriptions.


♻️ Unresolved from Previous Reviews

Groups 3–10: High-confidence pairs (previously flagged in #1793, unresolved)

Group 3: Power BI Expert Agents vs Power BI Best Practices Instructions β€” Cross-Type Cluster (previously reviewed β€” see #1793 Group 1)

  • Reviewed β€” these are intentionally separate
Resource Type Description
agents/power-bi-data-modeling-expert.agent.md Agent Expert Power BI data modeling guidance using star schema principles, relationship design, and Microsoft best practices
instructions/power-bi-data-modeling-best-practices.instructions.md Instruction Comprehensive Power BI data modeling best practices based on Microsoft guidance for creating efficient, scalable semantic models using star schema principles
agents/power-bi-dax-expert.agent.md Agent Expert Power BI DAX guidance using Microsoft best practices for performance, readability, and maintainability of DAX formulas
instructions/power-bi-dax-best-practices.instructions.md Instruction Comprehensive Power BI DAX best practices and patterns based on Microsoft guidance for creating efficient, maintainable, and performant DAX formulas
agents/power-bi-visualization-expert.agent.md Agent Expert Power BI report design and visualization guidance using Microsoft best practices for creating effective, performant, and user-friendly reports
instructions/power-bi-report-design-best-practices.instructions.md Instruction Comprehensive Power BI report design and visualization best practices based on Microsoft guidance for creating effective, accessible, and performant reports and dashboards

Why flagged: Three agent+instruction pairs covering the same Power BI sub-domains. Each pair shares 85%+ similar scope, differing only in resource type (agent = interactive expert, instruction = passive guidance).


Group 4: Implementation Plan Generation Agents β€” Identical Descriptions (previously reviewed β€” see #1793 Group 2)

  • Reviewed β€” these are intentionally separate
Resource Type Description
agents/planner.agent.md Agent Generate an implementation plan for new features or refactoring existing code.
agents/implementation-plan.agent.md Agent Generate an implementation plan for new features or refactoring existing code.

Why flagged: Both agents share a word-for-word identical description.


Group 5: Caveman Mode β€” Agent + Instruction with Identical Description (previously reviewed β€” see #1793 Group 3)

  • Reviewed β€” these are intentionally separate
Resource Type Description
agents/caveman-mode.agent.md Agent Terse, low-token responses. Minimal words, no fluff. Full capabilities preserved.
instructions/caveman-mode.instructions.md Instruction Terse, low-token responses. Minimal words, no fluff. Full capabilities preserved.

Why flagged: Word-for-word identical description. Same behavior, same directives. One applies passively (applyTo: '**'), the other is explicitly invoked.


Group 6: C#/.NET Janitor Cluster β€” Two Agents with Identical Descriptions + Universal Variant (previously reviewed β€” see #1793 Group 4)

  • Reviewed β€” these are intentionally separate
Resource Type Description
agents/csharp-dotnet-janitor.agent.md Agent Perform janitorial tasks on C#/.NET code including cleanup, modernization, and tech debt remediation.
agents/dotnet-upgrade.agent.md Agent Perform janitorial tasks on C#/.NET code including cleanup, modernization, and tech debt remediation.
agents/janitor.agent.md Agent Perform janitorial tasks on any codebase including cleanup, simplification, and tech debt remediation.

Why flagged: csharp-dotnet-janitor and dotnet-upgrade share a word-for-word identical description. janitor.agent.md broadens the same workflow to any language, potentially making both C#-specific agents redundant.


Group 7: Doublecheck β€” Agent + Skill with Identical Functionality (previously reviewed β€” see #1793 Group 5)

  • 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).
skills/doublecheck/SKILL.md Skill Three-layer verification pipeline for AI output. Extracts verifiable claims, finds supporting/contradicting sources, runs adversarial review for hallucination patterns.

Why flagged: Both describe the exact same three-layer verification pipeline for AI output. They differ only in resource type (agent vs skill).


Group 8: Gilfoyle Code Review β€” Agent + Instruction (previously reviewed β€” see #1793 Group 6)

  • Reviewed β€” these are intentionally separate
Resource Type Description
agents/gilfoyle.agent.md Agent Code review and analysis with the sardonic wit and technical elitism of Bertram Gilfoyle from Silicon Valley.
instructions/gilfoyle-code-review.instructions.md Instruction Gilfoyle-style code review instructions that channel the sardonic technical supremacy of Silicon Valley's most arrogant systems architect.

Why flagged: Same Gilfoyle persona, same code review domain. One performs active review sessions; the other passively applies the same style to all interactions.


Group 9: PRD β€” Agent + Skill (previously reviewed β€” see #1793 Group 7)

  • Reviewed β€” these are intentionally separate
Resource Type Description
agents/prd.agent.md Agent Generate a comprehensive Product Requirements Document (PRD) in Markdown, detailing user stories, acceptance criteria, technical considerations, and metrics.
skills/prd/SKILL.md Skill Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.

Why flagged: Same name (prd), same core purpose β€” generating PRD documents with user stories and acceptance criteria. Cross-type overlap (agent vs skill).


Group 10: MS-SQL DBA β€” Agent + Instruction (previously reviewed β€” see #1793 Group 8)

  • Reviewed β€” these are intentionally separate
Resource Type Description
agents/ms-sql-dba.agent.md Agent Work with Microsoft SQL Server databases using the MS SQL extension.
instructions/ms-sql-dba.instructions.md Instruction Instructions for customizing GitHub Copilot behavior for MS-SQL DBA chat mode.

Why flagged: The instruction explicitly targets use alongside the ms-sql-dba agent, creating heavily overlapping content for the same SQL Server DBA use case.


Groups 11–20: Broader clusters and multi-resource families (previously flagged in #1793, unresolved)

Group 11: Context7 β€” Agent + Instruction (previously reviewed β€” see #1793 Group 9)

  • Reviewed β€” these are intentionally separate
Resource Type Description
agents/context7.agent.md Agent Expert in latest library versions, best practices, and correct syntax using up-to-date documentation via Context7 MCP
instructions/context7.instructions.md Instruction Use Context7 for authoritative external docs and API references when local context is insufficient

Why flagged: Identical name, nearly identical scope (using Context7 MCP for documentation lookup), differing only in resource type.


Group 12: Markdown Accessibility β€” Agent + Instruction (previously reviewed β€” see #1793 Group 10)

  • Reviewed β€” these are intentionally separate
Resource Type Description
agents/markdown-accessibility-assistant.agent.md Agent Improves the accessibility of markdown files using five GitHub best practices
instructions/markdown-accessibility.instructions.md Instruction Markdown accessibility guidelines based on GitHub's 5 best practices for inclusive documentation

Why flagged: Both reference the same source (GitHub's 5 best practices for markdown accessibility). Identical domain and source material, cross-type overlap.


Group 13: Azure Functions vs Durable Functions C# β€” Near-Identical Instructions (previously reviewed β€” see #1793 Group 11)

  • Reviewed β€” these are intentionally separate
Resource Type Description
instructions/azure-functions-csharp.instructions.md Instruction Guidelines and best practices for building Azure Functions in C# using the isolated worker model
instructions/azure-durable-functions-csharp.instructions.md Instruction Guidelines and best practices for building Azure Durable Functions in C# using the isolated worker model

Why flagged: Descriptions are 95%+ identical (only difference is "Durable"), same applyTo patterns, closely overlapping content. Durable Functions is a specific extension of Azure Functions and may warrant a merged instruction.


Group 14: Dataverse Python β€” Advanced Patterns vs Production Code Skills (previously reviewed β€” see #1793 Group 12)

  • Reviewed β€” these are intentionally separate
Resource Type Description
skills/dataverse-python-advanced-patterns/SKILL.md Skill Generate production code for Dataverse SDK using advanced patterns, error handling, and optimization techniques.
skills/dataverse-python-production-code/SKILL.md Skill Generate production-ready Python code using Dataverse SDK with error handling, optimization, and best practices

Why flagged: Both generate production-ready Python code for the same Dataverse SDK with the same themes (error handling, retry logic, OData optimization). Descriptions differ only in wording.


Group 15: Spring Data Cosmos Migration Guides β€” Cassandra vs JPA (previously reviewed β€” see #1793 Group 13)

  • 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 describe a "step-by-step guide for converting Spring Boot X applications to use Azure Cosmos DB with Spring Data Cosmos" β€” differing only in source technology (Cassandra vs JPA). Same destination, likely shared structural content.


Group 16: Azure Logic Apps β€” Agent + Instruction Cross-Type Overlap (previously reviewed β€” see #1793 Group 14)

  • Reviewed β€” these are intentionally separate
Resource Type Description
agents/azure-logic-apps-expert.agent.md Agent Expert guidance for Azure Logic Apps development focusing on workflow design, integration patterns, and JSON-based Workflow Definition Language.
instructions/azure-logic-apps-power-automate.instructions.md Instruction Guidelines for developing Azure Logic Apps and Power Automate workflows with best practices for Workflow Definition Language (WDL), integration patterns, and enterprise automation

Why flagged: Both target Azure Logic Apps development with the same focus areas: Workflow Definition Language, integration patterns, and enterprise automation.


Group 17: Declarative Agents β€” Instruction + Skill Cross-Type Overlap (previously reviewed β€” see #1793 Group 15)

  • Reviewed β€” these are intentionally separate
Resource Type Description
instructions/declarative-agents-microsoft365.instructions.md Instruction Comprehensive development guidelines for Microsoft 365 Copilot declarative agents with schema v1.5, TypeSpec integration, and Microsoft 365 Agents Toolkit workflows
skills/declarative-agents/SKILL.md Skill Complete development kit for Microsoft 365 Copilot declarative agents with three comprehensive workflows (basic, advanced, validation), TypeSpec support, and Microsoft 365 Agents Toolkit integration

Why flagged: Both cover M365 Copilot declarative agent development with the same technologies: TypeSpec, M365 Agents Toolkit, schema v1.5.


Group 18: Prompt Engineering Safety β€” Instruction + Skill Cross-Type Overlap (previously reviewed β€” see #1793 Group 17)

  • Reviewed β€” these are intentionally separate
Resource Type Description
instructions/ai-prompt-engineering-safety-best-practices.instructions.md Instruction Comprehensive best practices for AI prompt engineering, safety frameworks, bias mitigation, and responsible AI usage
skills/ai-prompt-engineering-safety-review/SKILL.md Skill Comprehensive AI prompt engineering safety review and improvement prompt. Analyzes prompts for safety, bias, security vulnerabilities, and hallucination risks.

Why flagged: Both cover AI prompt engineering safety with the same focus areas (bias mitigation, safety frameworks, security).


Group 19: Code Tour β€” Agent + Skill Cross-Type Overlap (previously reviewed β€” see #1793 Group 19)

  • Reviewed β€” these are intentionally separate
Resource Type Description
agents/code-tour.agent.md Agent Expert agent for creating and maintaining VSCode CodeTour files with comprehensive schema support and best practices
skills/code-tour/SKILL.md Skill Use this skill to create CodeTour .tour files β€” persona-targeted, step-by-step walkthroughs that link to real files and line numbers.

Why flagged: Both create VSCode CodeTour .tour files for the same use cases. Core purpose is identical.


Group 20: Suggest Awesome Copilot Resources β€” Three Near-Identical Skills (previously reviewed β€” see #1793 Group 20)

  • Reviewed β€” these are intentionally separate
Resource Type Description
skills/suggest-awesome-github-copilot-agents/SKILL.md Skill Suggest relevant GitHub Copilot Custom Agents files from the awesome-copilot repository based on current repository context and chat history
skills/suggest-awesome-github-copilot-instructions/SKILL.md Skill Suggest relevant GitHub Copilot instruction files from the awesome-copilot repository based on current repository context and chat history
skills/suggest-awesome-github-copilot-skills/SKILL.md Skill Suggest relevant GitHub Copilot skills from the awesome-copilot repository based on current repository context and chat history

Why flagged: Three skills with nearly identical structure and wording β€” differing only in the resource type they suggest (agents vs instructions vs skills). Could potentially be a single parameterized skill.


Generated by Duplicate Resource Detector

Generated by Duplicate Resource Detector Β· ● 19.4M Β· β—·

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