[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F0B1R1W8WF4KT7HD4BA75F":3,"skill-same:01M7F0B1R1W8WF4KT7HD4BA75F":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":13,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":44},"01M7F0B1R1W8WF4KT7HD4BA75F","audit",null,"Review an existing project against the convention and the current Claude Code recommendations, then migrate it on approval - missing files, legacy docs structure, TODO.md to Asana, CLAUDE.md rewrite, a prompt-audit of instruction files, then a \u002Fdoctor checkup.","matwi5\u002Fmathis-plugins","matwi5","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F85203024?v=4","01M7F07V8STFXWXT8QZ2AT3S0E","01M7F07V9P11CN11Z1W7VXCDZ2",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmatwi5\u002Fmathis-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fproject\u002Fskills\u002Faudit\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: audit\ndescription: Review an existing project against the convention and the current Claude Code recommendations, then migrate it on approval - missing files, legacy docs structure, TODO.md to Asana, CLAUDE.md rewrite, a prompt-audit of instruction files, then a \u002Fdoctor checkup.\nargument-hint: \"[report]\"\ndisable-model-invocation: true\nallowed-tools: Read(\u002F${CLAUDE_PLUGIN_ROOT}\u002F**) Bash(python3 ${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Faudit.py *) Bash(python ${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Faudit.py *) Bash(py -3 ${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Faudit.py *)\n---\n\nBring the project in the current working directory to the convention in `${CLAUDE_PLUGIN_ROOT}\u002Freference\u002Fconventions.md`. Read that file first: sections 2, 4 and 6 are the yardstick for every finding.\n\nWith the argument `report` ($ARGUMENTS), stop after step 4: produce the report and the migration plan, change nothing.\n\nThe standard for this work: no information is lost. Content leaves a file only once it has a new home (DECISIONS.md, CLAUDE.md, a rule, Asana, a spec) or the owner has confirmed it can go.\n\nBefore step 1, create a task list (the TodoWrite tool, or TaskCreate and TaskUpdate where those are the task tools) with one entry per numbered step below, titled like the step, in order. Keep it current as you go: a step is in progress when you start it and completed when it ends. A step that does not apply, or that an argument skips, is marked completed and said in the report, never left open or removed.\n\n## 1. Mechanical inventory\n\nRun `python3 ${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Faudit.py .` (on Windows, `python` or `py -3`; quote the path if it contains spaces). It lists missing files, legacy structure, CLAUDE.md size and protocol markers, the journal order in `ETAT_DU_PROJET.md`, and prompt-audit signals (caps emphasis, dated idioms, backticked paths that no longer exist). If Python is unavailable, make the same checks with Glob, Grep and Read.\n\n## 2. Instruction files\n\nInvoke the `claude-api` skill with the subcommand `prompt-audit`, scoped to the project's instruction files (`CLAUDE.md`, `AGENTS.md`, `.claude\u002Frules\u002F`, `.claude\u002Fskills\u002F`, `.claude\u002Fagents\u002F`, `.claude\u002Fcommands\u002F`), target model: the model running this session. Keep its report and proposed diff for the plan; it does not edit files unless asked, and this skill applies its hunks only in step 5. If `claude-api` is not available, apply section 4 of the conventions yourself, with its keep list.\n\n## 3. Content review\n\nRead `CLAUDE.md` in full and the other convention files that exist. For each legacy item from step 1, open it and decide where its content goes, using the table in section 6 of the conventions. Things to check that the script cannot:\n- facts in `CLAUDE.md` that the repository now contradicts (paths, commands, versions). Trimming what Claude can derive from the code, deduplicating local and checked-in `CLAUDE.md` files and moving guidance to on-demand files is `\u002Fdoctor`'s job (step 6): don't redo it here;\n- rules that contradict each other across files, or contradict the code;\n- decisions buried in logs or specs that belong in `DECISIONS.md`;\n- recurring pitfalls in bug logs that belong in `CLAUDE.md`, or in the `CLAUDE.md` of the folder they concern;\n- the Asana part of the session protocol: project and section GIDs, the « [code] » parent task, the « Statut : » line, sub-tasks read through their parent, the no-connector fallback to the journal. A protocol that still reads or updates `TODO.md` is rewritten;\n- no PR template while the project uses pull requests: propose `${CLAUDE_PLUGIN_ROOT}\u002Ftemplates\u002Fpull_request_template.md` as `.github\u002Fpull_request_template.md`; an existing template stays, unless the owner wants the plugin's;\n- `ETAT_DU_PROJET.md`: a journal in oldest-first order is reversed, a missing « État » section is written from the latest entries.\n\n## 4. Report and migration plan\n\nPresent, in the owner's language:\n1. a summary: the two or three changes that matter most;\n2. a table with one row per item: element, finding, proposed action (keep \u002F rewrite \u002F merge into X \u002F move to X \u002F migrate to Asana \u002F delete), and where its content goes;\n3. the prompt-audit findings from step 2, grouped with their proposed hunks;\n4. what remains « à confirmer ».\n\nIn `report` mode, stop here and tell the owner that `\u002Fproject:audit` without argument applies the plan.\n\n## 5. Apply on approval\n\nCheck `git status` first. If the working tree has uncommitted changes, ask the owner to commit them (or run `\u002Fproject:commit`) so the migration can be reviewed and reverted as one diff.\n\nAsk the owner which groups of actions to apply (AskUserQuestion, multi-select). Deletions and anything outside the repository need their own explicit yes. Then apply in this order, so nothing is deleted before its content has moved:\n1. create missing files from `${CLAUDE_PLUGIN_ROOT}\u002Ftemplates\u002F`, filled from what the project already says (« à confirmer » otherwise);\n2. merge and move content (decisions, pitfalls, specs, relocated migrations);\n3. rewrite `CLAUDE.md`: keep the project's own commands, conventions and pitfalls, add the session protocol from the template, apply the accepted prompt-audit hunks;\n4. `TODO.md`: with the `asana-board:suivi-asana` skill, create the project's section and its unassigned parent task « [code] \u003Csection> : prochaines sessions Claude Code » if missing, write their GIDs into `CLAUDE.md`, then add the open items: Claude's work under the parent task, the owner's assigned to them, each description starting with a « Statut : » line. Show the owner what was added, then delete `TODO.md`, or move it to `archives\u002FTODO_\u003CYYYY-MM-DD>.md` when the folder does not allow deletion (synced folders such as OneDrive) or the owner prefers. If Asana is not reachable, keep `TODO.md` and say so;\n5. delete the legacy items the owner approved (or move them to `archives\u002F` where deletion is not possible, and note it in the journal).\n\n## 6. Verify\n\nRe-run the audit script and compare with step 1: every approved action must show up as resolved. Grep for references to deleted or moved paths (in instruction files, README, scripts) and fix or report them. Add an entry to the journal of `ETAT_DU_PROJET.md` describing the migration, and record in `DECISIONS.md` any convention choice the owner made along the way. Report what changed, what was verified, and what is left for the owner.\n\nThen ask the owner to run `\u002Fdoctor` in this project: it trims from `CLAUDE.md` what Claude can derive from the code, deduplicates local and checked-in `CLAUDE.md` files, and moves guidance that isn't needed every session into nested `CLAUDE.md` files and skills, asking before each change. It also checks the installation, settings and unused plugins, which is why the owner runs it rather than this skill.\n","Bring the project in the current working directory to the convention in `${CLAUDE_PLUGIN_ROOT}\u002Freference\u002Fconventions.md`. Read that file first: sections 2, 4 and 6 are the yardstick for every finding.\n\nWith the argument `report` ($ARGUMENTS), stop after step 4: produce the report and the migration plan, change nothing.\n\nThe standard for this work: no information is lost. Content leaves a file only once it has a new home (DECISIONS.md, CLAUDE.md, a rule, Asana, a spec) or the owner has confirmed it can go.\n\nBefore step 1, create a task list (the TodoWrite tool, or TaskCreate and TaskUpdate where those are the task tools) with one entry per numbered step below, titled like the step, in order. Keep it current as you go: a step is in progress when you start it and completed when it ends. A step that does not apply, or that an argument skips, is marked completed and said in the report, never left open or removed.\n\n## 1. Mechanical inventory\n\nRun `python3 ${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Faudit.py .` (on Windows, `python` or `py -3`; quote the path if it contains spaces). It lists missing files, legacy structure, CLAUDE.md size and protocol markers, the journal order in `ETAT_DU_PROJET.md`, and prompt-audit signals (caps emphasis, dated idioms, backticked paths that no longer exist). If Python is unavailable, make the same checks with Glob, Grep and Read.\n\n## 2. Instruction files\n\nInvoke the `claude-api` skill with the subcommand `prompt-audit`, scoped to the project's instruction files (`CLAUDE.md`, `AGENTS.md`, `.claude\u002Frules\u002F`, `.claude\u002Fskills\u002F`, `.claude\u002Fagents\u002F`, `.claude\u002Fcommands\u002F`), target model: the model running this session. Keep its report and proposed diff for the plan; it does not edit files unless asked, and this skill applies its hunks only in step 5. If `claude-api` is not available, apply section 4 of the conventions yourself, with its keep list.\n\n## 3. Content review\n\nRead `CLAUDE.md` in full and the other convention files that exist. For each legacy item from step 1, open it and decide where its content goes, using the table in section 6 of the conventions. Things to check that the script cannot:\n- facts in `CLAUDE.md` that the repository now contradicts (paths, commands, versions). Trimming what Claude can derive from the code, deduplicating local and checked-in `CLAUDE.md` files and moving guidance to on-demand files is `\u002Fdoctor`'s job (step 6): don't redo it here;\n- rules that contradict each other across files, or contradict the code;\n- decisions buried in logs or specs that belong in `DECISIONS.md`;\n- recurring pitfalls in bug logs that belong in `CLAUDE.md`, or in the `CLAUDE.md` of the folder they concern;\n- the Asana part of the session protocol: project and section GIDs, the « [code] » parent task, the « Statut : » line, sub-tasks read through their parent, the no-connector fallback to the journal. A protocol that still reads or updates `TODO.md` is rewritten;\n- no PR template while the project uses pull requests: propose `${CLAUDE_PLUGIN_ROOT}\u002Ftemplates\u002Fpull_request_template.md` as `.github\u002Fpull_request_template.md`; an existing template stays, unless the owner wants the plugin's;\n- `ETAT_DU_PROJET.md`: a journal in oldest-first order is reversed, a missing « État » section is written from the latest entries.\n\n## 4. Report and migration plan\n\nPresent, in the owner's language:\n1. a summary: the two or three changes that matter most;\n2. a table with one row per item: element, finding, proposed action (keep \u002F rewrite \u002F merge into X \u002F move to X \u002F migrate to Asana \u002F delete), and where its content goes;\n3. the prompt-audit findings from step 2, grouped with their proposed hunks;\n4. what remains « à confirmer ».\n\nIn `report` mode, stop here and tell the owner that `\u002Fproject:audit` without argument applies the plan.\n\n## 5. Apply on approval\n\nCheck `git status` first. If the working tree has uncommitted changes, ask the owner to commit them (or run `\u002Fproject:commit`) so the migration can be reviewed and reverted as one diff.\n\nAsk the owner which groups of actions to apply (AskUserQuestion, multi-select). Deletions and anything outside the repository need their own explicit yes. Then apply in this order, so nothing is deleted before its content has moved:\n1. create missing files from `${CLAUDE_PLUGIN_ROOT}\u002Ftemplates\u002F`, filled from what the project already says (« à confirmer » otherwise);\n2. merge and move content (decisions, pitfalls, specs, relocated migrations);\n3. rewrite `CLAUDE.md`: keep the project's own commands, conventions and pitfalls, add the session protocol from the template, apply the accepted prompt-audit hunks;\n4. `TODO.md`: with the `asana-board:suivi-asana` skill, create the project's section and its unassigned parent task « [code] \u003Csection> : prochaines sessions Claude Code » if missing, write their GIDs into `CLAUDE.md`, then add the open items: Claude's work under the parent task, the owner's assigned to them, each description starting with a « Statut : » line. Show the owner what was added, then delete `TODO.md`, or move it to `archives\u002FTODO_\u003CYYYY-MM-DD>.md` when the folder does not allow deletion (synced folders such as OneDrive) or the owner prefers. If Asana is not reachable, keep `TODO.md` and say so;\n5. delete the legacy items the owner approved (or move them to `archives\u002F` where deletion is not possible, and note it in the journal).\n\n## 6. Verify\n\nRe-run the audit script and compare with step 1: every approved action must show up as resolved. Grep for references to deleted or moved paths (in instruction files, README, scripts) and fix or report them. Add an entry to the journal of `ETAT_DU_PROJET.md` describing the migration, and record in `DECISIONS.md` any convention choice the owner made along the way. Report what changed, what was verified, and what is left for the owner.\n\nThen ask the owner to run `\u002Fdoctor` in this project: it trims from `CLAUDE.md` what Claude can derive from the code, deduplicates local and checked-in `CLAUDE.md` files, and moves guidance that isn't needed every session into nested `CLAUDE.md` files and skills, asking before each change. It also checks the installation, settings and unused plugins, which is why the owner runs it rather than this skill.\n",{"name":5,"description":7,"allowed-tools":23,"argument-hint":24,"disable-model-invocation":25},"Read(\u002F${CLAUDE_PLUGIN_ROOT}\u002F**) Bash(python3 ${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Faudit.py *) Bash(python ${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Faudit.py *) Bash(py -3 ${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Faudit.py *)","[report]",true,"main","b7b841410dbb5488ead5b0d25f24f1e52919e0a6","plugins\u002Fproject\u002Fskills\u002Faudit","https:\u002F\u002Fgithub.com\u002Fmatwi5\u002Fmathis-plugins","https:\u002F\u002Fgithub.com\u002Fmatwi5","2026-11-14 06:50:48",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":25},[34,37,40],{"tool":35,"command":36},"npx","npx skills add matwi5\u002Fmathis-plugins --skill audit",{"tool":38,"command":39},"bunx","bunx skills add matwi5\u002Fmathis-plugins --skill audit",{"tool":41,"command":42},"pnpm","pnpm dlx skills add matwi5\u002Fmathis-plugins --skill audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmatwi5\u002Fmathis-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fproject\u002Fskills\u002Faudit\u002FSKILL.md",[],[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":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7F0CR7NTS8ET9KGJZMJ5XZN","reserve","Skill d'essai de la sonde, réservé à l'utilisateur. Répond par un mot fixe, sans rien faire d'autre.","https:\u002F\u002Fgithub.com\u002Fmatwi5\u002Fmathis-plugins\u002Fblob\u002Fmain\u002Fscripts\u002Fsonde-essai\u002Fskills\u002Freserve\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M7F0CDMR8CK8T4GD9H84W2RG","recap","Récap de l'usage Claude Code en chat, d'après ccusage et les relevés de requêtes de stats-board — la discussion en cours (coût, tokens, cache, durée, temps actif, attente de ta réponse, temps API, requêtes et la plus chère, modèles, spécialistes) et la journée (coût, tokens, temps actif, temps cumulé et temps API de ce poste, par projet et par modèle, discussions actives, bloc de 5 h et son rythme, autres postes publiés dans claude-usage), ou une mission entière (manager, workers et spécialistes, retrouvés par le début de leur titre ou par les worktrees groupe-* d'un projet, avec leur temps actif sans double compte et leur temps cumulé). À utiliser sur « \u002Fstats-board:recap », « récap de l'usage », « combien m'a coûté cette discussion », « combien j'ai consommé aujourd'hui », « coût de la journée », « récap de la mission », « combien a coûté la mission », « récap du parcours », « combien a coûté le parcours ». Pas pour ouvrir le panneau de statistiques, qui passe par \u002Fccstats.","https:\u002F\u002Fgithub.com\u002Fmatwi5\u002Fmathis-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fstats-board\u002Fskills\u002Frecap\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M7F0C6YAZJ8FGHZJH0SSJZJR","install","Installe et initialise les plugins de la marketplace mathis-plugins choisis par l'utilisateur - choix par groupes, dépendances et prérequis, installation, réglages (Asana, partage des usages, modèle de session-tools, barre d'état) et bloc de règles dans le CLAUDE.md global ou du projet, montré avant écriture. Relançable pour ajouter ou retirer des plugins.","https:\u002F\u002Fgithub.com\u002Fmatwi5\u002Fmathis-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fsetup\u002Fskills\u002Finstall\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M7F0C055YGPV4ZF7BYZATXTM","version","Bump the project version with SemVer - detect the version files (package.json, pyproject.toml, Cargo.toml, Expo app config, Claude Code plugin manifests and their marketplace entry...), propose the bump from the commits since the last release, update every file consistently; handles Expo native vs OTA releases.","https:\u002F\u002Fgithub.com\u002Fmatwi5\u002Fmathis-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fproject\u002Fskills\u002Fversion\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M7F0BVNTR2CSK4526VDKBQSR","sync","Bring the current branch up to date with its remote, or with the default branch when asked, without losing local work - fetch, rebase or merge, autostash.","https:\u002F\u002Fgithub.com\u002Fmatwi5\u002Fmathis-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fproject\u002Fskills\u002Fsync\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M7F0BP07YP3XH3S8ECJJW8KT","push","Finish a piece of work and push it - commit what is left, run the project's checks, confirm the end-of-session files are up to date, sync with the remote and push without force.","https:\u002F\u002Fgithub.com\u002Fmatwi5\u002Fmathis-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fproject\u002Fskills\u002Fpush\u002FSKILL.md",[],[]]