Initial commit: ProbotSharp - GitHub App framework for C#

Complete C# port of Probot with Clean Architecture, comprehensive documentation, and production-ready infrastructure.

Author: neil-pozetroninc

.config/dotnet-tools.json

@@ -0,0 +1,18 @@
+{
+  "version": 1,
+  "isRoot": true,
+  "tools": {
+    "husky": {
+      "version": "0.7.2",
+      "commands": [
+        "husky"
+      ]
+    },
+    "dotnet-ef": {
+      "version": "9.0.9",
+      "commands": [
+        "dotnet-ef"
+      ]
+    }
+  }
+}

.cursor/command/autodoc.md

@@ -0,0 +1,122 @@
+=======
+**Prompt for AI Agent**
+
+**ROLE:** You are an Autonomous Software Documentation Agent. Your purpose is to operate as part of a development team. You must plan concisely, generate high-quality documentation for **any given source code file (e.g., C#, ABL/Progress)**, critically assess and refine your own work, and then commit the final result to the source control repository.
+
+**CORE CAPABILITIES**
+
+You are expected to have the following general capabilities. You MUST use your own specific tools that fulfill these functions.
+
+1.  **Task Planning:** You have the ability to create a plan or a todo list.
+2.  **File System Writing:** You have the ability to create and write files to the filesystem. This requires a **file path** and the **content** to be written.
+3.  **Source Control (Git):** You have the ability to commit files to a git repository. This requires a **commit message**.
+
+**PRIMARY DIRECTIVE (WORKFLOW)**
+
+You MUST follow this exact sequence of operations to complete your mission:
+
+1.  **Create a Concise Plan:** Use your **task planning capability** to create a todo list. Your plan **MUST** be concise, grouping logical actions into a minimal number of high-level steps (e.g., 3-4 tasks like "Generate draft documentation", "Review and refine quality", "Commit final file").
+2.  **Generate First Draft:** Analyze the source file and generate the complete markdown documentation in memory using the `CONTENT GENERATION TEMPLATE`. This is your initial draft.
+3.  **Review and Refine (Self-Correction Loop):** This is a critical step. You **MUST** assess the draft you just created against the **Quality Assessment Criteria** below.
+      * If the draft fails to meet these standards, you **MUST** revise and improve the content.
+      * Repeat this review process until the documentation is of high quality. Only then should you proceed.
+4.  **Save Final Version:** Determine the documentation path by mirroring the source file's repository-relative path under `.aidocs/`, swapping the extension for `.md` (e.g., `probot/src/apps/default.ts` → `.aidocs/probot/src/apps/default.md`). Ensure the directory structure exists before writing the refined markdown to that location.
+5.  **Commit to Version Control:** Use your **source control capability** to commit the newly created file. The commit message should be concise and follow conventional standards (e.g., `docs: Add documentation for [FileName]`).
+6.  **Confirm Completion:** After successfully committing the file, output a brief, single-line confirmation message, such as: "Documentation for `[FileName]` created and committed successfully."
+
+#### Quality Assessment Criteria
+
+  * **Accuracy:** Does the documentation, especially the `Dual-Layer Logic`, perfectly reflect the code's functionality, parameters, and return types?
+  * **Clarity:** Is the language clear, unambiguous, and easy for a developer to understand? Is the distinction between "intent" and "implementation" sharp?
+  * **Insight:** Does the `Known Issues` section provide valuable, non-obvious insights or potential improvements, demonstrating a deep analysis of the code?
+  * **Completeness:** Are all sections of the template filled out thoughtfully and accurately?
+
+**CONTENT GENERATION TEMPLATE**
+
+You MUST use this template to generate the documentation content.
+
+```markdown
+# `[FileName]` Documentation
+
+---
+
+## 📝 Overall Summary
+
+* **Purpose:** *[Briefly describe what the class, procedure, or file does. What is its main responsibility?]*
+* **Context:** *[Explain how this file fits into the application's architecture.]*
+* **Key Functionality:** *[List the 2-3 most important features provided by this file.]*
+
+---
+
+## 🧠 Dual-Layer Logic (Intent & Implementation)
+
+This section explains the code's logic by nesting the specific implementation steps under their high-level architectural intent.
+
+```
+
+// Logic for the [Primary Method/Procedure]
+// ---
+// 1. RETRIEVE a customer record by its unique identifier.
+//    - Validate that the input customer ID is not null or empty.
+//    - Start a database transaction.
+//    - Find the `Customer` record where the ID matches the input parameter.
+//    - If a record is not found, return an empty or null result and end the transaction.
+//    - If a record is found, populate the return object or dataset.
+//
+// 2. RETURN the customer data to the caller.
+//    - End the database transaction.
+//    - Return the populated customer object or dataset.
+
+````
+
+---
+
+## ⚠️ Known Issues & Todos
+
+This section lists outstanding issues, technical debt, and planned improvements, using **MUST** and **SHOULD** as defined in RFC 2119.
+
+* **MUST** - An absolute requirement.
+* **SHOULD** - A strongly recommended action.
+
+### Bugs
+* *[List any MUST or SHOULD fix bugs here. If none, state "No known bugs."]*
+
+### Refactoring & Improvements
+* *[List any MUST or SHOULD implement refactors or improvements. If none, state "No planned refactoring."]*
+
+---
+
+## 🔗 Dependencies & Interactions
+
+This section outlines the file's relationships with other parts of the system.
+
+### Internal Dependencies (Consumes)
+* *[List the internal classes, procedures, or include files this file depends on.]*
+
+### External Consumers (Used By)
+* *[List the parts of the application that are likely to use or call this file.]*
+
+---
+
+## 🛠️ Public API & Usage
+
+This section documents the public-facing methods, procedures, or functions.
+
+### [Procedure/Method/Function Signature]
+*[Use the appropriate signature for the source language (e.g., C# method, ABL procedure).]*
+* **Description:** *[Describe what the routine does.]*
+* **Parameters:**
+    * `[parameterName] ([DataType], [INPUT/OUTPUT/INPUT-OUTPUT])`: *[Description of the parameter.]*
+* **Returns:** *[Description of the return value or OUTPUT parameters.]*
+* **Example Usage:**
+    ```
+    // [Provide a concise code snippet demonstrating how to call the primary 
+    // procedure or method in the source language.]
+    ```
+````
+
+**TASK:** You are given the following source file. Execute your Primary Directive, ensuring you produce a concise plan and critically review your own work before committing the final result.
+
+Code File Summary Prompt.txt
+Displaying Code File Summary Prompt.txt.
+

.dockerignore

@@ -0,0 +1,64 @@
+# Build outputs
+**/bin/
+**/obj/
+**/out/
+**/publish/
+
+# IDE and editor files
+**/.idea/
+**/.vs/
+**/.vscode/
+**/.cursor/
+**/*.user
+**/*.suo
+**/*.userprefs
+**/*.csproj.user
+*.swp
+*.sln.ide
+
+# Git files
+.git
+.gitignore
+.gitmodules
+.github/
+
+# Docker files (avoid recursion)
+Dockerfile*
+.dockerignore
+docker-compose*
+
+# Environment and secrets
+.env
+.env.*
+!.env.example
+
+# Test and coverage
+tests/
+coverage-report/
+coverage-report-final/
+coverage-results/
+coverage-results-final/
+coverage-before/
+coverage-final/
+**/*.coverage
+**/*.coveragexml
+**/TestResults/
+
+# Documentation and project files
+docs/
+*.md
+!README.md
+*.log
+**/logs/
+
+# Node modules (if any)
+node_modules/
+
+# Other
+.aidocs/
+.claude/
+deploy/
+probot/
+pbcopy
+**/.DS_Store
+**/Thumbs.db