3.2K skills · sorted by relevance
Turn a recorded software failure into a draft bug report with timestamps, reproduction steps, expected and actual behavior, and relevant evidence. Separate visible symptoms from possible causes and remove sensitive details from shareable evidence.
Develop and test Windows-specific Screenpipe changes on a disposable Azure virtual machine. The workflow verifies native behavior, preserves logs and desktop video, and handles branch and pull request delivery when authorized.
Analyze a single discovery interview to understand actual behavior, needs, workarounds, and open questions. Receive a concise account tied to sources, separating participant actions from hypothetical intentions, interviewer suggestions, and interpretation.
Implement, fix, refactor, or remove repository code through a defined workflow. It connects each change to an acceptance criterion, checks effects on existing behavior, and guides focused testing, change review, and verification.
Guide changes to the published @kortix/sdk package with rules for preserving public APIs, writing failing tests before behavior changes, keeping the core independent of frameworks, and checking package installation. It also covers exports, streaming transport, and release version handling.
Test local web applications with Python scripts using Playwright, a browser automation tool. Verify interface behavior, investigate problems, capture screenshots, and inspect browser logs, with a helper that manages one or more application servers.
Draft or update GitHub pull request descriptions using the actual changes and related context. Explain the problem, changed behavior, and review concerns in plain language, including breaking changes and explicit issue-closing references when applicable.
Verify desktop UI changes through the Chrome DevTools Protocol, a connection for controlling the running app. Reproduce the user’s actual steps and compare screenshots, measured state, and console errors to establish evidence before and after a fix.
Implement a feature from its design and connect each covered user journey, a sequence of user actions, to a meaningful test. Run focused checks and assess the full change for effects on existing behavior.
Audit recovered bug reproduction tests before writing a fix or reviewing a pull request. Check that assertions reflect intended behavior, establish a valid failure on unfixed code, and verify the same test passes after the fix.
Verify Omnigent behavior through real user actions in an isolated environment. Use a feature map to cover relevant web, terminal, and CLI entry points, preserving recordings and other evidence for bug reproductions and fixes.
Investigate errors and unexpected behavior through reproduction, isolation, diagnosis, and a proposed fix. Receive a structured report covering the root cause, necessary code or configuration changes, and suggested tests to prevent the issue from returning.
Review a design or web page against WCAG 2.1 AA, an accessibility standard. Organize findings on contrast, keyboard access, forms, and screen reader behavior, with severity levels and practical recommendations for fixes.
Develop features and fix bugs by writing a behavior test first, observing its expected failure, and adding the minimum code needed to pass. Then clean up the code while keeping tests passing, applying this process where regression risk warrants it.
Interpret Culture Index behavioral profiles to understand individual traits, team balance, and possible strain from workplace adaptation. Use PDF or JSON data to inform hiring discussions, management approaches, onboarding plans, and conflict mediation.
Validate security patches by comparing vulnerable and patched code against exploit tests, related attack variants, and normal behavior. Produce reproducible logs showing remaining flaws, regressions, newly introduced security failures, and gaps that still need testing.
Assess a fixed code patch for behavior changes, regression risks, test coverage, and recovery options. Receive an evidence-based report and structured assessment indicating whether it is ready to merge and qualifies as an automatic merge candidate.
Build in-game changelogs that connect release notes and displayed versions to successful production deployments. Reconstruct supported history, integrate menu navigation and accessible controls, and verify version consistency and behavior on desktop and mobile.
Add and maintain Nexent Python unit tests with pytest. Isolate external dependencies, cover successful behavior, boundaries, and errors, and add regression assertions that detect fixed bugs. Review existing coverage and record test results separately from formal acceptance cases.
Test local web applications with Playwright, a browser automation tool. Write Python scripts to check interface behavior, inspect rendered pages, capture screenshots, and collect browser logs, with a helper that manages one or more application servers.
Make specific C# behavior testable by adding a minimal way to replace time, randomness, or other external dependencies. Preserve public APIs and production behavior, then run repeatable tests without real file access or waiting.
Refactor C#/.NET code through renaming, extraction, consolidation, and other structural changes while preserving behavior. Check compatibility beyond code references, including public APIs and serialized names, then validate with builds and relevant tests.
Move existing .NET 9 projects to .NET 10 by updating project settings and dependencies, fixing build errors, and reviewing behavior changes. Includes CI and Docker updates, followed by builds, tests, and security checks.
Upgrade an existing .NET 10 project to .NET 11 by updating framework targets and packages, fixing compatibility issues, reviewing runtime behavior changes, and verifying builds, tests, and deployment configuration.