[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CSNN290A5FSKN5E3WB4BPY":3,"skill-same:01M6CSNN290A5FSKN5E3WB4BPY":87},{"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":32,"linkOnly":33,"markdownContent":34,"markdownBody":35,"frontMatter":36,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":14,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":46,"ownerDescription":47,"updatedAt":48,"install":49,"resources":62},"01M6CSNN290A5FSKN5E3WB4BPY","openspec-verify-change",null,"Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.","psacc\u002Fomnisess","psacc","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F171010?v=4","01M6CSN1C11CTRR5G2Q0MCH0SE","Paolo Sacconier","01M6CSN1G116PZV68PYSN0WD31",1,"MIT","https:\u002F\u002Fgithub.com\u002Fpsacc\u002Fomnisess\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenspec-verify-change\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31],"change","openspec verify change","verify","verify change","openspec","cli","validate","artifacts","correct","user","use","implementation","coherent","2026-11-10 10:12:30",false,"---\nname: openspec-verify-change\ndescription: Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.\nlicense: MIT\ncompatibility: Requires openspec CLI.\nmetadata:\n  author: openspec\n  version: \"1.0\"\n  generatedBy: \"1.1.1\"\n---\n\nVerify that an implementation matches the change artifacts (specs, tasks, design).\n\n**Input**: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.\n\n**Steps**\n\n1. **If no change name provided, prompt for selection**\n\n   Run `openspec list --json` to get available changes. Use the **AskUserQuestion tool** to let the user select.\n\n   Show changes that have implementation tasks (tasks artifact exists).\n   Include the schema used for each change if available.\n   Mark changes with incomplete tasks as \"(In Progress)\".\n\n   **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.\n\n2. **Check status to understand the schema**\n   ```bash\n   openspec status --change \"\u003Cname>\" --json\n   ```\n   Parse the JSON to understand:\n   - `schemaName`: The workflow being used (e.g., \"spec-driven\")\n   - Which artifacts exist for this change\n\n3. **Get the change directory and load artifacts**\n\n   ```bash\n   openspec instructions apply --change \"\u003Cname>\" --json\n   ```\n\n   This returns the change directory and context files. Read all available artifacts from `contextFiles`.\n\n4. **Initialize verification report structure**\n\n   Create a report structure with three dimensions:\n   - **Completeness**: Track tasks and spec coverage\n   - **Correctness**: Track requirement implementation and scenario coverage\n   - **Coherence**: Track design adherence and pattern consistency\n\n   Each dimension can have CRITICAL, WARNING, or SUGGESTION issues.\n\n5. **Verify Completeness**\n\n   **Task Completion**:\n   - If tasks.md exists in contextFiles, read it\n   - Parse checkboxes: `- [ ]` (incomplete) vs `- [x]` (complete)\n   - Count complete vs total tasks\n   - If incomplete tasks exist:\n     - Add CRITICAL issue for each incomplete task\n     - Recommendation: \"Complete task: \u003Cdescription>\" or \"Mark as done if already implemented\"\n\n   **Spec Coverage**:\n   - If delta specs exist in `openspec\u002Fchanges\u002F\u003Cname>\u002Fspecs\u002F`:\n     - Extract all requirements (marked with \"### Requirement:\")\n     - For each requirement:\n       - Search codebase for keywords related to the requirement\n       - Assess if implementation likely exists\n     - If requirements appear unimplemented:\n       - Add CRITICAL issue: \"Requirement not found: \u003Crequirement name>\"\n       - Recommendation: \"Implement requirement X: \u003Cdescription>\"\n\n6. **Verify Correctness**\n\n   **Requirement Implementation Mapping**:\n   - For each requirement from delta specs:\n     - Search codebase for implementation evidence\n     - If found, note file paths and line ranges\n     - Assess if implementation matches requirement intent\n     - If divergence detected:\n       - Add WARNING: \"Implementation may diverge from spec: \u003Cdetails>\"\n       - Recommendation: \"Review \u003Cfile>:\u003Clines> against requirement X\"\n\n   **Scenario Coverage**:\n   - For each scenario in delta specs (marked with \"#### Scenario:\"):\n     - Check if conditions are handled in code\n     - Check if tests exist covering the scenario\n     - If scenario appears uncovered:\n       - Add WARNING: \"Scenario not covered: \u003Cscenario name>\"\n       - Recommendation: \"Add test or implementation for scenario: \u003Cdescription>\"\n\n7. **Verify Coherence**\n\n   **Design Adherence**:\n   - If design.md exists in contextFiles:\n     - Extract key decisions (look for sections like \"Decision:\", \"Approach:\", \"Architecture:\")\n     - Verify implementation follows those decisions\n     - If contradiction detected:\n       - Add WARNING: \"Design decision not followed: \u003Cdecision>\"\n       - Recommendation: \"Update implementation or revise design.md to match reality\"\n   - If no design.md: Skip design adherence check, note \"No design.md to verify against\"\n\n   **Code Pattern Consistency**:\n   - Review new code for consistency with project patterns\n   - Check file naming, directory structure, coding style\n   - If significant deviations found:\n     - Add SUGGESTION: \"Code pattern deviation: \u003Cdetails>\"\n     - Recommendation: \"Consider following project pattern: \u003Cexample>\"\n\n8. **Generate Verification Report**\n\n   **Summary Scorecard**:\n   ```\n   ## Verification Report: \u003Cchange-name>\n\n   ### Summary\n   | Dimension    | Status           |\n   |--------------|------------------|\n   | Completeness | X\u002FY tasks, N reqs|\n   | Correctness  | M\u002FN reqs covered |\n   | Coherence    | Followed\u002FIssues  |\n   ```\n\n   **Issues by Priority**:\n\n   1. **CRITICAL** (Must fix before archive):\n      - Incomplete tasks\n      - Missing requirement implementations\n      - Each with specific, actionable recommendation\n\n   2. **WARNING** (Should fix):\n      - Spec\u002Fdesign divergences\n      - Missing scenario coverage\n      - Each with specific recommendation\n\n   3. **SUGGESTION** (Nice to fix):\n      - Pattern inconsistencies\n      - Minor improvements\n      - Each with specific recommendation\n\n   **Final Assessment**:\n   - If CRITICAL issues: \"X critical issue(s) found. Fix before archiving.\"\n   - If only warnings: \"No critical issues. Y warning(s) to consider. Ready for archive (with noted improvements).\"\n   - If all clear: \"All checks passed. Ready for archive.\"\n\n**Verification Heuristics**\n\n- **Completeness**: Focus on objective checklist items (checkboxes, requirements list)\n- **Correctness**: Use keyword search, file path analysis, reasonable inference - don't require perfect certainty\n- **Coherence**: Look for glaring inconsistencies, don't nitpick style\n- **False Positives**: When uncertain, prefer SUGGESTION over WARNING, WARNING over CRITICAL\n- **Actionability**: Every issue must have a specific recommendation with file\u002Fline references where applicable\n\n**Graceful Degradation**\n\n- If only tasks.md exists: verify task completion only, skip spec\u002Fdesign checks\n- If tasks + specs exist: verify completeness and correctness, skip design\n- If full artifacts: verify all three dimensions\n- Always note which checks were skipped and why\n\n**Output Format**\n\nUse clear markdown with:\n- Table for summary scorecard\n- Grouped lists for issues (CRITICAL\u002FWARNING\u002FSUGGESTION)\n- Code references in format: `file.ts:123`\n- Specific, actionable recommendations\n- No vague suggestions like \"consider reviewing\"\n","Verify that an implementation matches the change artifacts (specs, tasks, design).\n\n**Input**: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.\n\n**Steps**\n\n1. **If no change name provided, prompt for selection**\n\n   Run `openspec list --json` to get available changes. Use the **AskUserQuestion tool** to let the user select.\n\n   Show changes that have implementation tasks (tasks artifact exists).\n   Include the schema used for each change if available.\n   Mark changes with incomplete tasks as \"(In Progress)\".\n\n   **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.\n\n2. **Check status to understand the schema**\n   ```bash\n   openspec status --change \"\u003Cname>\" --json\n   ```\n   Parse the JSON to understand:\n   - `schemaName`: The workflow being used (e.g., \"spec-driven\")\n   - Which artifacts exist for this change\n\n3. **Get the change directory and load artifacts**\n\n   ```bash\n   openspec instructions apply --change \"\u003Cname>\" --json\n   ```\n\n   This returns the change directory and context files. Read all available artifacts from `contextFiles`.\n\n4. **Initialize verification report structure**\n\n   Create a report structure with three dimensions:\n   - **Completeness**: Track tasks and spec coverage\n   - **Correctness**: Track requirement implementation and scenario coverage\n   - **Coherence**: Track design adherence and pattern consistency\n\n   Each dimension can have CRITICAL, WARNING, or SUGGESTION issues.\n\n5. **Verify Completeness**\n\n   **Task Completion**:\n   - If tasks.md exists in contextFiles, read it\n   - Parse checkboxes: `- [ ]` (incomplete) vs `- [x]` (complete)\n   - Count complete vs total tasks\n   - If incomplete tasks exist:\n     - Add CRITICAL issue for each incomplete task\n     - Recommendation: \"Complete task: \u003Cdescription>\" or \"Mark as done if already implemented\"\n\n   **Spec Coverage**:\n   - If delta specs exist in `openspec\u002Fchanges\u002F\u003Cname>\u002Fspecs\u002F`:\n     - Extract all requirements (marked with \"### Requirement:\")\n     - For each requirement:\n       - Search codebase for keywords related to the requirement\n       - Assess if implementation likely exists\n     - If requirements appear unimplemented:\n       - Add CRITICAL issue: \"Requirement not found: \u003Crequirement name>\"\n       - Recommendation: \"Implement requirement X: \u003Cdescription>\"\n\n6. **Verify Correctness**\n\n   **Requirement Implementation Mapping**:\n   - For each requirement from delta specs:\n     - Search codebase for implementation evidence\n     - If found, note file paths and line ranges\n     - Assess if implementation matches requirement intent\n     - If divergence detected:\n       - Add WARNING: \"Implementation may diverge from spec: \u003Cdetails>\"\n       - Recommendation: \"Review \u003Cfile>:\u003Clines> against requirement X\"\n\n   **Scenario Coverage**:\n   - For each scenario in delta specs (marked with \"#### Scenario:\"):\n     - Check if conditions are handled in code\n     - Check if tests exist covering the scenario\n     - If scenario appears uncovered:\n       - Add WARNING: \"Scenario not covered: \u003Cscenario name>\"\n       - Recommendation: \"Add test or implementation for scenario: \u003Cdescription>\"\n\n7. **Verify Coherence**\n\n   **Design Adherence**:\n   - If design.md exists in contextFiles:\n     - Extract key decisions (look for sections like \"Decision:\", \"Approach:\", \"Architecture:\")\n     - Verify implementation follows those decisions\n     - If contradiction detected:\n       - Add WARNING: \"Design decision not followed: \u003Cdecision>\"\n       - Recommendation: \"Update implementation or revise design.md to match reality\"\n   - If no design.md: Skip design adherence check, note \"No design.md to verify against\"\n\n   **Code Pattern Consistency**:\n   - Review new code for consistency with project patterns\n   - Check file naming, directory structure, coding style\n   - If significant deviations found:\n     - Add SUGGESTION: \"Code pattern deviation: \u003Cdetails>\"\n     - Recommendation: \"Consider following project pattern: \u003Cexample>\"\n\n8. **Generate Verification Report**\n\n   **Summary Scorecard**:\n   ```\n   ## Verification Report: \u003Cchange-name>\n\n   ### Summary\n   | Dimension    | Status           |\n   |--------------|------------------|\n   | Completeness | X\u002FY tasks, N reqs|\n   | Correctness  | M\u002FN reqs covered |\n   | Coherence    | Followed\u002FIssues  |\n   ```\n\n   **Issues by Priority**:\n\n   1. **CRITICAL** (Must fix before archive):\n      - Incomplete tasks\n      - Missing requirement implementations\n      - Each with specific, actionable recommendation\n\n   2. **WARNING** (Should fix):\n      - Spec\u002Fdesign divergences\n      - Missing scenario coverage\n      - Each with specific recommendation\n\n   3. **SUGGESTION** (Nice to fix):\n      - Pattern inconsistencies\n      - Minor improvements\n      - Each with specific recommendation\n\n   **Final Assessment**:\n   - If CRITICAL issues: \"X critical issue(s) found. Fix before archiving.\"\n   - If only warnings: \"No critical issues. Y warning(s) to consider. Ready for archive (with noted improvements).\"\n   - If all clear: \"All checks passed. Ready for archive.\"\n\n**Verification Heuristics**\n\n- **Completeness**: Focus on objective checklist items (checkboxes, requirements list)\n- **Correctness**: Use keyword search, file path analysis, reasonable inference - don't require perfect certainty\n- **Coherence**: Look for glaring inconsistencies, don't nitpick style\n- **False Positives**: When uncertain, prefer SUGGESTION over WARNING, WARNING over CRITICAL\n- **Actionability**: Every issue must have a specific recommendation with file\u002Fline references where applicable\n\n**Graceful Degradation**\n\n- If only tasks.md exists: verify task completion only, skip spec\u002Fdesign checks\n- If tasks + specs exist: verify completeness and correctness, skip design\n- If full artifacts: verify all three dimensions\n- Always note which checks were skipped and why\n\n**Output Format**\n\nUse clear markdown with:\n- Table for summary scorecard\n- Grouped lists for issues (CRITICAL\u002FWARNING\u002FSUGGESTION)\n- Code references in format: `file.ts:123`\n- Specific, actionable recommendations\n- No vague suggestions like \"consider reviewing\"\n",{"name":5,"license":15,"metadata":37,"description":7,"compatibility":40},{"author":23,"version":38,"generatedBy":39},"1.0","1.1.1","Requires openspec CLI.","main","ef52a1fa5af69c0357cc554044ba40801d76165d",".claude\u002Fskills\u002Fopenspec-verify-change","https:\u002F\u002Fgithub.com\u002Fpsacc\u002Fomnisess","https:\u002F\u002Fgithub.com\u002Fpsacc","http:\u002F\u002Fpaolo.sacconier.net","brain in a jar","2026-11-12 11:11:40",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add psacc\u002Fomnisess --skill openspec-verify-change",{"tool":55,"command":56},"bunx","bunx skills add psacc\u002Fomnisess --skill openspec-verify-change",{"tool":58,"command":59},"pnpm","pnpm dlx skills add psacc\u002Fomnisess --skill openspec-verify-change","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpsacc\u002Fomnisess\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenspec-verify-change\u002FSKILL.md",true,[63,69,73,77,83],{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"Tools\u002FFetchFredSeries.ts","SCRIPT","脚本",12372,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002FPersonal_AI_Infrastructure\u002FLifeOS\u002Finstall\u002Fskills\u002FUSMetrics\u002FTools\u002FFetchFredSeries.ts",{"path":70,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":71,"sourceHtmlUrl":72},"Tools\u002FGenerateAnalysis.ts",16215,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002FPersonal_AI_Infrastructure\u002FLifeOS\u002Finstall\u002Fskills\u002FUSMetrics\u002FTools\u002FGenerateAnalysis.ts",{"path":74,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":75,"sourceHtmlUrl":76},"Tools\u002FUpdateSubstrateMetrics.ts",23417,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002FPersonal_AI_Infrastructure\u002FLifeOS\u002Finstall\u002Fskills\u002FUSMetrics\u002FTools\u002FUpdateSubstrateMetrics.ts",{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"Workflows\u002FGetCurrentState.md","REFERENCE","参考文档",7998,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002FPersonal_AI_Infrastructure\u002FLifeOS\u002Finstall\u002Fskills\u002FUSMetrics\u002FWorkflows\u002FGetCurrentState.md",{"path":84,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":85,"sourceHtmlUrl":86},"Workflows\u002FUpdateData.md",3692,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002FPersonal_AI_Infrastructure\u002FLifeOS\u002Finstall\u002Fskills\u002FUSMetrics\u002FWorkflows\u002FUpdateData.md",[88,113,136,152,169,185],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":32},"01M6CSQGP57Y6A3RC0FMQ7SNGK","stats","Show tool-call counts and file-I\u002FO activity from the transcript SQLite index.\nAggregates Read\u002FWrite\u002FEdit file paths, line counts, token usage, and error flags\nacross a time window (default 7d) or for a single session.\nUse this skill when asked which tools were used most, which files saw the most\nactivity, how many tokens were spent, or to inspect a single session's\ntool-call summary.\nTrigger phrases: \"session stats\", \"tool stats\", \"what tools did I use\",\n\"tool usage\", \"files touched\", \"token usage\", \"stats for last week\",\n\"summarize tool calls\", \"session tool breakdown\".","https:\u002F\u002Fgithub.com\u002Fpsacc\u002Fomnisess\u002Fblob\u002Fmain\u002Fskills\u002Fomnisess-stats\u002FSKILL.md",[],[90,95,96,97,98,99,100,101,102,103,104,105,29,106,107,108,109,110,111,112],"transcript","file","sqlite","how","Bash","tool","json","read","write","edit","session","files","default","show","flags","call","aggregates","time",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":32},"01M6CSQDESFF8YP0CMETN519FE","skills-audit","Classify agent skills by usage tier (Keep \u002F Borderline \u002F Archive \u002F Unknown) using\nClaude Code session JSONL transcripts as the signal source. Read-only — never\nmodifies skills, sessions, or any file on disk.\nUse this skill when asked to audit skills, find unused skills, classify skills,\ncheck which skills get used, produce a skill usage report, or prune skills.\nTrigger phrases: \"audit skills\", \"find unused skills\", \"classify skills\",\n\"which skills do I use\", \"skill usage report\", \"prune skills\",\n\"what skills are unused\", \"skills I can remove\", \"trim my skill list\".\nOutput is a recommendation (Keep \u002F Borderline \u002F Archive) — acting on it is always\na manual step.","https:\u002F\u002Fgithub.com\u002Fpsacc\u002Fomnisess\u002Fblob\u002Fmain\u002Fskills\u002Fomnisess-skills-audit\u002FSKILL.md",[],[120,121,122,123,124,125,96,126,99,127,128,129,130,131,105,132,29,133,134,135],"audit","skills audit","sessions","code","my skill","produce","disk","markdown","skill usage","archive","find","check","remove","never","only","do",{"skillNo":137,"name":108,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":32},"01M6CSQB2H38WJ1FKHFT4FQWQB","Show the full detail of a single AI coding session by its ID.\nSession IDs are in the format \u003Ctool>:\u003Cid> (e.g., claude:5c3f2742, cursor:a1b2c3d4).\nUse this skill when asked to show a specific session, inspect a session, read a session,\nor view the messages in a session.\nTrigger phrases: \"show session\", \"open session\", \"inspect session\", \"read session\",\n\"show me claude:5c3f2742\", \"view session details\", \"what happened in session\".","https:\u002F\u002Fgithub.com\u002Fpsacc\u002Fomnisess\u002Fblob\u002Fmain\u002Fskills\u002Fomnisess-show\u002FSKILL.md",[],[108,142,143,144,145,99,100,146,147,102,148,149,105,29,150,151],"messages","ids","open","show me","format","coding","view","cursor","ai coding","me",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":158,"publishedAt":32},"01M6CSQ8M3MRDR8EDAJMWZPKKH","search","Full-text search across all AI coding sessions (Claude Code, Cursor, Codex, GitHub Copilot CLI).\nUse this skill when asked to search sessions, find a conversation about a topic,\nlook up what was discussed in past sessions, or find sessions mentioning specific code or concepts.\nTrigger phrases: \"search sessions\", \"find sessions about\", \"look up in sessions\",\n\"what did I discuss about\", \"find conversation about\", \"search my history\".","https:\u002F\u002Fgithub.com\u002Fpsacc\u002Fomnisess\u002Fblob\u002Fmain\u002Fskills\u002Fomnisess-search\u002FSKILL.md",[],[154,24,159,160,122,161,162,123,99,163,147,164,130,149,29,165,166,150,167,168],"github","codex","github copilot","copilot","text","history","up","look","conversation","query",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":175,"publishedAt":32},"01M6CSQ5R6430D028Q9G41EX5Q","recap","Produce a structured markdown briefing of AI coding sessions for a given time window.\nGroups sessions by project and summarizes each group with intent, outcome, and status.\nUse this skill when asked to recap recent coding work, summarize today's sessions,\nshow what was worked on, or produce a daily\u002Fweekly session summary.\nTrigger phrases: \"recap\", \"what did I work on\", \"daily summary\", \"session summary\",\n\"summarize my sessions\", \"what sessions did I have today\", \"coding recap\".\nThis is the sessions-only public version — no Slack, Jira, or Granola integration.","https:\u002F\u002Fgithub.com\u002Fpsacc\u002Fomnisess\u002Fblob\u002Fmain\u002Fskills\u002Fomnisess-recap\u002FSKILL.md",[],[171,176,122,177,125,99,127,178,179,180,105,29,181,134,182,150,183,108,184,112],"slack","session summary","work on","work","outcome","version","daily","intent","granola",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":191,"publishedAt":32},"01M6CSQ31NYJNFR7R4WPYCXB2M","ps","Show live Claude Code and Codex sessions as a process tree, grouped by\nshared ancestor chain up to launchd. Covers Claude CLI sessions, Claude\nDesktop agent mode, and Codex sessions (CLI TUI + Codex.app threads).\nUse this skill when asked about the process tree, ancestor lineage, which\nterminal or tmux window a Claude or Codex session is running in, or what's\ncurrently running.\nTrigger phrases: \"process tree\", \"what's running\", \"lineage\", \"ancestor chain\",\n\"which terminal is my claude in\", \"tmux tree\", \"claude process tree\",\n\"codex process tree\", \"session lineage\".\nmacOS-only: on other platforms the command prints \"unsupported\" and exits 0.","https:\u002F\u002Fgithub.com\u002Fpsacc\u002Fomnisess\u002Fblob\u002Fmain\u002Fskills\u002Fomnisess-ps\u002FSKILL.md",[],[192,193,24,194,195,160,122,196,123,197,99,198,199,105,200,29,201,134,165,108],"PS","macos","terminal","tmux","desktop","lineage","tui","command","process","launchd"]