Adds checks before an agent runs destructive commands and restricts file edits to a chosen directory. Offers separate or combined protection modes for production work, autonomous sessions, migrations, deployments, and data changes.
- Checking dangerous commands before production work
- Restricting edits to a specific directory
- Combining protections for autonomous agent sessions
affaan-m/ECC☆ 283.5KUpdated Oct 16, 2026
Develop and refactor Quarkus 3.x LTS services by writing tests first. Covers API responses, event handling, and asynchronous operations, with unit and integration tests plus coverage checks to show how much code is tested.
- Adding REST endpoints with tests first
- Reproducing bugs before fixing them
- Testing Apache Camel routes and event handling
affaan-m/ECC☆ 283.5KUpdated Oct 16, 2026
Write and run Perl tests with Test2::V0 or Test::More, replace external dependencies with controlled test substitutes, and measure coverage—the code exercised by tests. Guidance covers test-first development, failure diagnosis, and migration between testing modules.
- Writing Perl tests before implementation
- Migrating tests from Test::More to Test2::V0
- Testing API and database interactions in isolation
affaan-m/ECC☆ 283.5KUpdated Oct 16, 2026
Verify Quarkus services before pull requests or deployment through builds, code analysis, tests, coverage reports, and security scans. The workflow also checks native executables, containers, performance, health endpoints, configuration, and documentation.
- Checking a Quarkus service before a pull request
- Verifying refactoring or dependency upgrades
- Checking native executable compatibility
affaan-m/ECC☆ 283.5KUpdated Oct 16, 2026
Review prediction-market and trading-agent workflows before they handle account access, portfolio data, or trade planning. Produces structured findings on venue rules, data quality, security, privacy, and execution risks, with required safeguards and a safe next step.
- Review workflows before adding venue authentication
- Check how portfolio data and API keys are handled
- Review market data quality and source labels
affaan-m/ECC☆ 283.5KUpdated Oct 16, 2026
Write or repair React tests around user actions and visible results. Cover components and hooks, simulate network responses, check accessibility, and decide when real browser component tests or end-to-end tests across pages are needed.
- Adding behavior tests to React forms and components
- Testing custom hooks and asynchronous updates
- Simulating successful and failed API responses
affaan-m/ECC☆ 283.5KUpdated Oct 16, 2026
Build and review Python tests with pytest. Use reusable setup, simulated external services, and multiple input cases to check behavior, then measure coverage—the proportion of code exercised by tests—and follow a test-first development cycle.
- Writing tests before implementing a Python feature
- Sharing test setup through reusable fixtures
- Testing external API behavior with mocks
affaan-m/ECC☆ 283.5KUpdated Oct 16, 2026
Assess whether an application is ready for production using local files and authorized evidence. Reviews authentication, data, payments, and operations, then reports release blockers, prioritized fixes, and a readiness score without uploading repository contents to an external audit service.
- Checking application readiness before launch
- Reviewing release risks after a merge
- Finding production risks beyond passing CI checks
affaan-m/ECC☆ 283.5KUpdated Oct 16, 2026
Review Laravel authentication, permissions, database operations, forms, APIs, and production settings for security weaknesses. Use implementation examples to address unsafe input handling, exposed secrets, session risks, and insufficient access controls.
- Reviewing login and permission controls
- Checking database queries and input validation
- Reviewing forms for forged requests and unsafe scripts
affaan-m/ECC☆ 283.5KUpdated Oct 16, 2026
Build Laravel features test first with PHPUnit or Pest. Create tests for models, HTTP endpoints, authentication, and permissions, simulate external services, and measure coverage to see which code your tests exercise.
- Building Laravel features test first
- Testing API authentication and permissions
- Simulating payments, mail, and queues in tests
affaan-m/ECC☆ 283.5KUpdated Oct 16, 2026
Review safeguards for AI agents authorized to sign or send transactions. Cover malicious instructions hidden in external data, spending caps, pre-send simulation, automatic stop conditions, protected transaction routing, and private-key handling through layered security checks.
- Audit a trading bot with transaction authority
- Set per-transaction and daily spending limits
- Design pre-send checks and automatic stops
affaan-m/ECC☆ 283.5KUpdated Oct 16, 2026
Check a Laravel project before merging or deploying. Work through environment settings, code checks, tests and coverage, dependency security, database changes, caches, queues, and scheduled tasks, stopping when a required check fails.
- Checking a Laravel project before opening a pull request
- Verifying a major refactor or dependency upgrade
- Checking readiness for staging or production deployment
affaan-m/ECC☆ 283.5KUpdated Oct 16, 2026
Write Kotlin tests with Kotest and MockK using test-driven development, where tests come before implementation. Cover asynchronous code, check behavior across generated inputs, and use Kover reports to measure how much code the tests exercise.
- Adding tests to existing Kotlin code
- Developing new functions by writing tests first
- Testing coroutines and Flow behavior
affaan-m/ECC☆ 283.5KUpdated Oct 16, 2026
Review healthcare applications for exposure of patient and staff information. Classify sensitive data, design access restrictions for individual database rows, record data access and changes, and check common leaks through logs, URLs, and browser storage.
- Review code that handles patient records
- Design access restrictions between healthcare facilities
- Record access to and changes in sensitive data
affaan-m/ECC☆ 283.5KUpdated Oct 16, 2026
Helps build Go tests using a test-first workflow. Covers grouped test cases, HTTP response checks, performance benchmarks, fuzzing to explore generated inputs, and coverage reports showing which code was exercised by tests.
- Developing Go functions with tests written first
- Adding normal and error cases to existing tests
- Measuring execution time and memory allocations
affaan-m/ECC☆ 283.5KUpdated Oct 16, 2026
Write and organize F# unit and integration tests with xUnit, FsUnit, and Unquote. Use FsCheck to generate test inputs and check general rules, replace dependencies for isolated tests, and review test quality and coverage.
- Writing unit tests for F# code
- Checking general rules with generated inputs
- Testing ASP.NET Core API integration
affaan-m/ECC☆ 283.5KUpdated Oct 16, 2026
Review US healthcare software for HIPAA privacy and security concerns. The skill guides checks on protected health information, vendor agreements, minimum necessary access, and audit records, while directing implementation and specialized review to related skills.
- Reviewing AI-generated visit summaries for HIPAA concerns
- Checking patient data flows into analytics services
- Planning minimum necessary access and audit records
affaan-m/ECC☆ 283.5KUpdated Oct 16, 2026
Create rules that detect command patterns, file edits, prompts, or completion events and issue warnings or block matching actions. Configure checks for dangerous commands, sensitive files, and debug code using text patterns or multiple conditions.
- Blocking dangerous commands
- Warning about edits to sensitive files
- Detecting debug code during file edits
affaan-m/ECC☆ 283.5KUpdated Oct 16, 2026
Set up deployment checks for healthcare applications covering clinical decision support, patient information exposure, data integrity, workflows, and integrations. Block releases when critical tests fail, and flag lower workflow or integration pass rates for review.
- Checking an electronic health record application before deployment
- Testing changes to drug interactions or dose validation
- Checking patient data exposure after access control changes
affaan-m/ECC☆ 283.5KUpdated Oct 16, 2026
Check a Django application before a pull request or deployment. Review its environment, code quality, database changes, tests, vulnerabilities, and configuration, then produce a phased pass/fail report identifying issues that need fixes.
- Checking a Django pull request
- Reviewing database migrations
- Checking test coverage targets
affaan-m/ECC☆ 283.5KUpdated Oct 16, 2026
Review Solidity automated market makers, liquidity pools, and token swaps using security checklists and safer code examples. Check repeated calls during transfers, manipulated prices, share calculations, swap limits, and administrator permissions.
- Auditing liquidity pool contracts
- Reviewing deposit and withdrawal calculations
- Adding swap limits and deadlines
affaan-m/ECC☆ 283.5KUpdated Oct 16, 2026
Write and review C# and .NET tests using xUnit examples. Covers unit tests, mocks that replace dependencies, API and database integration tests, reusable test data, and project organization to check behavior and outcomes.
- Adding tests for C# services
- Testing ASP.NET Core APIs
- Checking database persistence
affaan-m/ECC☆ 283.5KUpdated Oct 16, 2026
Build Playwright tests that reproduce browser interactions, organize reusable page operations, and run checks automatically. Investigate tests that fail inconsistently, and save screenshots, videos, and execution traces to help diagnose failures.
- Testing login and search flows
- Organizing reusable page operations
- Investigating intermittent test failures
affaan-m/ECC☆ 283.5KUpdated Oct 16, 2026
Create and repair C++ tests, configure GoogleTest and CTest, and investigate failures or inconsistent results. The workflow also covers measuring which code tests exercise and using runtime checks to detect memory errors and race conditions.
- Writing C++ unit and integration tests
- Configuring GoogleTest and CTest
- Investigating tests that fail inconsistently
affaan-m/ECC☆ 283.5KUpdated Oct 16, 2026