GitQuuu
@GitQuuu
Public Skills
devops-github-actions
by GitQuuu
Three-branch strategy (development → staging → prod) with GitHub Actions - CI on pull requests, deploy per environment to Azure (App Service + Static Web Apps) or MonsterASP (Web Deploy), release and back-merge pull requests, branch rulesets, environment secrets and the bot identity for agent PRs. Use for CI/CD, pipelines, deployments, branch protection, releases, hotfixes, environments or hosting questions.
ado-deliver
by GitQuuu
Builds one approved Azure DevOps Task end to end with the agent team - picks the next Task tagged agent-ready (or a given id), claims it, creates a branch, runs fullstack-developer, tester and reviewer, then commits, pushes, opens a linked pull request and updates the work item. Use when the user says take the next task, deliver task 456, work the backlog, or similar.
ado-backlog
by GitQuuu
Conventions for running the QuGents agent team from an Azure DevOps (Scrum) backlog - work item types and fields, the agent tag workflow (agent-plan, agent-proposed, agent-ready, agent-working, agent-pr-open, needs-human), WIQL queries, branch/commit/PR naming and the Azure DevOps MCP tools. Loaded by ado-plan and ado-deliver; use directly when reading or updating backlog items for the agents.
dotnet-new-solution
by GitQuuu
Bootstraps a new solution for this stack from scratch with the dotnet and Angular CLIs - Web API (controllers) + Services + DataAccess + NUnit tests, SQLite (app.db) as the starting database, ASP.NET Core Identity with JWT, central package management, development configuration in appsettings.Development.json, and an Angular + PrimeNG + Tailwind app. Use when starting a new project or repo, or when asked how to set one up.
ado-plan
by GitQuuu
Plans Azure DevOps Product Backlog Items for the agent team - reads PBIs tagged agent-plan (or a given PBI id), has the planner agent break each into tasks, and creates them as child Tasks tagged agent-proposed for the product owner to approve. Use when the user says plan the backlog, plan PBI 123, break down this item, or similar.
angular-frontend
by GitQuuu
Conventions for Angular frontends (v20+, signals, standalone, zoneless/OnPush) built with PrimeNG components and Tailwind CSS that talk to a versioned ASP.NET Core API. Use when writing, placing or reviewing Angular code, e.g. a feature, component, page layout, PrimeNG table/form/dialog, route, API service, interceptor, or a spec file, or when wiring the frontend to a backend endpoint.
dotnet-identity-jwt
by GitQuuu
Authentication and authorization for the ASP.NET Core Web API with ASP.NET Core Identity (users, roles, passwords, lockout) and JWT bearer access tokens with rotating refresh tokens, plus the matching Angular auth store. Use when adding or changing login, registration, refresh/logout, roles, [Authorize] policies, the current-user id, token settings, or the frontend auth flow.
secure-code-review
by GitQuuu
Code-review checklist for correctness, security, robustness and performance in ASP.NET Core + EF Core APIs and Angular frontends, with severity levels and a findings format. Use when reviewing a diff, pull request or file for bugs and vulnerabilities (not layer structure, which the dotnet-n-layer skill covers).
dotnet-n-layer
by GitQuuu
Conventions for ASP.NET Core N-layer modular monoliths (API → Services → Data Access) with thin controllers and feature-sliced service modules (Controller → BLL → Service → Unit of Work/Repository). Use when writing, placing or reviewing C# in such a solution, e.g. adding an endpoint or use case, a controller action, BLL, service, repository, DTO, DI registration or Hangfire job.
dotnet-testing
by GitQuuu
Unit-testing conventions for .NET with NUnit 4, Arrange-Act-Assert and FakeItEasy, for N-layer solutions (Service, BLL, ResponseService, Hangfire jobs, repositories). Use when writing, fixing or reviewing C# tests, deciding what to test, or running dotnet test.