torikhayes
Community@torikhayes
torikhayes provides spec-driven development, QA testing, and security review skills for .NET microservices teams using spec-kit, Playwright, and EF Core.
Agent Skills by torikhayes
Showing 34 vetted skills indexed across 1 GitHub repositories.
speckit-checklist
Generate requirements-quality checklists for spec-kit feature specifications.
qa-team
Runs QA validation workflows and test health checks for branches and features.
review-tests
Reviews test coverage and test quality for new or changed code.
qa-dotnet
Runs and analyzes .NET unit and functional tests across test projects.
speckit-scripttest
Generate Bash test scripts from spec-kit test plan markdown files using parallel sub-agents.
speckit-constitution
Create and update project constitution files while syncing dependent spec-kit templates.
security-code-review
Reviews code for bugs and vulnerabilities and persists findings into structured reports.
speckit-implement
Executes implementation plans by processing tasks defined in tasks.md.
security-cve-review
Inventory NuGet and container dependencies, query OSV.dev, and assess CVE reachability.
sync-skills
Audit and bridge skill parity between Claude skills and GitHub Copilot prompts.
code-review
Reviews code changes and pull requests for quality, security, correctness, and style issues.
speckit-runtests
Executes shell-scripted integration tests for the active feature spec and reports pass/fail results.
speckit-taskstoissues
Convert spec-kit tasks into dependency-ordered GitHub issues via the GitHub MCP server.
save-session
Saves the current session state to memory for later resumption.
run-unit-tests
Runs the four eShop unit test projects that require no live infrastructure.
speckit-clarify
Identifies underspecified areas in feature specs and records targeted clarification answers.
speckit-plan
Generates implementation plans and design artifacts from feature specifications using spec-kit templates.
run-full-suite
Discovers and runs all speckit shell test suites across feature specs, then prints a consolidated cross-spec summary.
speckit-analyze
Analyze spec.md, plan.md, and tasks.md for inconsistencies, gaps, and constitution violations.
qa-coverage
Analyzes test coverage to identify untested code paths and missing test scenarios.
security-report
Regenerates and displays the consolidated security-review findings report across code, dependency, and adversarial reviews.
update-context
Syncs .github/context/ documentation files after code changes by executing a shared agent workflow.
local-setup
Guides developers through local setup, build, and run steps for the eShop .NET Aspire project on macOS.
continue-session
Resumes prior work by loading the saved session workflow from a shared prompt file.
Frequently Asked Questions About torikhayes
FAQPage SchemaWhat tasks can I accomplish with torikhayes's skills?▼
You can run the full spec-kit lifecycle (specify, clarify, plan, tasks, implement, analyze), generate and execute shell-based integration tests, run .NET unit and Playwright E2E tests, perform static security code reviews, scan dependencies against OSV.dev, and manage EF Core migrations and seed data.
Who are these skills designed for?▼
They target .NET developers and QA engineers working on the eShop microservices solution, plus teams practicing spec-driven development with GitHub's spec-kit. Specialist subagents cover C# code review, test coverage analysis, and adversarial runtime testing against loopback instances.
What prerequisites are required to use the spec-kit skills?▼
Spec-kit skills require a project initialized with the .specify/ directory structure. Test execution skills additionally require a generated test-plan.md and spec-integration-tests/run-all.sh. The .NET QA skills assume the eShop solution, while local-setup targets macOS with Homebrew, Colima, and the dotnet SDK.
How do the security review skills work together?▼
Three capabilities feed one report: static code review for bugs and vulnerabilities, CVE review cross-referencing NuGet and Aspire components against OSV.dev, and adversarial testing against a loopback URL. Findings can be acknowledged, linked as duplicates, and consolidated via the security-report skill.
How do session and context management skills support daily development?▼
save-session checkpoints progress to memory, continue-session resumes it later, and new-session archives and starts fresh. The update-context skill syncs .github/context/ documentation after code changes by diffing against origin/main, keeping architecture docs current before pull requests.