Найдите подходящую возможность для вашего агента.
Use this skill when writing Go tests with stretchr/testify, implementing TDD workflows, creating mocks, or organizing test suites. Covers assert vs require patterns, interface mocking, table-driven tests, and the red-green-refactor cycle.
Verify implementation completeness against spec and tasks. Use after implementation to ensure all tasks are complete, tests pass, and code meets quality standards before marking feature done.
Scans DAPR projects for security issues including plain-text secrets, missing ACLs, insecure configurations, and security best practice violations. Automatically triggers on component file modifications.
WHEN: User is writing Go code, asking about Go patterns, reviewing Go code, or asking questions like "what's the best way to..." in Go projects WHEN NOT: Non-Go languages, general questions unrelated to Go programming
Apply Go best practices, idioms, and conventions from golang.org/doc/effective_go. Use when writing, reviewing, or refactoring Go code to ensure idiomatic, clean, and efficient implementations.
Claude Code hook creation and configuration. PAI event-driven automation. USE WHEN: "create hook", "hook system", "modify hooks", "add hook"
Check for conflicts before dangerous operations. Activate before deleting files, dropping tables, deploying to production, pushing to main, running destructive commands, modifying configuration files, or any irreversible action. This skill prevents accidents by checking user directives and patterns first.
Use when implementing any feature or bugfix, before writing implementation code
Research Reba is the Guardian and QA. She validates everything - code from Gary, protocol changes from Peter, architectural reviews from Neo. She guards the IMMUTABLE sections of skills and ensures nothing merges without her sign-off. Detail-obsessed analyst who writes tests, maintains docs, and tears code apart in reviews. Invoke by mentioning Reba by name.
Write markdown content to file paths using the MCP markdown-writer server. Use when you need to save generated markdown content to a file, especially in contexts where (1) The Write tool is unavailable or restricted, (2) You need guaranteed atomic writes with verification, (3) Writing markdown files for documentation, reports, or research outputs, (4) An agent needs to persist markdown without user permission prompts.
Consolidate and improve evolved specs - identifies inconsistencies, removes redundancy, improves structure while maintaining feature coverage
Rapidly find and reclaim disk storage by identifying build artifacts, git garbage, temp files, and other space hogs. Use when disk is full or running low on space.
Archive a completed change and apply spec updates to the main specifications.
Autonomously audit the entire repository and update the main README with comprehensive, accurate documentation of the current codebase
Fast codebase search via WarpGrep (20x faster than grep)
Cleans and maintains Package.swift files in a Clean Architecture–oriented Swift project. Use when removing obsolete dependencies, refactoring module graphs, or enforcing architectural conventions encoded in Package.swift.
Generate structured changelogs for app releases from git history. Use when preparing releases, documenting changes, or creating version notes.
Write safe context expressions in Claude Code slash command files. Covers backtick expressions, find vs ls patterns, and commands that always exit 0. Use when creating slash commands, writing context sections with backtick expressions, or debugging command execution failures.
