Skip to content

Standardize agents with TemplateDotNetTool template#82

Merged
Malcolmnixon merged 2 commits intomainfrom
copilot/replace-agents-in-repo
Feb 11, 2026
Merged

Standardize agents with TemplateDotNetTool template#82
Malcolmnixon merged 2 commits intomainfrom
copilot/replace-agents-in-repo

Conversation

Copy link
Contributor

Copilot AI commented Feb 11, 2026

Pull Request

Description

Replaces SonarMark's custom agents with the standardized agent set from TemplateDotNetTool to align with DEMA Consulting's .NET tool patterns.

Changes

Removed agents (3):

  • documentation-writer.md
  • project-maintainer.md
  • software-quality-enforcer.md

Added agents (6, customized for SonarMark):

  • code-quality-agent.md - linting, static analysis, security
  • requirements-agent.md - requirements development, test coverage strategy
  • software-developer.md - production code, self-validation tests, literate programming
  • technical-writer.md - documentation, regulatory best practices
  • test-developer.md - unit/integration tests, AAA pattern
  • repo-consistency-agent.md - maintains alignment with TemplateDotNetTool

Key consideration: repo-consistency-agent.md intentionally preserves "TemplateDotNetTool" references throughout since its purpose is to keep SonarMark consistent with that template. Added explicit note to prevent future renaming.

Updated AGENTS.md:

  • Added "Available Specialized Agents" section
  • Updated agent invocation guidelines
  • Aligned requirements/testing language with template patterns

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update
  • Code quality improvement

Related Issues

N/A

Pre-Submission Checklist

Before submitting this pull request, ensure you have completed the following:

Build and Test

  • Code builds successfully: dotnet build --configuration Release
  • All tests pass: dotnet test --configuration Release
  • Code produces zero warnings

Code Quality

  • Code formatting is correct: dotnet format --verify-no-changes
  • New code has appropriate XML documentation comments
  • Static analyzer warnings have been addressed

Linting

  • Markdown linter passes: npx markdownlint-cli2 "**/*.md" "#node_modules"
  • Spell checker passes: npx cspell "**/*.{md,cs}" --no-progress
  • YAML linter passes: yamllint .

Testing

  • Added unit tests for new functionality
  • Updated existing tests if behavior changed
  • All tests follow the AAA (Arrange, Act, Assert) pattern
  • Test coverage is maintained or improved

Documentation

  • Updated README.md (if applicable)
  • Updated ARCHITECTURE.md (if applicable)
  • Added code examples for new features (if applicable)
  • Updated requirements.yaml (if applicable)

Additional Notes

Agent migration maintains template consistency while customizing project-specific references (e.g., SonarMark_* test naming vs TemplateTool_*).

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

  • https://storage.googleapis.com/chromium-browser-snapshots/Linux_x64/1108766/chrome-linux.zip
    • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node install.js (http block)

If you need me to access, download, or install something from one of these locations, you can either:


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Co-authored-by: Malcolmnixon <1863707+Malcolmnixon@users.noreply.github.com>
Copilot AI changed the title [WIP] Replace agents with those from TemplateDotNetTool Standardize agents with TemplateDotNetTool template Feb 11, 2026
Copilot AI requested a review from Malcolmnixon February 11, 2026 15:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants