Real-time web search using Playwright-controlled browser. Use this skill when you need current information, latest documentation, recent news, or any data beyond your knowledge cutoff (January 2025).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
테스트 설계, 취약점 진단, 품질 보증 (1.3만건)
Real-time web search using Playwright-controlled browser. Use this skill when you need current information, latest documentation, recent news, or any data beyond your knowledge cutoff (January 2025).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Help the user turn their Retentioneering ideas, friction reports, bug findings, or feature needs into high-quality upstream contributions: from capturing and validating the idea, through minimal reproductions and issue drafts, to preparing, testing, and submitting a pull request that follows this repository's conventions. Use when the user says they found a bug, wants a feature, wrote a workaround worth upstreaming, or asks how to contribute, open an issue, or make a PR to retentioneering-tools.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Prevent 此地无银三百两式 residue: finalize artifacts without echoing rejected session-only alternatives into labels, metadata, commits, PRs, or handoffs. Use after corrections or discarded proposals. Not for ordinary deletion, deprecation, migration, or exclusions materially required for safety, accuracy, compatibility, audit, quotation, or requested comparison.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematic root-cause debugging. Iron Law: no fixes without root cause investigation first. Four phases: Root Cause Investigation, Pattern Analysis (6 known patterns), Hypothesis Testing (3-strike rule), Implementation. Structured debug report output.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematically QA test a web application with browser-based bug fixing. Four modes: diff-aware (automatic on feature branches), full (systematic exploration), quick (30-second smoke test), regression (compare against baseline). Atomic bug-fix workflow with regression testing. Health scoring across 8 categories.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Headless Chromium CLI for QA testing and site dogfooding. 100-200ms per command after startup. Persistent state with cookies, tabs, sessions. Snapshot system with element refs. Navigate, interact, verify page state, take screenshots, check responsive layouts, test forms, handle dialogs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fully automated ship workflow: pre-flight, merge base, run tests, coverage audit, pre-landing review, design review, adversarial review, version bump, CHANGELOG generation, TODOS.md update, bisectable commits, push and PR creation, auto-sync docs via document-release.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Pre-landing PR review with two-pass checklist. Pass 1 critical: SQL safety, race conditions, LLM trust boundaries, enum completeness. Pass 2 informational: side effects, magic numbers, dead code, test gaps. Adversarial review auto-scaled by diff size. Scope drift detection.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Report-only QA — same browser-based testing as qa but documents bugs with screenshots and repro steps only, no code changes. Health score formula weighted across 8 categories. Outputs to .gstack/qa-reports/.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Eng manager-mode plan review. Scope challenge, architecture review, code quality review, detailed test coverage diagram, performance review. Produces test plan artifact for downstream QA. Optional cross-model outside voice.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans across functional, performance, and security testing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates Spring Boot 3.x configurations, creates REST controllers, implements Spring Security 6, sets up Spring Data JPA, and configures reactive WebFlux endpoints.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Builds security-focused full-stack web applications with integrated frontend and backend components implementing layered security including auth, validation, encoding, and parameterized queries.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Challenges ideas, plans, decisions, and proposals using structured critical reasoning as devil's advocate, pre-mortem, red team, or evidence audit.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Optimizes Active Record queries, implements Turbo Frames and Streams, configures Action Cable WebSockets, sets up Sidekiq workers, and writes RSpec test suites for Rails 7+.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Identifies security vulnerabilities, generates structured audit reports with severity ratings, and provides actionable remediation guidance for SAST, DevSecOps, and compliance.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Writes E2E tests with Playwright including test scripts, page objects, test fixtures, reporters, CI integration, API mocking, and visual regression testing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Asset naming and pipeline validation
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Autonomously validate that a task is complete and ready to ship — tests, build, and requirement checks
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Scan security advisories and vulnerability disclosures
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Multi-pass code review orchestration with parallel reviewers for quality, security, performance, and test coverage
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates python code that evaluates SageMaker models. Supports two evaluation types: LLM-as-Judge and Custom Scorer. Use when the user says "evaluate my model", "run a benchmark", "test model performance", "how did my model perform", "compare models", or other similar requests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze a software codebase for algorithmic complexity and performance hotspots, then propose or implement safe optimizations without breaking behavior. Use when Codex is asked to scan many files, find inefficient loops, nested iteration, repeated scans, costly rendering/recomputation, N+1 queries, avoidable O(n^2) or O(n) operations, or reduce complexity such as O(n^2) to O(n log n) / O(n), while preserving tests, APIs, outputs, and maintainability.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.