[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C7GD90TAAMZV1EGFWS6C11":3,"skill-same:01M7C7GD90TAAMZV1EGFWS6C11":45},{"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":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7C7GD90TAAMZV1EGFWS6C11","self-review",null,"The implementer's own review: one reviewer sub-agent runs three axes over the diff since the session's start (Standards, Spec, Correctness) and reports findings back. Report-only, never edits code, runs once per implement-loop.","ShehabMohamedGamal\u002Fsimple-laravel","ShehabMohamedGamal","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F83552041?v=4","01M7C79TF94SZ9036Z0Y5G9JQ8","Shehab","01M7C79TFV0WDW2DAMGB1JSKA6",1,"MIT","https:\u002F\u002Fgithub.com\u002FShehabMohamedGamal\u002Fsimple-laravel\u002Fblob\u002Fmain\u002Fsimple\u002F.agents\u002Fskills\u002Fself-review\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: self-review\ndescription: \"The implementer's own review: one reviewer sub-agent runs three axes over the diff since the session's start (Standards, Spec, Correctness) and reports findings back. Report-only, never edits code, runs once per implement-loop.\"\n---\n\nThree-axis review of the working diff against a fixed point the caller supplies:\n\n- **Standards**: does the code conform to this repo's documented coding standards?\n- **Spec**: does the code faithfully implement the originating ticket \u002F spec?\n- **Correctness**: does the code contain bugs, and can its tests catch them?\n\nOne reviewer sub-agent runs all three axes in a single pass, so each axis benefits from the context the previous ones build, then this skill presents the report. The review is report-only: findings go back to the implementer, who fixes them in the implement-loop fix rounds.\n\nThe issue tracker should have been provided to you. If `docs\u002Fagents\u002Fissue-tracker.md` is missing, tell the user to run `\u002Fsetup-ae-harness`.\n\n## Process\n\n### 1. Pin the fixed point\n\nWhatever the caller said is the fixed point (a commit SHA, branch name, tag, `main`, `HEAD~5`, etc.). The implement-loop skill passes the commit the session started from. If nothing was supplied, ask for it.\n\nCapture the diff command once: `git diff \u003Cfixed-point>` (working tree against the fixed point, so the session's uncommitted work is included). Also note the list of commits via `git log \u003Cfixed-point>..HEAD --oneline`.\n\nBefore going further, confirm the fixed point resolves (`git rev-parse \u003Cfixed-point>`) and the diff is non-empty. A bad ref or empty diff should fail here, not inside the reviewer.\n\n### 2. Identify the spec source\n\nLook for the originating spec, in this order:\n\n1. The ticket the implementer is working, via `bd show \u003Cid>` and the workflow in `docs\u002Fagents\u002Fissue-tracker.md`.\n2. A path the caller passed as an argument.\n3. A spec file under `docs\u002F`, `specs\u002F`, or `.scratch\u002F` matching the branch name or feature.\n4. If nothing is found, the reviewer reports \"no spec available\" on the Spec axis.\n\n### 3. Identify the standards sources\n\nAnything in the repo that documents how code should be written, such as `CODING_STANDARDS.md` or `CONTRIBUTING.md`.\n\nOn top of whatever the repo documents, the Standards axis always carries the **smell baseline** below: a fixed set of Fowler code smells (_Refactoring_, ch.3) that applies even when a repo documents nothing. Two rules bind it:\n\n- **The repo overrides.** A documented repo standard always wins; where it endorses something the baseline would flag, suppress the smell.\n- **Always a judgement call.** Each smell is a labelled heuristic (\"possible Feature Envy\"), never a hard violation. Like any standard here, skip anything tooling already enforces.\n\nEach smell reads *what it is* → *how to fix*; match it against the diff:\n\n- **Mysterious Name**: a function, variable, or type whose name doesn't reveal what it does or holds. → rename it; if no honest name comes, the design's murky.\n- **Duplicated Code**: the same logic shape appears in more than one hunk or file in the change. → extract the shared shape, call it from both.\n- **Feature Envy**: a method that reaches into another object's data more than its own. → move the method onto the data it envies.\n- **Data Clumps**: the same few fields or params keep travelling together (a type wanting to be born). → bundle them into one type, pass that.\n- **Primitive Obsession**: a primitive or string standing in for a domain concept that deserves its own type. → give the concept its own small type.\n- **Repeated Switches**: the same `switch`\u002F`if`-cascade on the same type recurs across the change. → replace with polymorphism, or one map both sites share.\n- **Shotgun Surgery**: one logical change forces scattered edits across many files in the diff. → gather what changes together into one module.\n- **Divergent Change**: one file or module is edited for several unrelated reasons. → split so each module changes for one reason.\n- **Speculative Generality**: abstraction, parameters, or hooks added for needs the spec doesn't have. → delete it; inline back until a real need shows.\n- **Message Chains**: long `a.b().c().d()` navigation the caller shouldn't depend on. → hide the walk behind one method on the first object.\n- **Middle Man**: a class or function that mostly just delegates onward. → cut it, call the real target direct.\n- **Refused Bequest**: a subclass or implementer that ignores or overrides most of what it inherits. → drop the inheritance, use composition.\n\n### 4. Spawn one reviewer sub-agent\n\nLaunch the three-axis review sub-agent once, resolved from the agents section of `docs\u002Fagents\u002Fregistry.md` (default: `reviewer`), with `REVIEW_AXIS` covering all three axes. Its prompt should include:\n\n- The full diff command and commit list.\n- The list of standards-source files you found in step 3, **plus the smell baseline from step 3** pasted in full (the sub-agent has no other access to it).\n- The path or fetched contents of the spec, or an explicit \"no spec available\".\n\nThe Correctness axis owns its own brief; the sub-agent's definition carries it. Do not paste a copy here.\n\n### 5. Present the report\n\nPresent the report under `## Standards`, `## Spec`, and `## Correctness` headings, verbatim or lightly cleaned. Do **not** merge or rerank findings across axes: the axes are deliberately separate (see _Why three axes_).\n\nEnd with a one-line summary: total findings per axis, and the worst issue _within each axis_ (if any). Don't pick a single winner across axes: that's the reranking the separation exists to prevent.\n\n### 6. Deterministic checks (advisory)\n\nBefore presenting, read the `report: docs-coverage` output from `composer verify`. If verification has not run, ask the implementer to run it from the profile directory.\n\nReport missing required declaration docblocks as advisory Standards-axis findings. The coverage summary is context, not a finding. Review the changed declarations against `.ai\u002Frules\u002Fphp-docblocks.md` for meaningful prose, method contracts, and retry behavior that the script cannot judge. Docs coverage remains report-only and never blocks the change on its own.\n\nTest-shape scope: tests sit at recorded seams; use `tdd` for test design and profile rules for verification policy.\n\n## Why three axes\n\nA change can pass two axes and fail the third:\n\n- Code that follows every standard and implements the ticket, but breaks on an edge case → **Standards pass, Spec pass, Correctness fail.**\n- Code that follows every standard and handles its edge cases, but implements the wrong thing → **Standards pass, Spec fail, Correctness pass.**\n- Code that does exactly what the ticket asked, in a shape the repo rejects → **Spec pass, Correctness pass, Standards fail.**\n\nReporting them separately stops one axis from masking another. The single sub-agent keeps the context shared: a spec gap found on the Spec axis is evidence for the Correctness axis, and a confirmed bug on the Correctness axis can excuse a Standards judgement call.\n","Three-axis review of the working diff against a fixed point the caller supplies:\n\n- **Standards**: does the code conform to this repo's documented coding standards?\n- **Spec**: does the code faithfully implement the originating ticket \u002F spec?\n- **Correctness**: does the code contain bugs, and can its tests catch them?\n\nOne reviewer sub-agent runs all three axes in a single pass, so each axis benefits from the context the previous ones build, then this skill presents the report. The review is report-only: findings go back to the implementer, who fixes them in the implement-loop fix rounds.\n\nThe issue tracker should have been provided to you. If `docs\u002Fagents\u002Fissue-tracker.md` is missing, tell the user to run `\u002Fsetup-ae-harness`.\n\n## Process\n\n### 1. Pin the fixed point\n\nWhatever the caller said is the fixed point (a commit SHA, branch name, tag, `main`, `HEAD~5`, etc.). The implement-loop skill passes the commit the session started from. If nothing was supplied, ask for it.\n\nCapture the diff command once: `git diff \u003Cfixed-point>` (working tree against the fixed point, so the session's uncommitted work is included). Also note the list of commits via `git log \u003Cfixed-point>..HEAD --oneline`.\n\nBefore going further, confirm the fixed point resolves (`git rev-parse \u003Cfixed-point>`) and the diff is non-empty. A bad ref or empty diff should fail here, not inside the reviewer.\n\n### 2. Identify the spec source\n\nLook for the originating spec, in this order:\n\n1. The ticket the implementer is working, via `bd show \u003Cid>` and the workflow in `docs\u002Fagents\u002Fissue-tracker.md`.\n2. A path the caller passed as an argument.\n3. A spec file under `docs\u002F`, `specs\u002F`, or `.scratch\u002F` matching the branch name or feature.\n4. If nothing is found, the reviewer reports \"no spec available\" on the Spec axis.\n\n### 3. Identify the standards sources\n\nAnything in the repo that documents how code should be written, such as `CODING_STANDARDS.md` or `CONTRIBUTING.md`.\n\nOn top of whatever the repo documents, the Standards axis always carries the **smell baseline** below: a fixed set of Fowler code smells (_Refactoring_, ch.3) that applies even when a repo documents nothing. Two rules bind it:\n\n- **The repo overrides.** A documented repo standard always wins; where it endorses something the baseline would flag, suppress the smell.\n- **Always a judgement call.** Each smell is a labelled heuristic (\"possible Feature Envy\"), never a hard violation. Like any standard here, skip anything tooling already enforces.\n\nEach smell reads *what it is* → *how to fix*; match it against the diff:\n\n- **Mysterious Name**: a function, variable, or type whose name doesn't reveal what it does or holds. → rename it; if no honest name comes, the design's murky.\n- **Duplicated Code**: the same logic shape appears in more than one hunk or file in the change. → extract the shared shape, call it from both.\n- **Feature Envy**: a method that reaches into another object's data more than its own. → move the method onto the data it envies.\n- **Data Clumps**: the same few fields or params keep travelling together (a type wanting to be born). → bundle them into one type, pass that.\n- **Primitive Obsession**: a primitive or string standing in for a domain concept that deserves its own type. → give the concept its own small type.\n- **Repeated Switches**: the same `switch`\u002F`if`-cascade on the same type recurs across the change. → replace with polymorphism, or one map both sites share.\n- **Shotgun Surgery**: one logical change forces scattered edits across many files in the diff. → gather what changes together into one module.\n- **Divergent Change**: one file or module is edited for several unrelated reasons. → split so each module changes for one reason.\n- **Speculative Generality**: abstraction, parameters, or hooks added for needs the spec doesn't have. → delete it; inline back until a real need shows.\n- **Message Chains**: long `a.b().c().d()` navigation the caller shouldn't depend on. → hide the walk behind one method on the first object.\n- **Middle Man**: a class or function that mostly just delegates onward. → cut it, call the real target direct.\n- **Refused Bequest**: a subclass or implementer that ignores or overrides most of what it inherits. → drop the inheritance, use composition.\n\n### 4. Spawn one reviewer sub-agent\n\nLaunch the three-axis review sub-agent once, resolved from the agents section of `docs\u002Fagents\u002Fregistry.md` (default: `reviewer`), with `REVIEW_AXIS` covering all three axes. Its prompt should include:\n\n- The full diff command and commit list.\n- The list of standards-source files you found in step 3, **plus the smell baseline from step 3** pasted in full (the sub-agent has no other access to it).\n- The path or fetched contents of the spec, or an explicit \"no spec available\".\n\nThe Correctness axis owns its own brief; the sub-agent's definition carries it. Do not paste a copy here.\n\n### 5. Present the report\n\nPresent the report under `## Standards`, `## Spec`, and `## Correctness` headings, verbatim or lightly cleaned. Do **not** merge or rerank findings across axes: the axes are deliberately separate (see _Why three axes_).\n\nEnd with a one-line summary: total findings per axis, and the worst issue _within each axis_ (if any). Don't pick a single winner across axes: that's the reranking the separation exists to prevent.\n\n### 6. Deterministic checks (advisory)\n\nBefore presenting, read the `report: docs-coverage` output from `composer verify`. If verification has not run, ask the implementer to run it from the profile directory.\n\nReport missing required declaration docblocks as advisory Standards-axis findings. The coverage summary is context, not a finding. Review the changed declarations against `.ai\u002Frules\u002Fphp-docblocks.md` for meaningful prose, method contracts, and retry behavior that the script cannot judge. Docs coverage remains report-only and never blocks the change on its own.\n\nTest-shape scope: tests sit at recorded seams; use `tdd` for test design and profile rules for verification policy.\n\n## Why three axes\n\nA change can pass two axes and fail the third:\n\n- Code that follows every standard and implements the ticket, but breaks on an edge case → **Standards pass, Spec pass, Correctness fail.**\n- Code that follows every standard and handles its edge cases, but implements the wrong thing → **Standards pass, Spec fail, Correctness pass.**\n- Code that does exactly what the ticket asked, in a shape the repo rejects → **Spec pass, Correctness pass, Standards fail.**\n\nReporting them separately stops one axis from masking another. The single sub-agent keeps the context shared: a spec gap found on the Spec axis is evidence for the Correctness axis, and a confirmed bug on the Correctness axis can excuse a Standards judgement call.\n",{"name":5,"description":7},"main","7eaad6bd4c63295f8cb6f3e970ebcf4b25fe3707","simple\u002F.agents\u002Fskills\u002Fself-review",0,"https:\u002F\u002Fgithub.com\u002FShehabMohamedGamal\u002Fsimple-laravel","https:\u002F\u002Fgithub.com\u002FShehabMohamedGamal","2026-10-17 01:25:38",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add ShehabMohamedGamal\u002Fsimple-laravel --skill self-review",{"tool":37,"command":38},"bunx","bunx skills add ShehabMohamedGamal\u002Fsimple-laravel --skill self-review",{"tool":40,"command":41},"pnpm","pnpm dlx skills add ShehabMohamedGamal\u002Fsimple-laravel --skill self-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FShehabMohamedGamal\u002Fsimple-laravel\u002Fblob\u002Fmain\u002Fsimple\u002F.agents\u002Fskills\u002Fself-review\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7C7HHRAH4W5GMGYTYQ0S02S","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002FShehabMohamedGamal\u002Fsimple-laravel\u002Fblob\u002Fmain\u002Fsimple\u002F.agents\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7C7HDVEACGV78RYY9BNWKHP","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002FShehabMohamedGamal\u002Fsimple-laravel\u002Fblob\u002Fmain\u002Fsimple\u002F.agents\u002Fskills\u002Fwizard\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7C7HACMYEQQ9B438937AVKD","wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002FShehabMohamedGamal\u002Fsimple-laravel\u002Fblob\u002Fmain\u002Fsimple\u002F.agents\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7C7H84BTB72N82WS4GR6XYZ","wait-what","Stop. That last message did not land: re-pitch it.","https:\u002F\u002Fgithub.com\u002FShehabMohamedGamal\u002Fsimple-laravel\u002Fblob\u002Fmain\u002Fsimple\u002F.agents\u002Fskills\u002Fwait-what\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7C7H65MWB2N1675BAR689CW","visual-spec","Turn the grilled conversation into a spec, optionally confirming risky decisions as a visual HTML explainer first, then publish it to the issue tracker.","https:\u002F\u002Fgithub.com\u002FShehabMohamedGamal\u002Fsimple-laravel\u002Fblob\u002Fmain\u002Fsimple\u002F.agents\u002Fskills\u002Fvisual-spec\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7C7H40KNBS5P324GS9AE7PZ","triage","Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.","https:\u002F\u002Fgithub.com\u002FShehabMohamedGamal\u002Fsimple-laravel\u002Fblob\u002Fmain\u002Fsimple\u002F.agents\u002Fskills\u002Ftriage\u002FSKILL.md",[],[]]