GitHub

Review C#/.NET code for design patterns, separation of responsibilities, and common implementation issues. Receive actionable recommendations covering maintainability, testing, performance, and security without changing the code.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review design patterns in C#/.NET code
• Check separation of responsibilities before refactoring
• Identify dependencies that make testing difficult

Turn feature requests, refactoring work, package upgrades, or infrastructure changes into structured Markdown implementation plans. Each plan defines concrete tasks, dependencies, affected files, and validation criteria for execution by AI agents or people.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Plan the implementation of a new feature
• Break refactoring work into concrete tasks
• Prepare a package upgrade plan

Write consistent XML documentation comments for C# types and public members. Follow specific rules for summaries, parameters, return values, properties, exceptions, examples, and inherited documentation so API behavior and usage are clearly described alongside the code.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding documentation to public APIs
• Standardizing parameter and return value descriptions
• Documenting exception conditions and usage examples

Review C# asynchronous code and get suggestions for method names, return types, exception handling, concurrent tasks, and cancellation. Identify blocking calls and missing awaits, and choose patterns for long operations or sequences processed asynchronously.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing async/await usage
• Finding blocking calls and missing awaits
• Planning concurrent tasks and cancellation

Review an AI workflow across five areas: prompts, use of context, tools, system structure, and safety. Receive scores, specific findings, and prioritized actions to address quality and reliability problems.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check an AI workflow before production use
• Audit an existing agent for quality and reliability
• Prioritize fixes for workflow problems

Create a Spring Boot Java project skeleton with Maven, database connection settings, and Docker Compose services. Adds dependencies for API documentation and architecture tests, then checks the generated project with a Maven test command.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Start a Java 21 Spring Boot project
• Prepare local PostgreSQL, Redis, and MongoDB services
• Add API documentation and architecture test dependencies

Review and improve .NET/C# code against project conventions. Cover public API documentation, dependency injection for supplying services to classes, asynchronous operations, tests, configuration, logging, and input validation, including guidance for Semantic Kernel integrations.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review C# code against project conventions
• Improve XML documentation for public APIs
• Review asynchronous operations and dependency injection

Set up a dedicated workspace for a new workstream, with a journal and a folder for structured signals. Record its purpose, scope, and first steps so later sessions can pick up the context.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Starting a new workstream
• Giving a topic its own workspace and history
• Preparing context for the next session

Create a browser board for daily tasks and numeric goals, then track progress alongside conversations with an AI partner. Includes focus mode, gentle task carryover, progress notes, and a recap you can save at the end of the day.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Plan a manageable set of tasks for today
• Track reading pages or completed work sessions
• Focus on one task when getting started feels difficult

Prepare for an upcoming workday by combining Outlook meetings with open tasks and workspace context. Generate an HTML briefing with meeting preparation, scheduling conflicts, suggested priorities, and available time for learning and focused work.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prepare for tomorrow's meetings
• Spot overlapping meetings and scheduling issues
• Find time for learning and focused work

Compare specification requirements with the codebase and create GitHub issues for unmet requirements. Check existing issues for duplicates, then include requirement IDs, implementation guidance, context, and acceptance criteria in each new issue.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding requirements missing from an implementation
• Turning unmet requirements into GitHub issues
• Checking for duplicate issues before creating tasks

Turn official command documentation into a concise tldr page, an example-based command reference. Provide a command name and documentation URL to get five to eight common usage examples with consistent formatting and placeholders.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create a quick reference from a lengthy command manual
• Organize common command usage into five to eight examples
• Format command examples according to tldr conventions

Turn a business use case into a Dataverse solution using Python. Get table and relationship designs, implementation code, usage instructions, and recommendations for error recovery, logging, monitoring, and performance based on the expected workload.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Designing customer and document management solutions
• Building data migration or scheduled synchronization jobs
• Implementing order processing and approval workflows

Review Entity Framework Core code and get improvements for database models, queries, saving changes, and migrations, which track database schema changes. Covers performance, security, testing, and how database access code is organized.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review database models and relationships
• Improve slow queries and avoid repeated database calls
• Check migrations before production deployment

Write C# unit tests with TUnit using clear test structure, asynchronous checks, and multiple input cases. Get guidance on setup and cleanup, execution controls, test organization, and converting existing xUnit tests to TUnit.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Setting up a TUnit test project
• Testing one behavior with multiple input cases
• Organizing test setup and cleanup

Prepare raw credit data for pre-loan modeling by checking data quality and screening variables. Review missing values, predictive usefulness, stability, noise, and correlation, then export an Excel report with organization-level statistics and cleaning results.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prepare credit data before building a model
• Compare missing values and bad-sample rates across organizations
• Screen variables for usefulness, stability, and redundancy

Keep a short, persistent work journal so an agent can resume across sessions. Record completed work, current status, next steps, and unsuccessful attempts, then read the latest entry when restarting or summarize the work when closing it.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Recording progress at the end of a session
• Resuming work from the latest journal entry
• Saving key decisions and unsuccessful attempts

Turn defects found during Oracle-to-PostgreSQL migration into structured bug reports. Document expected and actual behavior, reproduction steps, severity, root causes, proposed changes, and validation on both databases so teams can act on the findings.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Documenting behavioral differences found during migration
• Organizing reproduction steps and test data
• Recording fixes, affected files, and validation steps

Provides prompts for assessing and planning .NET upgrades across multiple projects. Helps identify compatibility issues, order migration work, propose code and build pipeline changes, and prepare testing checklists, review guidance, and release documentation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Assessing project structure and dependency compatibility
• Planning an incremental upgrade with rollback checkpoints
• Reviewing deprecated APIs and NuGet package replacements

Create and edit draw.io files for workflows, system architecture, database relationships, and service interactions. Organize shapes and connectors, apply consistent styling, and check file structure so diagrams can be opened and edited in draw.io.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turn business processes into flowcharts
• Document system components and connections
• Diagram database tables and relationships

Document a local codebase with file references, architecture diagrams, and verified project commands. For legacy modernization, assess what still runs and create a phased migration plan with validation methods suited to each component’s current condition.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating an onboarding guide for a codebase
• Mapping system architecture and dependencies
• Planning a legacy system migration or rewrite

Create structured Markdown specifications that AI agents can read and use. Organize requirements, constraints, interfaces, acceptance criteria, and testing plans into a self-contained document with clear definitions and examples.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Writing specifications for AI-assisted implementation
• Defining requirements and acceptance criteria
• Documenting APIs and data contracts

Turn an existing GitHub Actions workflow into a structured specification for maintenance and AI reference. Document its purpose, triggers, job dependencies, inputs, outputs, permissions, and failure handling, focusing on expected behavior rather than implementation details.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Documenting an existing GitHub Actions workflow
• Reviewing job order and dependencies
• Organizing permissions and failure handling

Build and troubleshoot C#/.NET MCP servers that expose tools and information to AI agents. Guidance targets the official 2.x SDK and covers transport setup, authentication, interactive features, basic clients, and migration issues caused by changed defaults.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Build a C#/.NET MCP server
• Add tools, prompts, and resources
• Diagnose STDIO and HTTP connection errors