[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CS9YZ000B8Y13GTT9AMSAG":3,"skill-same:01M7CS9YZ000B8Y13GTT9AMSAG":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7CS9YZ000B8Y13GTT9AMSAG","ponytail-review",null,"Quality review of a change: is the logic right, is it safe, does it hold under real load, is risky code tested, is it fast enough, and is every line needed. Reads the connected code, not only the diff. Each finding is explained in plain English. Use for \"review this\", \"code review\", \"review the last commit\", \"review my PR\", \"is this over-engineered\", \u002Fponytail-review.","Henrique1601\u002FSkiilsToIAs","Henrique1601","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F92006691?v=4","01M7CRXVT0GVXVK80JT1GR687S","Henrique Bezerra Dos Santos","01M7CRXVTN5Y8TMWJ1MDSKCQ1T",0,"MIT","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fai-agents\u002Fponytail-review\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ponytail-review\ndescription: >\n  Quality review of a change: is the logic right, is it safe, does it hold\n  under real load, is risky code tested, is it fast enough, and is every line\n  needed. Reads the connected code, not only the diff. Each finding is\n  explained in plain English. Use for \"review this\", \"code review\", \"review\n  the last commit\", \"review my PR\", \"is this over-engineered\", \u002Fponytail-review.\n---\n\nReview a change like the senior developer who will be paged when it breaks.\nOrder of importance: correct, safe, holds under load, tested, fast, lean.\nLean still matters: every extra line must be read, tested and fixed later.\nThis is a report the user asked for, so give it in full.\n\n## 1. Understand first\n\n- Review what the user names: uncommitted or staged changes, a branch, a PR\n  link, or files. Nothing named: the uncommitted changes, or the last commit\n  if there are none.\n- Read the diff, then the code it touches: callers of every changed function,\n  the functions it calls, the tests, the README.\n- Trace the real flow: where data comes in, what is stored, what goes out.\n- A change can break code it does not touch. When a signature, return value\n  or behavior changes, grep every caller.\n- Find the expected load in the repo (README, deploy config): one person\n  running a script, or many users and processes at once. Judge scale against\n  that, and say which load you assumed.\n\n## 2. Look for\n\n1. **Bug:** wrong result, crash, missed edge case (empty, zero, last item,\n   rounding, time zones), a caller broken by the change, a fix applied in one\n   caller while the shared function stays broken.\n2. **Risk:** security holes (injection, weak randomness, secrets, missing\n   checks on input from users), data loss (errors swallowed, writes in the\n   wrong order, no transaction).\n3. **Scale:** fine for one user, wrong for many: check-then-write races, the\n   same work done by every process, memory or lists that only grow, a query\n   per item, O(n^2) on big input, per-process state that must be shared.\n4. **Missing test:** risky new logic (a branch, a parser, money, security,\n   data writes, a bug fix) with no test that fails when it breaks. One good\n   test, not coverage.\n5. **Speed:** big slowdowns are problems. Small wins (work repeated in a hot\n   loop) are suggestions; some software counts every millisecond.\n6. **Lean:** code that should not exist or should be smaller.\n   - delete: dead code, unused options, speculative features\n   - reuse: the repo already has this helper (name the path)\n   - stdlib \u002F native: the standard library or platform already does it; a\n     new dependency for a few lines\n   - yagni: abstraction with one implementation, config nobody sets\n   - merge: near-copies that must change together\n   - split: one function doing several unrelated jobs, so it is hard to read\n     or test. Split by job, never by line count, and never into helpers that\n     exist only to make a function shorter.\n\n## 3. Check before you report\n\n- Every finding needs a concrete case: \"this input or situation leads to this\n  wrong result\". No case, no finding.\n- Re-read the lines and confirm: the caller exists, the value can really be\n  empty, the code really is unused.\n- A shortcut marked with a `shortcut:` (or older `ponytail:`) comment that names its limit is a\n  decision, not a finding, unless the expected load already crosses it.\n- Propose the smallest fix that works. Prefer fixes that delete code. Never\n  add layers, frameworks or config the problem does not need.\n- No style taste, no \"consider\", no vague worries.\n\n## 4. Output\n\nVery simple English: short sentences, everyday words. Explain a technical\nterm the first time you use it. The reader may never have seen this code.\n\nStart with `What this change does:` in two or three sentences.\n\nThen the findings in three groups, skip empty groups:\n- **Must fix:** bug, security, data loss, breaks at the expected load.\n- **Should fix:** risky code without a test, real slowness, duplication, a\n  function that mixes jobs, code that should not exist.\n- **Nice to have:** small speed-ups, shorter forms.\n\nNumber findings across all groups, so the user can say \"fix 2 and 5\".\nEvery finding has all four parts, each one or two short sentences:\n\n2. **Orders land on the wrong day** (`billing\u002Fclose_day.py:L40-52`)\n   - **What this is:** At midnight this job closes the day and bills all orders of that day.\n   - **Problem:** It takes \"today\" from the server clock, which runs in UTC. An order placed\n     at 00:30 in Berlin is billed on the day before.\n   - **Fix:** Compute the day once in the shop's time zone:\n     `datetime.now(ZoneInfo(\"Europe\u002FBerlin\")).date()`. One line, nothing else changes.\n   - **If we skip it:** Late orders show the wrong date, and accounting fixes them by hand.\n\nEnd with:\n- `Verdict: Ship.` or `Verdict: fix 1 and 3 first.`\n- `Lean: -\u003CN> lines possible.` when lean findings exist.\n- `Not checked:` one line, if something mattered and you could not check it.\n\nNothing found: `What this change does:`, then `Looks good. Ship.` and one line\non what you checked.\n\nLists findings, changes no code.\n","Review a change like the senior developer who will be paged when it breaks.\nOrder of importance: correct, safe, holds under load, tested, fast, lean.\nLean still matters: every extra line must be read, tested and fixed later.\nThis is a report the user asked for, so give it in full.\n\n## 1. Understand first\n\n- Review what the user names: uncommitted or staged changes, a branch, a PR\n  link, or files. Nothing named: the uncommitted changes, or the last commit\n  if there are none.\n- Read the diff, then the code it touches: callers of every changed function,\n  the functions it calls, the tests, the README.\n- Trace the real flow: where data comes in, what is stored, what goes out.\n- A change can break code it does not touch. When a signature, return value\n  or behavior changes, grep every caller.\n- Find the expected load in the repo (README, deploy config): one person\n  running a script, or many users and processes at once. Judge scale against\n  that, and say which load you assumed.\n\n## 2. Look for\n\n1. **Bug:** wrong result, crash, missed edge case (empty, zero, last item,\n   rounding, time zones), a caller broken by the change, a fix applied in one\n   caller while the shared function stays broken.\n2. **Risk:** security holes (injection, weak randomness, secrets, missing\n   checks on input from users), data loss (errors swallowed, writes in the\n   wrong order, no transaction).\n3. **Scale:** fine for one user, wrong for many: check-then-write races, the\n   same work done by every process, memory or lists that only grow, a query\n   per item, O(n^2) on big input, per-process state that must be shared.\n4. **Missing test:** risky new logic (a branch, a parser, money, security,\n   data writes, a bug fix) with no test that fails when it breaks. One good\n   test, not coverage.\n5. **Speed:** big slowdowns are problems. Small wins (work repeated in a hot\n   loop) are suggestions; some software counts every millisecond.\n6. **Lean:** code that should not exist or should be smaller.\n   - delete: dead code, unused options, speculative features\n   - reuse: the repo already has this helper (name the path)\n   - stdlib \u002F native: the standard library or platform already does it; a\n     new dependency for a few lines\n   - yagni: abstraction with one implementation, config nobody sets\n   - merge: near-copies that must change together\n   - split: one function doing several unrelated jobs, so it is hard to read\n     or test. Split by job, never by line count, and never into helpers that\n     exist only to make a function shorter.\n\n## 3. Check before you report\n\n- Every finding needs a concrete case: \"this input or situation leads to this\n  wrong result\". No case, no finding.\n- Re-read the lines and confirm: the caller exists, the value can really be\n  empty, the code really is unused.\n- A shortcut marked with a `shortcut:` (or older `ponytail:`) comment that names its limit is a\n  decision, not a finding, unless the expected load already crosses it.\n- Propose the smallest fix that works. Prefer fixes that delete code. Never\n  add layers, frameworks or config the problem does not need.\n- No style taste, no \"consider\", no vague worries.\n\n## 4. Output\n\nVery simple English: short sentences, everyday words. Explain a technical\nterm the first time you use it. The reader may never have seen this code.\n\nStart with `What this change does:` in two or three sentences.\n\nThen the findings in three groups, skip empty groups:\n- **Must fix:** bug, security, data loss, breaks at the expected load.\n- **Should fix:** risky code without a test, real slowness, duplication, a\n  function that mixes jobs, code that should not exist.\n- **Nice to have:** small speed-ups, shorter forms.\n\nNumber findings across all groups, so the user can say \"fix 2 and 5\".\nEvery finding has all four parts, each one or two short sentences:\n\n2. **Orders land on the wrong day** (`billing\u002Fclose_day.py:L40-52`)\n   - **What this is:** At midnight this job closes the day and bills all orders of that day.\n   - **Problem:** It takes \"today\" from the server clock, which runs in UTC. An order placed\n     at 00:30 in Berlin is billed on the day before.\n   - **Fix:** Compute the day once in the shop's time zone:\n     `datetime.now(ZoneInfo(\"Europe\u002FBerlin\")).date()`. One line, nothing else changes.\n   - **If we skip it:** Late orders show the wrong date, and accounting fixes them by hand.\n\nEnd with:\n- `Verdict: Ship.` or `Verdict: fix 1 and 3 first.`\n- `Lean: -\u003CN> lines possible.` when lean findings exist.\n- `Not checked:` one line, if something mattered and you could not check it.\n\nNothing found: `What this change does:`, then `Looks good. Ship.` and one line\non what you checked.\n\nLists findings, changes no code.\n",{"name":5,"description":7},"main","a73152352c0612252131e5cf84e91312a6cf17dc","ai-agents\u002Fponytail-review","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs","https:\u002F\u002Fgithub.com\u002FHenrique1601","https:\u002F\u002Fbezerraportifolio.netlify.app\u002F","Full Stack Developer | React, Next.js, TypeScript, Node.js & IA | Construindo produtos digitais e soluções SaaS","2026-11-15 02:56:04",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Henrique1601\u002FSkiilsToIAs --skill ponytail-review",{"tool":38,"command":39},"bunx","bunx skills add Henrique1601\u002FSkiilsToIAs --skill ponytail-review",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Henrique1601\u002FSkiilsToIAs --skill ponytail-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fai-agents\u002Fponytail-review\u002FSKILL.md",true,[],[47,54,61,69,76,83],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7E2ANBW9V6AVX5JXNCEAWF8","rag-architect-agent","Agente Arquiteto de RAG, Embeddings & Busca Vetorial. Especialista em design e implementação de pipelines de Retrieval-Augmented Generation de alta fidelidade: chunking semântico, modelagem pgvector no PostgreSQL (Neon\u002FSupabase), busca híbrida (cosseno + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fcustom-agents\u002Frag-architect-agent\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7E29KKF8R02ZRGYE2MJM67G","rag-architecture-patterns","Padrões arquiteturais e implementação de pipelines RAG (Retrieval-Augmented Generation) de alta fidelidade para qualquer projeto ou sistema. Cobre chunking semântico, embeddings, busca híbrida (pgvector + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fai-agents\u002Frag-architecture-patterns\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":65,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7CWRA8E3BJ7CPY8N8EG28J1","skill-repair","Use this to fix and re-install agent skills that have failed installation.\nThis skill provides the necessary context and permissions to surgically update\nthe `manifest.json` after a fix has been applied.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fskill-repair\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7CWR66FZP8FA47WVZ4Z2EXC","security-scan","Scan your Claude Code configuration (.claude\u002F directory) for security vulnerabilities, misconfigurations, and injection risks using AgentShield. Checks CLAUDE.md, settings.json, MCP servers, hooks, and agent definitions.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-scan\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7CWR0QPY58QPTR1P759TFNG","security-review","Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment\u002Fsensitive features. Provides comprehensive security checklist and patterns.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-review\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7CWQXCE40XWT4FZ3VWZFGDP","security-bounty-hunter","Hunt for exploitable, bounty-worthy security issues in repositories. Focuses on remotely reachable vulnerabilities that qualify for real reports instead of noisy local-only findings.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-bounty-hunter\u002FSKILL.md",[],[]]