Alex Schilling
Community@adschill
Alex Schilling's skill registry delivers disciplined software engineering practices: staged implementation, TDD enforcement, test quality assessment, and multi-tier code review for pull requests.
Agent Skills by Alex Schilling
Showing 7 vetted skills indexed across 1 GitHub repositories.
adschillstaged-implementation
Implements coding changes in engineer-approved stages with test-first execution and confirmation gates.
adschillqa-review
Reviews diffs, branches, and pull requests across correctness, security, performance, and style lanes.
adschilltest-quality
Assess test suites for coverage gaps, weak assertions, and flaky patterns.
adschilltdd-development
Enforces test-first workflow for code changes with focused failing tests and verification.
adschillpr-description-summary
Generates a concise bullet-list pull request description from the current branch diff.
adschillcomment-commentary
Analyzes GitHub pull-request review threads one at a time with evidence-based recommendations.
adschilllightweight-review
Reviews code diffs and pull requests for defects, regressions, and missing tests.
Frequently Asked Questions About Alex Schilling
FAQPage SchemaWhat tasks can I accomplish with Alex Schilling's skills?▼
You can implement code changes in engineer-approved stages, enforce test-driven development, assess test suites for coverage gaps and flaky patterns, generate concise PR descriptions, triage GitHub review threads, and run lightweight or full QA reviews of diffs, branches, and pull requests before merging.
Who should use these software engineering skills?▼
Software engineers, tech leads, and code reviewers who want disciplined change management benefit most. They suit developers practicing TDD, reviewers validating pull requests for correctness and maintainability, and teams needing structured stage-by-stage implementation with explicit human confirmation between steps.
How do the review skills differ from each other?▼
qa-review performs comprehensive pre-merge validation covering correctness, performance, and style across branches, tickets, or commit ranges. lightweight-review is a faster, high-signal pass focused on defects, regressions, and missing tests. comment-commentary instead works through individual GitHub inline review threads sequentially.
When are these skills triggered during development?▼
Skills activate only on explicit invocation or direct request: staged-implementation requires asking for incremental stages with pauses, qa-review requires a QA or merge-check request, and tdd-development applies to code changes where a failing test is written first, then the minimal implementation follows.
What prerequisites do these skills require?▼
The skills operate on existing codebases with tests, diffs, branches, or pull requests. comment-commentary requires GitHub pull request review threads or discussion URLs. No external services, licenses, or paid dependencies are specified in the manifest; they function as invocation-based engineering practice guides.