Skip to content

Latest commit

 

History

History
108 lines (75 loc) · 2.63 KB

File metadata and controls

108 lines (75 loc) · 2.63 KB

Summary

Type of Change

  • New Agent
  • New Prompt Template
  • Agent/Prompt Enhancement
  • Documentation Update
  • Bug Fix
  • Configuration/Setup Change
  • Other: _________

Changes Made

Files Added/Modified

  • path/to/file.md - Description of changes
  • path/to/another.md - Description of changes

Agent/Prompt Details

Agent/Prompt Name: example-name.agent.md
Purpose: Brief description of what this agent/prompt accomplishes
Triggers: How users invoke this (e.g., @agent-name, /command)
Dependencies: Required tools, permissions, or setup

Testing Done

  • Tested with GitHub Copilot
  • Verified prompt variables work correctly
  • Checked integration with existing agents
  • Tested edge cases and error scenarios
  • Validated against preferences.md configuration

Test Scenarios

  1. Scenario 1: Description and outcome
  2. Scenario 2: Description and outcome
  3. Error Handling: How it handles invalid inputs or missing data

Usage Examples

@agent-name do something with input

Expected Output:

[Description of what the agent would respond with]

Documentation Updates

  • Updated README.md if needed
  • Added/updated relevant documentation
  • Included usage examples
  • Updated CONTRIBUTING.md if new patterns introduced

Checklist

  • Code Quality

    • Follows existing patterns and conventions
    • YAML frontmatter is properly formatted
    • Markdown formatting is consistent
    • Variable placeholders use ${input:name:description} format
  • Functionality

    • Agent/prompt serves a clear, useful purpose
    • Integrates well with existing workflow
    • Handles errors gracefully
    • Respects user preferences where applicable
  • Documentation

    • Clear description and usage instructions
    • Examples are helpful and accurate
    • Any setup requirements are documented

Related Issues

Closes #123
Relates to #456

Additional Notes


For Reviewers:

  • Functionality works as described
  • Code follows project conventions
  • Documentation is clear and complete
  • Testing is adequate
  • Integration considerations addressed