wilsonfreitas

Bulk PR reviewer for awesome-quant. Use when the user asks to review all open PRs, review unreviewed PRs, bulk review, or mentions "bprr". Reviews open PRs lacking the reviewed label and presents a summary before any merge/comment/label action.

Single PR reviewer for awesome-quant. Use when the user asks to review, validate, comment on, label, close, or merge one specific pull request that adds README.md entries. Triggers include "sprr", "review PR", "check PR", and "validate contribution".

Refresh tracked PyPI last-updated dates in awesome-quant README.md. Use when the user asks to update PyPI dates, refresh PyPI metadata, or run update-pypi-dates.

Bulk review all unreviewed pull requests for the awesome-quant curated list. Review all open PRs without the "reviewed" label in one session, then present a summary table for user selection before merging. Use this skill when asked to "bulk review", "review all prs", "bprr", or "review unreviewed".

Single PR reviewer. Review and validate pull requests that add new library entries to the awesome-quant README.md. Use this skill whenever the user asks to review PRs, check contributions, validate submissions, triage pull requests, or mentions anything about incoming entries or additions to the curated list. Also triggers for "review pr", "check prs", "merge contributions", "sprr", or any PR-related workflow in this repo.

Check PyPI projects for last updated dates and update README.md entries. Use this skill to keep PyPI project information current with latest release dates from PyPI. Run periodically to maintain up-to-date metadata on Python packages listed in awesome-quant.

Connect to BrasaDB's DuckDB database and execute SQL queries to explore Brazilian financial market data. Use this skill whenever the user asks to query, explore, analyze, or study data in the brasa database, asks about available datasets or tables, wants to run SQL queries against financial data, wants to create views or combine datasets for a specific application, or mentions DuckDB, BrasaDB, or SQL in the context of this project. Also trigger when the user asks questions that could be answered by querying the data — e.g., "what stocks are in IBOV?", "show me PETR4 prices", "what's the DI1 curve?", "help me create a view with these datasets", "I have datasets A and B, combine them for X".

Execute a previously-planned brasa Linear issue end-to-end: read the plan from the Implementation Plan Document, work through each step faithfully, tick checkboxes in that Document as they complete, maintain an append-only Execution Log comment with Findings, work on a per-issue git branch with one commit per task, run quality gates, merge to main, run gated Findings triage at close-out, and mark the issue Done. Use whenever the user says "execute WIL-X", "run the plan for WIL-X", "implement WIL-X", or otherwise wants to turn a planned issue into actual code changes — even if they don't say "execute".

Read the Design Document from a brasa Linear issue and produce an implementation plan stored as an `Implementation Plan` Document on the same issue (not a description section). Moves the issue to `Planned` on success. Use whenever the user says "plan WIL-X", "write the plan for WIL-X", or wants to turn an already-refined issue into an actionable plan.

Manage the Linear workflow for the brasa project: saving ideas as issues, and refining/planning issues using EnterPlanMode and updating them in Linear. Use this skill whenever the user mentions Linear, saving an idea, refining a ticket, or planning a feature — even if they don't explicitly say "Linear" but the context is clearly about brasa development tasks.

Refine a brasa Linear issue via brainstorm → grill → synthesize, persisting the result as a `Design` Document on the issue (not a description section). Moves the issue to `Refined` on success. Use whenever the user says "refine WIL-X", "brainstorm WIL-X", "design WIL-X", or wants to turn a brasa Linear issue into a reviewed design spec.

Write new brasa YAML templates from scratch or migrate legacy templates (with reader.function and handler-based fields) to the modern pipeline-based format. Use when the user asks to create a new template, write a template, migrate a legacy template, convert an old template, or work with YAML template definitions. Also trigger when the user mentions template creation, template migration, or refers to legacy/old templates.