lklimek
Publisher on askill
Secure programming best practices based on the OWASP Cheat Sheet Series. Use this skill whenever writing, reviewing, or discussing application security, input validation, authentication, authorization...
Security-focused review of a dependency update. Use when reviewing dependency bumps, library upgrades, or evaluating a new dependency.
Use for new projects, features, or major refactoring. Phases: Requirements → Architecture → TDD → Implementation → QA → Lessons Learned.
Severity classification for findings in code reviews, security audits, and quality assessments. Preload on agents that produce review findings to ensure consistent severity ratings.
Unified review report format for all finding-producing agents. Load when emitting or consuming review findings.
Python best practices — PEP 8, type hints, testing, error handling, code quality tools. Use when writing, reviewing, or discussing Python code.
Verify whether existing PR review comments have been addressed in code. Checks out the branch, verifies each comment against current code, resolves addressed threads, and produces a structured report....
Frontend best practices — TypeScript, React/Vue/Svelte, CSS, accessibility, testing. Use when writing, reviewing, or discussing frontend code.
Use when developing code. Universal rules for TDD, self-review, quality timing, review format, security. Preloaded on developers.
Use to autonomously handle peer review — request, wait, fix comments, push, repeat until resolved.
Use for typos or single-line fixes (≤20 lines). Phases: TDD → Implementation → QA → Lessons Learned.
Use for bug fixes or small changes (≤200 lines). Phases: Requirements → Architecture → TDD → Implementation → QA → Lessons Learned (lighter ceremony).
Save a pre-qualified memory. Handles scoping, dedup, and reports collection size.