fmacias/engineering
Reusable C# and .NET engineering workflows for review, implementation, testing, validation, and documentation.
Coordinate documentation changes affecting multiple repositories or information mirrored or referenced across repository boundaries, including navigation, publishing instructions, licensing text, and repository-boundary explanations.
Review proposed or implemented changes that cross module boundaries, change dependencies or references, move public or internal responsibilities, introduce abstractions or components, or may alter layering. Also use for explicit architecture-review requests. Assess against repository-declared architecture and design intent.
Create or improve precise English XML documentation when new C# APIs require documentation, substantially modified APIs need documentation updates, or the human explicitly requests API or code documentation cleanup. Keep edits within the affected scope.
Implement a bounded feature, bug fix, added behavior, or explicitly defined implementation task while preserving existing architecture, compatibility, and repository conventions.
Refactor existing code when the human explicitly requests refactoring, cleanup, simplification, or maintainability improvement without primarily requesting a new feature. Preserve intended behavior and respect repository and module boundaries.
Review C# changes involving multithreading, Tasks or async-await, concurrent collections, queues or schedulers, cancellation, retries, parallel execution, asynchronous observers or events, ordering guarantees, or shared mutable state. Provide focused concurrency analysis alongside normal C# review competence.
Review C# changes when the human explicitly requests a code review, staged-change review, commit or diff review, or assessment of C# changes without broad implementation changes. Analyze and report by default; make fixes only when explicitly requested with the review.
Review .NET changes affecting public classes, interfaces, members, DTOs or contracts, visibility, public static APIs, or signatures used across modules and packages. Identify unnecessary exposure, compatibility risks, and architectural leakage under declared repository policy.
Inspect staged Git changes and produce a concise, human-readable commit message when the human asks for a commit message, commit text, a summary of staged changes for commit, or a conventional or humanized description of the staged diff.
Add or update scoped .NET/C# tests when implementation, bug fixing, or refactoring requires test changes, or when the human explicitly asks for tests. Follow repository testing policy and verify the behavior relevant to the requested change.
Validate completed .NET code changes, refactoring, or implementation when validation is required. Use the repository's actual build, test, local packaging, and package-consumer workflow and report evidence and remaining gaps.