Results for “find”

Helps find and analyze competitors to imitate using a five-filter method, focusing on profitability and feasibility while eliminating personal bias.

Create and open a new desk in the workshop. Sets up the folder structure, initial journal, and desk identity so the next session that sits down finds the trail.

Design search experiences that help users find what they need, recover from failure, and refine results.

Runs five parallel review agents on code changes, validates findings, triages them, and applies approved fixes after confirmation.

Runs an adversarial code review with two blind judges analyzing the same code from opposing perspectives to find flaws before production.

Reviews local branch changes for bugs, security vulnerabilities, and code quality issues, using a structured checklist and verification process.

Verifies test effectiveness by introducing small bugs into production code and running the test suite to find weak or missing tests.

Audits code quality against a shared contract, producing structured findings and blocking pipeline phases on critical issues without modifying code.

Reviews pull request diffs for correctness, security, maintainability, and test coverage, providing severity-ranked findings and a close-out recommendation.

Token-optimized structural code search using tree-sitter AST parsing. Use instead of reading full files when you need to understand code structure, find functions, or explore a codebase efficiently.

Intelligently organizes files and folders by understanding context, finding duplicates, and suggesting better organizational structures. Use when user wants to clean up directories, organize downloads, remove duplicates, or restructure projects.

Intelligently organizes files and folders by understanding context, finding duplicates, and suggesting better organizational structures. Use when user wants to clean up directories, organize downloads, remove duplicates, or restructure projects.

Find brand products that should be added to an existing article. Compares the article's current product mentions to the brand-config product list and proposes natural insertion points.

Intelligently organizes files and folders by understanding context, finding duplicates, and suggesting better organizational structures. Use when user wants to clean up directories, organize downloads, remove duplicates, or restructure projects.

Ensures skills are invoked before any response, including clarifying questions, and establishes how to find and use skills.

Finds, inspects, and compares .NET project templates by resolving natural-language descriptions to ranked template matches with pre-filled parameters.

Runs a deeper code review with the GLM-5 model via glm-review, validates findings against the actual code, and reports only confirmed issues.

Interactive knowledge graph analysis. Routes natural language questions to graph scripts, interprets results in domain vocabulary, and suggests concrete actions. Triggers on "/graph", "/graph health", "/graph triangles", "find synthesis opportunities", "graph analysis".

Use when adapting academic findings for a public audience (op-ed, social post, podcast) and the simplification must stay evidence-faithful, avoid overclaiming, respect embargoes, and disclose AI assistance.

Find and analyze arbitrage opportunities across prediction markets like Polymarket and Kalshi. Use when you need to match equivalent markets, compare prices, and verify whether a spread looks actionable.

Use when the user wants to use the UCP CLI to find, compare, buy, or track products from online merchants, or to set up and troubleshoot the local UCP profile required for merchant-scoped operations. Covers global catalog search ("find me X under $Y"), named-merchant transactions ("buy this from Z.com"), order tracking, `ucp profile init`, `ucp doctor`, carts, checkout, orders, and UCP setup/help. Falls back to merchant-hosted handoff when direct in-protocol checkout isn't available.

Query a pre-indexed codebase via CLI to understand structure, find symbols, assess change impact, debug failures, and evaluate PR risk.

Investigating bugs via root cause analysis, reproduction steps, and impact assessment. Investigation-only — finds why bugs occur and where to fix them, no code. Use when a bug needs RCA before a fix.

Systematically find and fix bugs using proven debugging techniques, tracing from symptoms to root cause, implementing fixes, and preventing regression.

Performs structured code reviews of git branches, tracking findings in a living document and optionally running deep architectural analysis with subagents.

Runs a multi-perspective review of a pull request, including code quality, tests, and potential silent failures, then reports findings ranked by severity.

Reviews local branch changes for bugs, security vulnerabilities, and code quality issues, producing a prioritized report with severity ratings and concrete fixes.

Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.

Analyze complex systems through stocks, flows, and feedback loops to find high-leverage interventions. For organizational, environmental, social, and technical systems exhibiting circular causality. NOT for linear problems or simple cause-effect chains.

Analyzes production code to find gaps in existing tests by reasoning about hypothetical mutations and checking whether tests would catch them.

Runs Semgrep static analysis to find bugs and security vulnerabilities, with guidance on installation, rule selection, custom rule writing, and CI/CD integration.

Launches four parallel adversarial review agents covering security, scope, fidelity, and test gaps, then synthesizes findings into a ranked verdict for plans or feature branches.

Reviews staged and unstaged code changes for security vulnerabilities, code quality issues, and adherence to project conventions, reporting findings by severity.

Runs three parallel reviewers to find code reuse, quality, and efficiency issues in a diff, then applies safe fixes and reports risky ones.

Finds architectural friction in a codebase and proposes deep-module refactors to improve testability and AI-navigability, informed by the domain glossary and ADRs.

SLURM EDF job must use marker names from CHANNELNAMES.txt for output files. Trigger: EDF output naming, SLURM job producing CH#_edf.tif instead of marker names, downstream _find_edf_file failures