jsuvic
UserConfigure Codex, Claude, and Tabnine to understand your project, follow its workflow, and respect its safety rules.
Categories
Indexed Skills (17)
grill-change
Use when a stakeholder request is rough, ambiguous, or underspecified and needs clarification before planning, writing a spec, or creating issues.
implement-next
Use after synthesis to dispatch the next ready task from the TASKS.md ledger through one subagent-driven implementation cycle, one task per invocation.
request-to-spec-issues
Use after a grill-change session is complete to turn the agreement record into an intent-first spec candidate and vertical TDD-ready issue briefs.
subagent-driven-change
Use when a scoped implementation can be delegated to an implementation subagent and then independently reviewed for spec compliance before code quality.
tdd-change
Use when changing behavior where a focused failing test or golden fixture must prove RED before implementation and GREEN after the minimal fix.
loop-docs-update
Use to run a bounded documentation drift scan, update, and re-verify loop that stops when docs match the code, on no diff, or on a repeated identical mismatch.
loop-implement-test-fix
Use to run a bounded implement, test, and fix loop that stops on green, on no diff, or on a repeated identical failure.
loop-review-patch-retest
Use to run a bounded review, patch, and retest loop that stops on green, on no diff, or on a repeated identical finding.
loop-sdd-cycle
Use to run a bounded spec, tests, implementation, and verify cycle that stops on green, on no diff, or on a repeated identical failure.
loop-security-patch-retest
Use to run a bounded security-review, patch, and retest loop that stops on green, on no diff, or on a repeated identical finding.
final-review
Use before handing off an implementation to compare the diff against the spec, tests, docs, contracts, and safety rules.
sdd-change
Use when implementing a meaningful repository change that requires an approved spec before code edits.
architecture-review
Review module boundaries, dependency direction, contracts, migration risk, and fit to the product architecture.
readability-review
Review naming, decomposition, control flow, duplication, comments, error-handling clarity, and unnecessary abstraction.
review-change
Use to review a proposed change for correctness, security-sensitive behavior, readability, tests, performance when relevant, architecture and contract impact, and generated-file drift.
security-review
Review exploit paths, secret exposure, unsafe permissions, injection, authentication and authorization, supply-chain risk, and data leakage.
test-review
Review missing cases, regression coverage, flaky patterns, fixture quality, edge cases, and behavior-versus-implementation testing.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.