[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ER3HW57RH32VKB5PXAMB7Z":3,"skill-same:01M6ER3HW57RH32VKB5PXAMB7Z":73},{"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":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":13,"repositoryHtmlUrl":56,"repositoryHomepageUrl":57,"ownerHtmlUrl":58,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":59,"install":60,"resources":72},"01M6ER3HW57RH32VKB5PXAMB7Z","import-skill",null,"Adapts an imported or external agent skill to match Arcana quality standards — rewrites frontmatter, tone, structure, and adds missing sections. Run after `arcana import` or on any skill that needs quality adaptation. Manual via \u002Fimport-skill.","cj-ways\u002Farcana","cj-ways","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F268418145?v=4","01M6ER2722FXTDPCH3119PJ5T3","01M6ER2773VFWAC3D21KGP6N7Q",0,"MIT","https:\u002F\u002Fgithub.com\u002Fcj-ways\u002Farcana\u002Fblob\u002Fmain\u002Fskills\u002Fimport-skill\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"import skill","import","structure","utility","via","missing","name","agent skill","adaptation","tone","run","imported","standards","edit","write","read","grep","quality","Bash","execution","2026-11-10 10:12:30",false,"---\nname: import-skill\ndescription: 'Adapts an imported or external agent skill to match Arcana quality standards — rewrites frontmatter, tone, structure, and adds missing sections. Run after `arcana import` or on any skill that needs quality adaptation. Manual via \u002Fimport-skill.'\nargument-hint: '\u003Cskill-name>'\ndisable-model-invocation: true\nallowed-tools: Read, Write, Edit, Glob, Grep, Bash\neffort: medium\nphase: utility\nfeedback-profile: execution\ncatalog-order: 140\n---\n\n# Import Skill — Quality Adaptation Pipeline\n\nAdapts an existing skill to match Arcana's quality standards. Works on skills imported via `arcana import` or any skill already in the skills directory that needs quality improvement.\n\n## Arguments\n\n```\n\u002Fimport-skill \u003Cskill-name>\n```\n\n- `skill-name`: name of the skill directory to adapt (must exist in the installed skills directory)\n\nIf no argument, list all installed skills and ask which one to adapt.\n\n## Gotchas\n\n1. **Rewriting content changes meaning.** When fixing tone or restructuring, the original skill's logic can drift. After every rewrite pass, re-read the original and verify the adapted version preserves every capability, every edge case, and every decision point.\n2. **\"Add missing sections\" can bloat the skill.** Not every skill needs Gotchas, not every skill needs edge case handling. A 50-line utility skill that lists files does not need a 20-line Gotchas section. Only add sections that genuinely improve the skill for its specific use case.\n3. **Description rewriting can break triggers.** The description is the triggering mechanism. Changing keywords, removing aliases, or being too specific can cause the skill to stop triggering correctly. If the original description triggered well, preserve its key phrases even while fixing voice\u002Fformat.\n4. **allowed-tools must be verified, not guessed.** Read every line of the skill body. If it says \"run `git diff`\", it needs Bash. If it says \"search the codebase\", it needs Grep\u002FGlob. Don't add tools the skill doesn't actually use, and don't miss tools it does use.\n\n## Step 1: Locate and Read\n\n1. Find the skill's SKILL.md in the installed skills directory\n2. Read `SKILL-AUTHORING-REFERENCE.md` from the Arcana package root — this is the quality standard\n3. Read the skill completely, including any supporting files in `references\u002F`\n4. Note the original source attribution comment if present (`\u003C!-- Imported by Arcana from: ... -->`)\n\n## Step 2: Audit Against Arcana Standards\n\nRun every check below. Record PASS or NEEDS FIX for each.\n\n### Frontmatter Checks\n\n| Check | Rule | How to Verify |\n|-------|------|--------------|\n| `name` | Lowercase kebab-case, matches directory name, under 64 chars | Regex: `\u002F^[a-z0-9]+(-[a-z0-9]+)*$\u002F` |\n| `description` | Third person, under 1024 chars, no XML tags, includes trigger phrases or has `disable-model-invocation: true` | Read it. Check voice. Count chars. |\n| `argument-hint` | Present if skill accepts arguments | Search body for argument parsing |\n| `allowed-tools` | Comma-separated, lists every tool the skill uses | Read every step, match tools to declarations |\n| `disable-model-invocation` | `true` if skill has side effects (writes files, runs commands, launches agents) | Search for Write, Edit, Bash, Agent in the body |\n| No unsupported fields | Only: name, description, argument-hint, disable-model-invocation, user-invocable, allowed-tools, effort | Compare against list |\n\n### Content Checks\n\n| Check | Rule | How to Verify |\n|-------|------|--------------|\n| Tone | Third-person imperative throughout | Search for \"I \", \"you \", \"we \", \"my \", \"your \" |\n| Line count | Under 500 lines | Count lines |\n| Structure | Clear phases\u002Fsteps with numbered sequence | Skim headers — should follow a logical flow |\n| Output format | Specifies what the user sees at the end | Search for output template or example |\n| Edge cases | Handles: empty results, missing files, user cancellation | Search for error handling guidance |\n| Hardcoded paths | No absolute paths, no project-specific paths | Search for `\u002FUsers\u002F`, `\u002Fhome\u002F`, `C:\\`, specific project names |\n| Gotchas | Present near top if skill has non-obvious failure modes | Only required if there ARE gotchas — don't add empty ones |\n\n### Quality Checks\n\n| Check | Rule | How to Verify |\n|-------|------|--------------|\n| Affirmative framing | \"Always do X\" preferred over \"Don't do Y\" | Count negative vs positive rules |\n| CAPS emphasis | At most 2-3 ALWAYS\u002FNEVER in caps | Count caps directives |\n| Examples | At least one concrete example for non-trivial skills | Search for code blocks or example sections |\n| Validation | \"Do → validate → fix\" pattern where applicable | Check if steps include verification |\n\n## Step 3: Present Assessment\n\nShow the user:\n\n```\n## Adaptation Assessment: \u003Cskill-name>\n\n**Source:** \u003Coriginal source from attribution comment>\n**Lines:** \u003Ccount> | **Frontmatter:** \u003CPASS\u002FFAIL> | **Tone:** \u003CPASS\u002FNEEDS FIX>\n\n### Checks\n\n| Category | Check | Status | Detail |\n|----------|-------|--------|--------|\n| Frontmatter | name | PASS | ... |\n| Frontmatter | description | NEEDS FIX | Uses first person |\n| Content | tone | NEEDS FIX | 12 instances of \"you should\" |\n| Content | line count | PASS | 340 lines |\n| Quality | gotchas | NEEDS FIX | Has 3 non-obvious failure modes, no Gotchas section |\n| ... | ... | ... | ... |\n\n### Proposed Changes\n\n1. Rewrite description to third person, add trigger phrases\n2. Convert 12 \"you should\" → imperative form\n3. Add Gotchas section with 3 items\n4. Add allowed-tools: Read, Grep, Glob, Bash\n5. Move reference tables to references\u002Fapi-patterns.md (currently 480 lines, would be 310 after split)\n\n**Proceed with these adaptations?**\n```\n\nWAIT for user confirmation before making any changes.\n\n## Step 4: Adapt\n\nApply each proposed change. For each change:\n\n1. Make the edit\n2. Re-read the affected section\n3. Verify the original intent is preserved\n\n### Adaptation order (do in this sequence):\n\n1. **Fix frontmatter** — name, description, allowed-tools, effort\n2. **Fix tone** — batch-convert first\u002Fsecond person to third-person imperative\n3. **Restructure if needed** — reorder sections per Arcana convention (Quick Start → Gotchas → Steps → Output → Rules)\n4. **Add missing sections** — only sections that genuinely add value\n5. **Split if over 500 lines** — extract reference material to `references\u002F`\n6. **Fix emphasis** — reduce CAPS to 2-3 critical rules max\n7. **Remove hardcoded content** — absolute paths, project-specific assumptions\n\nAfter all adaptations, show the user the complete adapted skill for final review.\n\n## Step 5: Verify\n\nAfter user confirms the final version:\n\n1. Write the adapted SKILL.md\n2. Run `node bin\u002Farcana.js info \u003Cskill-name>` to verify it parses correctly\n3. Run `node bin\u002Farcana.js list` to verify it appears\n4. Report the final line count and confirm it's under 500\n\n## Rules\n\n- NEVER modify a skill without user approval of the proposed changes\n- NEVER change the skill's core logic or capabilities — only adapt packaging and quality\n- ALWAYS read SKILL-AUTHORING-REFERENCE.md before auditing\n- ALWAYS present the assessment table before making changes\n- ALWAYS re-read original content after each rewrite to verify intent is preserved\n- ALWAYS verify the adapted skill parses correctly via `arcana info`\n- If the skill is under 50 lines and too vague to be useful, tell the user honestly\n- Preserve the source attribution comment\n- When splitting to references\u002F, the main SKILL.md must remain self-contained for the core workflow\n","# Import Skill — Quality Adaptation Pipeline\n\nAdapts an existing skill to match Arcana's quality standards. Works on skills imported via `arcana import` or any skill already in the skills directory that needs quality improvement.\n\n## Arguments\n\n```\n\u002Fimport-skill \u003Cskill-name>\n```\n\n- `skill-name`: name of the skill directory to adapt (must exist in the installed skills directory)\n\nIf no argument, list all installed skills and ask which one to adapt.\n\n## Gotchas\n\n1. **Rewriting content changes meaning.** When fixing tone or restructuring, the original skill's logic can drift. After every rewrite pass, re-read the original and verify the adapted version preserves every capability, every edge case, and every decision point.\n2. **\"Add missing sections\" can bloat the skill.** Not every skill needs Gotchas, not every skill needs edge case handling. A 50-line utility skill that lists files does not need a 20-line Gotchas section. Only add sections that genuinely improve the skill for its specific use case.\n3. **Description rewriting can break triggers.** The description is the triggering mechanism. Changing keywords, removing aliases, or being too specific can cause the skill to stop triggering correctly. If the original description triggered well, preserve its key phrases even while fixing voice\u002Fformat.\n4. **allowed-tools must be verified, not guessed.** Read every line of the skill body. If it says \"run `git diff`\", it needs Bash. If it says \"search the codebase\", it needs Grep\u002FGlob. Don't add tools the skill doesn't actually use, and don't miss tools it does use.\n\n## Step 1: Locate and Read\n\n1. Find the skill's SKILL.md in the installed skills directory\n2. Read `SKILL-AUTHORING-REFERENCE.md` from the Arcana package root — this is the quality standard\n3. Read the skill completely, including any supporting files in `references\u002F`\n4. Note the original source attribution comment if present (`\u003C!-- Imported by Arcana from: ... -->`)\n\n## Step 2: Audit Against Arcana Standards\n\nRun every check below. Record PASS or NEEDS FIX for each.\n\n### Frontmatter Checks\n\n| Check | Rule | How to Verify |\n|-------|------|--------------|\n| `name` | Lowercase kebab-case, matches directory name, under 64 chars | Regex: `\u002F^[a-z0-9]+(-[a-z0-9]+)*$\u002F` |\n| `description` | Third person, under 1024 chars, no XML tags, includes trigger phrases or has `disable-model-invocation: true` | Read it. Check voice. Count chars. |\n| `argument-hint` | Present if skill accepts arguments | Search body for argument parsing |\n| `allowed-tools` | Comma-separated, lists every tool the skill uses | Read every step, match tools to declarations |\n| `disable-model-invocation` | `true` if skill has side effects (writes files, runs commands, launches agents) | Search for Write, Edit, Bash, Agent in the body |\n| No unsupported fields | Only: name, description, argument-hint, disable-model-invocation, user-invocable, allowed-tools, effort | Compare against list |\n\n### Content Checks\n\n| Check | Rule | How to Verify |\n|-------|------|--------------|\n| Tone | Third-person imperative throughout | Search for \"I \", \"you \", \"we \", \"my \", \"your \" |\n| Line count | Under 500 lines | Count lines |\n| Structure | Clear phases\u002Fsteps with numbered sequence | Skim headers — should follow a logical flow |\n| Output format | Specifies what the user sees at the end | Search for output template or example |\n| Edge cases | Handles: empty results, missing files, user cancellation | Search for error handling guidance |\n| Hardcoded paths | No absolute paths, no project-specific paths | Search for `\u002FUsers\u002F`, `\u002Fhome\u002F`, `C:\\`, specific project names |\n| Gotchas | Present near top if skill has non-obvious failure modes | Only required if there ARE gotchas — don't add empty ones |\n\n### Quality Checks\n\n| Check | Rule | How to Verify |\n|-------|------|--------------|\n| Affirmative framing | \"Always do X\" preferred over \"Don't do Y\" | Count negative vs positive rules |\n| CAPS emphasis | At most 2-3 ALWAYS\u002FNEVER in caps | Count caps directives |\n| Examples | At least one concrete example for non-trivial skills | Search for code blocks or example sections |\n| Validation | \"Do → validate → fix\" pattern where applicable | Check if steps include verification |\n\n## Step 3: Present Assessment\n\nShow the user:\n\n```\n## Adaptation Assessment: \u003Cskill-name>\n\n**Source:** \u003Coriginal source from attribution comment>\n**Lines:** \u003Ccount> | **Frontmatter:** \u003CPASS\u002FFAIL> | **Tone:** \u003CPASS\u002FNEEDS FIX>\n\n### Checks\n\n| Category | Check | Status | Detail |\n|----------|-------|--------|--------|\n| Frontmatter | name | PASS | ... |\n| Frontmatter | description | NEEDS FIX | Uses first person |\n| Content | tone | NEEDS FIX | 12 instances of \"you should\" |\n| Content | line count | PASS | 340 lines |\n| Quality | gotchas | NEEDS FIX | Has 3 non-obvious failure modes, no Gotchas section |\n| ... | ... | ... | ... |\n\n### Proposed Changes\n\n1. Rewrite description to third person, add trigger phrases\n2. Convert 12 \"you should\" → imperative form\n3. Add Gotchas section with 3 items\n4. Add allowed-tools: Read, Grep, Glob, Bash\n5. Move reference tables to references\u002Fapi-patterns.md (currently 480 lines, would be 310 after split)\n\n**Proceed with these adaptations?**\n```\n\nWAIT for user confirmation before making any changes.\n\n## Step 4: Adapt\n\nApply each proposed change. For each change:\n\n1. Make the edit\n2. Re-read the affected section\n3. Verify the original intent is preserved\n\n### Adaptation order (do in this sequence):\n\n1. **Fix frontmatter** — name, description, allowed-tools, effort\n2. **Fix tone** — batch-convert first\u002Fsecond person to third-person imperative\n3. **Restructure if needed** — reorder sections per Arcana convention (Quick Start → Gotchas → Steps → Output → Rules)\n4. **Add missing sections** — only sections that genuinely add value\n5. **Split if over 500 lines** — extract reference material to `references\u002F`\n6. **Fix emphasis** — reduce CAPS to 2-3 critical rules max\n7. **Remove hardcoded content** — absolute paths, project-specific assumptions\n\nAfter all adaptations, show the user the complete adapted skill for final review.\n\n## Step 5: Verify\n\nAfter user confirms the final version:\n\n1. Write the adapted SKILL.md\n2. Run `node bin\u002Farcana.js info \u003Cskill-name>` to verify it parses correctly\n3. Run `node bin\u002Farcana.js list` to verify it appears\n4. Report the final line count and confirm it's under 500\n\n## Rules\n\n- NEVER modify a skill without user approval of the proposed changes\n- NEVER change the skill's core logic or capabilities — only adapt packaging and quality\n- ALWAYS read SKILL-AUTHORING-REFERENCE.md before auditing\n- ALWAYS present the assessment table before making changes\n- ALWAYS re-read original content after each rewrite to verify intent is preserved\n- ALWAYS verify the adapted skill parses correctly via `arcana info`\n- If the skill is under 50 lines and too vague to be useful, tell the user honestly\n- Preserve the source attribution comment\n- When splitting to references\u002F, the main SKILL.md must remain self-contained for the core workflow\n",{"name":5,"phase":26,"effort":48,"description":7,"allowed-tools":49,"argument-hint":50,"catalog-order":51,"feedback-profile":42,"disable-model-invocation":52},"medium","Read, Write, Edit, Glob, Grep, Bash","\u003Cskill-name>",140,true,"main","62a5cbde2da44ccf4660521f0e3b2286f71dcbfd","skills\u002Fimport-skill","https:\u002F\u002Fgithub.com\u002Fcj-ways\u002Farcana","https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002F@cj-ways\u002Farcana","https:\u002F\u002Fgithub.com\u002Fcj-ways","2026-04-27 15:57:45",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":52},[62,65,68],{"tool":63,"command":64},"npx","npx skills add cj-ways\u002Farcana --skill import-skill",{"tool":66,"command":67},"bunx","bunx skills add cj-ways\u002Farcana --skill import-skill",{"tool":69,"command":70},"pnpm","pnpm dlx skills add cj-ways\u002Farcana --skill import-skill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcj-ways\u002Farcana\u002Fblob\u002Fmain\u002Fskills\u002Fimport-skill\u002FSKILL.md",[],[74,107,129,149,170,194],{"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":88,"publishedAt":43},"01M6ER4PGRFCMZ3D11YCEQ7Q9H","v0-design","Generates optimized v0.dev prompts for UI design — full pages, single components, design systems, or redesigns. Analyzes the project, adapts questions to context, researches user-specified design references, and outputs ready-to-copy prompts following Vercel's three-part framework. Manual via \u002Fv0-design.","https:\u002F\u002Fgithub.com\u002Fcj-ways\u002Farcana\u002Fblob\u002Fmain\u002Fskills\u002Fv0-design\u002FSKILL.md",[80,83],{"categoryNo":81,"categoryName":82,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":84,"categoryName":85,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[89,90,91,92,93,94,95,96,38,37,97,98,99,100,101,102,103,104,105,106],"design","v0","v0 design","components","component","design systems","framework","ui","context","design-system","ready","ui design","references","three","project","full","feature","app",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":114,"publishedAt":43},"01M6ER4J1MAN09RA7ZVFQP5WC0","skill-scout","Scouts major skill providers for skills that match the current project — fetches catalogs, analyzes the codebase, cross-matches, and recommends with evidence. Critical assessment, not a dump of everything available. Manual via \u002Fskill-scout.","https:\u002F\u002Fgithub.com\u002Fcj-ways\u002Farcana\u002Fblob\u002Fmain\u002Fskills\u002Fskill-scout\u002FSKILL.md",[113],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[115,116,117,118,119,120,121,41,39,38,122,123,124,125,126,103,127,128,27,26],"skill scout","scout","testing","security","workflow","assessment","Providers","webfetch","ops","evidence","focus","advisory","critical","dump",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":43},"01M6ER4EGNXCNN8P05RKVCQXHC","security-check","Quick security scan — hardcoded secrets, common vulnerabilities, dependency issues. Use when the user asks to check security, scan for secrets, or audit for vulnerabilities. Manual via \u002Fsecurity-check.","https:\u002F\u002Fgithub.com\u002Fcj-ways\u002Farcana\u002Fblob\u002Fmain\u002Fskills\u002Fsecurity-check\u002FSKILL.md",[],[118,136,137,138,139,140,141,142,41,143,144,39,38,122,145,146,147,148,27,26],"check","security check","vulnerabilities","issues","security scan","audit","secrets","deps","common","use","dependency","scan","scope",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":155,"publishedAt":43},"01M6ER4A08G4CPT443J7XSHDJQ","release-check","Analyzes branch diff to generate deploy checklists — env vars, migrations, new services, dependencies, schema changes, breaking changes. Works across any tech stack. Manual via \u002Frelease-check [source] [target].","https:\u002F\u002Fgithub.com\u002Fcj-ways\u002Farcana\u002Fblob\u002Fmain\u002Fskills\u002Frelease-check\u002FSKILL.md",[],[156,157,136,158,159,160,42,41,161,39,162,38,163,164,165,166,167,168,27,169],"release","release check","generate","env vars","services","stack","branch","diff","schema","migrations","dependencies","across","env","tech",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":179,"publishedAt":43},"01M6ER45AQCN9RDAXZA5A5W03C","refactor-plan","Plans and executes safe multi-file refactoring — maps dependency graph, batches changes into atomic commits, runs tests between batches. Prevents the cascading-breakage pattern where agents make sweeping changes that fail halfway. Use for renames, extractions, moves, or structural changes across multiple files. Manual via \u002Frefactor-plan.","https:\u002F\u002Fgithub.com\u002Fcj-ways\u002Farcana\u002Fblob\u002Fmain\u002Fskills\u002Frefactor-plan\u002FSKILL.md",[176],{"categoryNo":177,"categoryName":178,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查",[180,181,182,183,184,185,41,186,187,38,37,36,146,188,189,190,191,167,192,193],"refactor plan","refactor","plan","safe","graph","commits","refactoring","atomic commits","dependency graph","files","maps","pattern","structural","make",{"skillNo":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":198,"categories":199,"keywords":204,"publishedAt":43},"01M6ER41VW96NCAMSQF8SV31J7","quick-review","Fast single-pass code review with strong false-positive suppression. Reviews git diff for runtime errors, data corruption, security breaches, operational incidents. Use for PR reviews and quick change validation. Manual via \u002Fquick-review.","https:\u002F\u002Fgithub.com\u002Fcj-ways\u002Farcana\u002Fblob\u002Fmain\u002Fskills\u002Fquick-review\u002FSKILL.md",[200,201],{"categoryNo":177,"categoryName":178,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":202,"categoryName":203,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000030","开发工程师",[205,206,207,208,209,210,211,212,213,41,39,162,38,145,163,189,103,214,215,27],"review","quick review","code review","change","pr","code","validation","worktree","false-positive","runtime","false"]