[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F4MMR2J04BTB8BZ7MYG08B":3,"skill-same:01M7F4MMR2J04BTB8BZ7MYG08B":52},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":45},"01M7F4MMR2J04BTB8BZ7MYG08B","skill-audit",null,"Audit codebases for quality, consistency, and broken patterns — use for pre-release or tech debt review","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fskill-audit\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: skill-audit\ndescription: \"Audit codebases for quality, consistency, and broken patterns — use for pre-release or tech debt review\"\ndisable-model-invocation: true\n---\n\n> **Host: Codex CLI** — This skill was designed for Claude Code and adapted for Codex.\n> Cross-reference commands use installed skill names in Codex rather than `\u002Focto:*` slash commands.\n> Use the active Codex shell and subagent tools. Do not claim a provider, model, or host subagent is available until the current session exposes it.\n> For host tool equivalents, see `skills\u002Fblocks\u002Fcodex-host-adapter.md`.\n\n\n# Systematic Audit Process\n\nLoad `skills\u002Fblocks\u002Fengineering-method-selection.md` from the installed plugin\nand apply only the methods relevant to this task. Preserve this entry point's\nexecution contract and output format. Read referenced skills as instructions;\ndo not invoke the current command recursively or add provider calls from a seat.\n\n## Overview\n\nComprehensive, methodical auditing to find issues, inconsistencies, and broken features across a codebase.\n\n**Core principle:** Define scope → Create checklist → Execute systematically → Report findings → Prioritize fixes.\n\nFor architecture simplification, load\n`skills\u002Fblocks\u002Farchitecture-simplification.md`. Pin the revision, inspect recent\nchurn and representative callers, then apply the deletion test. Do not recommend\nremoving a small wrapper when it centralizes a security, cleanup, precedence, or\nfailure invariant. A `simplify` verdict needs source evidence, a concrete caller,\nand migration and rollback steps.\n\n\n## When to Use\n\n**Use this skill when user wants to:**\n- Audit entire application for issues\n- Find all instances of a problem pattern\n- Check for broken features systematically\n- Comprehensive quality verification\n- Identify inconsistencies across codebase\n\n**Do NOT use for:**\n- Security vulnerability scanning (use skill-security-audit)\n- Code quality review (use skill-code-review)\n- Single file searches (use Grep\u002FGlob directly)\n- Performance profiling\n\n\n## The Process\n\n### Phase 1: Scope Definition\n\n#### Step 1: Understand Audit Objectives\n\n```markdown\n**Audit Objectives:**\n\nWhat to audit: [app features, code patterns, specific issues]\nWhy auditing: [what prompted this, what problem are we solving]\nScope: [entire app, specific module, particular feature set]\nDepth: [surface-level or deep inspection]\n```\n\n#### Step 2: Define Audit Criteria\n\nUse AskUserQuestion if needed:\n\n```markdown\n**Audit Focus:**\n\nWhich aspects should I audit?\n1. Functional - Do features work as expected?\n2. Consistency - Are patterns applied uniformly?\n3. Completeness - Are implementations finished?\n4. Quality - Is code maintainable?\n5. User-facing - Does UI\u002FUX work correctly?\n6. Integration - Do components work together?\n```\n\n#### Step 3: Create Audit Plan\n\n```markdown\n**Audit Plan**\n\n**Areas to Cover:**\n1. [Area 1: e.g., All form submissions]\n2. [Area 2: e.g., All API endpoints]\n3. [Area 3: e.g., All button states]\n4. [Area 4: e.g., All error handling]\n\n**Methodology:**\n- [ ] Identify all instances\n- [ ] Test each systematically\n- [ ] Document findings\n- [ ] Categorize by severity\n- [ ] Propose fixes\n\n**Estimated Coverage:** [X components, Y files, Z features]\n```\n\n\n### Phase 2: Discovery\n\n#### Step 1: Identify Audit Targets\n\nUse Glob and Grep to find all relevant code:\n\n```markdown\n**Finding Audit Targets:**\n\nSearching for: [pattern\u002Ffeature]\nMethod: [glob pattern or grep query]\n\n**Found:**\n1. [File 1:line]\n2. [File 2:line]\n3. [File 3:line]\n...\nN. [File N:line]\n\nTotal instances: [N]\n```\n\n#### Step 2: Create Audit Checklist\n\n```markdown\n**Audit Checklist:**\n\n- [ ] Item 1: [component\u002Ffeature to check]\n  - Location: [file:line]\n  - Expected: [what should happen]\n  - Test: [how to verify]\n\n- [ ] Item 2: [component\u002Ffeature to check]\n  - Location: [file:line]\n  - Expected: [what should happen]\n  - Test: [how to verify]\n\n...\n\nTotal items to audit: [N]\n```\n\nUse task plan tool to track audit progress.\n\n\n### Phase 3: Systematic Execution\n\n#### Step 1: Execute Audit Checklist\n\nFor each item:\n\n```markdown\n**Auditing Item [N]\u002F[Total]: [Description]**\n\n**Location:** [file:line]\n\n**Check 1: [Test name]**\n- Expected: [what should happen]\n- Method: [how to test - code review, runtime check, etc.]\n- Result: ✓ Pass \u002F ❌ Fail\n- Evidence: [what you observed]\n\n**Check 2: [Test name]**\n- Expected: [what should happen]\n- Method: [how to test]\n- Result: ✓ Pass \u002F ❌ Fail\n- Evidence: [what you observed]\n\n**Overall Status:** ✓ Pass \u002F ⚠️ Issues Found \u002F ❌ Broken\n\n**Issues:**\n[If any issues, list them here]\n\n```\n\n#### Step 2: Track Progress\n\n```\nAudit Progress:\n✓ [1\u002F50] User login form\n✓ [2\u002F50] Password reset form\n⚠️ [3\u002F50] Registration form (issues found)\n❌ [4\u002F50] Contact form (broken)\n⚙️ [5\u002F50] Newsletter signup (in progress)\n- [6\u002F50] Survey form\n...\n```\n\n\n### Phase 4: Analysis & Reporting\n\n#### Step 1: Categorize Findings\n\n```markdown\n**Audit Findings Summary**\n\n**Critical Issues (Broken Functionality):**\n1. [Issue 1]\n   - Location: [file:line]\n   - Impact: [what's broken]\n   - Severity: Critical\n\n2. [Issue 2]\n   - Location: [file:line]\n   - Impact: [what's broken]\n   - Severity: Critical\n\n**Major Issues (Degraded Functionality):**\n1. [Issue 1]\n   - Location: [file:line]\n   - Impact: [what's wrong]\n   - Severity: Major\n\n**Minor Issues (Inconsistencies\u002FPolish):**\n1. [Issue 1]\n   - Location: [file:line]\n   - Impact: [what's inconsistent]\n   - Severity: Minor\n\n**Passed Checks:**\n- [N] items fully functional\n- [List if relevant]\n```\n\n#### Step 2: Provide Statistics\n\n```markdown\n**Audit Statistics**\n\nTotal Items Audited: [N]\n✓ Passed: [N] ([X%])\n⚠️ Issues Found: [N] ([X%])\n❌ Broken: [N] ([X%])\n\n**By Category:**\n- Critical: [N]\n- Major: [N]\n- Minor: [N]\n\n**Coverage:**\n- Files reviewed: [N]\n- Components tested: [N]\n- Code paths verified: [N]\n```\n\n\n### Phase 5: Remediation Plan\n\n#### Step 1: Prioritize Issues\n\n```markdown\n**Recommended Fix Priority:**\n\n**Phase 1: Critical Fixes (Do First)**\n1. [Issue - file:line]\n   - Why critical: [reason]\n   - Estimated effort: [time]\n\n2. [Issue - file:line]\n   - Why critical: [reason]\n   - Estimated effort: [time]\n\n**Phase 2: Major Fixes (Do Next)**\n1. [Issue - file:line]\n   - Impact: [description]\n   - Estimated effort: [time]\n\n**Phase 3: Minor Fixes (Nice to Have)**\n1. [Issue - file:line]\n   - Impact: [description]\n   - Estimated effort: [time]\n\n**Total Estimated Effort:** [sum of all fixes]\n```\n\n#### Step 2: Offer to Execute Fixes\n\n```markdown\n**Next Steps:**\n\nI found [N] issues during the audit.\n\nWould you like me to:\n1. Fix all critical issues now (estimated [time])\n2. Fix issues one category at a time (critical → major → minor)\n3. Let you review findings first, then decide what to fix\n4. Create detailed tickets\u002Ftodos for each issue\n\nWhat's your preference?\n```\n\n\n## Common Patterns\n\n### Pattern 1: Audit Entire App for Broken Features\n\n```\nUser: \"Create a process to audit and check the entire app for things that might be broken\"\n\nImplementation:\n\n**Phase 1: Scope**\n- Audit all user-facing features\n- Check for runtime errors\n- Verify expected behavior\n\n**Phase 2: Discovery**\n- List all features (from routes, components, docs)\n- Create comprehensive checklist\n\n**Phase 3: Execute**\n- Test each feature systematically\n- Document working vs broken\n\n**Phase 4: Report**\n- Critical: Features that crash\n- Major: Features that work incorrectly\n- Minor: Features with UX issues\n\n**Phase 5: Fix**\n- Prioritized remediation plan\n```\n\n### Pattern 2: Audit for Specific Pattern\n\n```\nUser: \"Find all instances of direct DOM manipulation and check if they should use React state\"\n\nImplementation:\n\n**Phase 1: Scope**\n- Audit: Direct DOM manipulation patterns\n- Goal: Identify React anti-patterns\n\n**Phase 2: Discovery**\n- Grep for: document.querySelector, getElementById, etc.\n- Found: [N] instances\n\n**Phase 3: Execute**\n- Check each instance:\n  - Is there a good reason for direct DOM?\n  - Should it use React state instead?\n  - Is it causing bugs?\n\n**Phase 4: Report**\n- List instances that should migrate to React\n- List instances that are fine as-is\n\n**Phase 5: Fix**\n- Refactor problematic instances\n```\n\n### Pattern 3: Consistency Audit\n\n```\nUser: \"Audit the app for button style consistency\"\n\nImplementation:\n\n**Phase 1: Scope**\n- Audit: All button elements\n- Goal: Ensure consistent styling\n\n**Phase 2: Discovery**\n- Find all buttons in codebase\n- Identify button component(s)\n\n**Phase 3: Execute**\n- Check each button against style guide\n- Document inconsistencies\n\n**Phase 4: Report**\n- Buttons using correct component: [N]\n- Buttons with inconsistent styles: [N]\n- Buttons using deprecated patterns: [N]\n\n**Phase 5: Fix**\n- Standardize all buttons to design system\n```\n\n\n## Integration with Other Skills\n\n### With skill-debug\n\n```\nAudit found a broken feature?\n→ Use skill-debug to investigate root cause\n→ Use systematic debugging to fix\n```\n\n### With skill-visual-feedback\n\n```\nAudit found UI inconsistencies?\n→ Use skill-visual-feedback to fix visual issues\n→ Ensure consistency across app\n```\n\n### With skill-iterative-loop\n\n```\nLarge audit with many items?\n→ Use skill-iterative-loop to process in batches\n→ Loop through sections of the app\n```\n\n### With skill-security-audit\n\n```\nAudit includes security concerns?\n→ Delegate security-specific checks to skill-security-audit\n→ Use skill-audit for functional checks\n```\n\n\n## Best Practices\n\n### 1. Be Systematic, Not Random\n\n**Good:**\n```\nAuditing all form submissions:\n1. Login form\n2. Registration form\n3. Password reset form\n4. Contact form\n5. Newsletter signup\n...\n(Methodical, complete)\n```\n\n**Poor:**\n```\nChecking some forms:\n- Login form\n- Maybe that contact thing\n- Whatever else I find\n(Random, incomplete)\n```\n\n### 2. Document Everything\n\nFor each audit item, record:\n- What was checked\n- How it was checked\n- Result (pass\u002Ffail)\n- Evidence (what you observed)\n\n### 3. Use Categories\n\nGroup findings into meaningful categories:\n- By severity (critical, major, minor)\n- By type (functional, UI, consistency, performance)\n- By component (forms, navigation, data display)\n\n### 4. Make Findings Actionable\n\n**Good:**\n```\nIssue: Registration form submit button doesn't work\nLocation: src\u002Fcomponents\u002FRegisterForm.tsx:45\nRoot cause: onClick handler missing\nFix: Add onClick={handleSubmit}\nEffort: 5 minutes\n```\n\n**Poor:**\n```\nIssue: Some button broken somewhere\nFix: Fix it\n```\n\n\n## Red Flags - Don't Do This\n\n| Action | Why It's Wrong |\n|--------|----------------|\n| Skip creating checklist | Will miss things, duplicate work |\n| Test randomly without system | Incomplete coverage |\n| Not documenting findings | Can't prioritize or fix later |\n| Audit without clear criteria | Don't know what \"pass\" means |\n| Fix while auditing | Confuses audit with remediation |\n| Ignore patterns | Miss systemic issues |\n\n\n## Audit Templates\n\n### Template 1: Functional Feature Audit\n\n```markdown\n**Feature:** [Name]\n**Location:** [file:line]\n\n**Tests:**\n- [ ] Feature loads without errors\n- [ ] Feature responds to user input\n- [ ] Feature displays correct data\n- [ ] Feature handles errors gracefully\n- [ ] Feature works on mobile\n- [ ] Feature is accessible\n\n**Result:** ✓ Pass \u002F ⚠️ Issues \u002F ❌ Broken\n**Issues:** [if any]\n```\n\n### Template 2: Code Pattern Audit\n\n```markdown\n**Pattern:** [What to check]\n**Instance:** [file:line]\n\n**Checks:**\n- [ ] Follows current best practices\n- [ ] Consistent with codebase\n- [ ] No deprecated APIs used\n- [ ] Properly typed\u002Fdocumented\n- [ ] No obvious bugs\n\n**Result:** ✓ Good \u002F ⚠️ Needs update \u002F ❌ Problematic\n**Notes:** [any observations]\n```\n\n### Template 3: UI Consistency Audit\n\n```markdown\n**Component:** [Name]\n**Location:** [file:line]\n\n**Checks:**\n- [ ] Uses design system components\n- [ ] Follows spacing guidelines\n- [ ] Uses correct colors\n- [ ] Typography consistent\n- [ ] Responsive design works\n- [ ] States handled (hover, active, disabled)\n\n**Result:** ✓ Consistent \u002F ⚠️ Minor issues \u002F ❌ Inconsistent\n**Issues:** [if any]\n```\n\n\n## Quick Reference\n\n| Audit Type | Discovery Method | Check Method | Output |\n|------------|------------------|--------------|--------|\n| Functional | List features | Test each | Pass\u002Ffail report |\n| Pattern | Grep for code | Review each instance | Compliant\u002Fnon-compliant |\n| Consistency | Find all instances | Compare to standard | Consistent\u002Finconsistent |\n| Completeness | List requirements | Verify each exists | Complete\u002Fincomplete |\n\n\n## The Bottom Line\n\n```\nSystematic audit → Complete checklist + Methodical execution + Prioritized findings\nOtherwise → Missed issues + Duplicate work + No clear action plan\n```\n\n**Define scope. Create checklist. Execute systematically. Report findings. Prioritize fixes.**\n","> **Host: Codex CLI** — This skill was designed for Claude Code and adapted for Codex.\n> Cross-reference commands use installed skill names in Codex rather than `\u002Focto:*` slash commands.\n> Use the active Codex shell and subagent tools. Do not claim a provider, model, or host subagent is available until the current session exposes it.\n> For host tool equivalents, see `skills\u002Fblocks\u002Fcodex-host-adapter.md`.\n\n\n# Systematic Audit Process\n\nLoad `skills\u002Fblocks\u002Fengineering-method-selection.md` from the installed plugin\nand apply only the methods relevant to this task. Preserve this entry point's\nexecution contract and output format. Read referenced skills as instructions;\ndo not invoke the current command recursively or add provider calls from a seat.\n\n## Overview\n\nComprehensive, methodical auditing to find issues, inconsistencies, and broken features across a codebase.\n\n**Core principle:** Define scope → Create checklist → Execute systematically → Report findings → Prioritize fixes.\n\nFor architecture simplification, load\n`skills\u002Fblocks\u002Farchitecture-simplification.md`. Pin the revision, inspect recent\nchurn and representative callers, then apply the deletion test. Do not recommend\nremoving a small wrapper when it centralizes a security, cleanup, precedence, or\nfailure invariant. A `simplify` verdict needs source evidence, a concrete caller,\nand migration and rollback steps.\n\n\n## When to Use\n\n**Use this skill when user wants to:**\n- Audit entire application for issues\n- Find all instances of a problem pattern\n- Check for broken features systematically\n- Comprehensive quality verification\n- Identify inconsistencies across codebase\n\n**Do NOT use for:**\n- Security vulnerability scanning (use skill-security-audit)\n- Code quality review (use skill-code-review)\n- Single file searches (use Grep\u002FGlob directly)\n- Performance profiling\n\n\n## The Process\n\n### Phase 1: Scope Definition\n\n#### Step 1: Understand Audit Objectives\n\n```markdown\n**Audit Objectives:**\n\nWhat to audit: [app features, code patterns, specific issues]\nWhy auditing: [what prompted this, what problem are we solving]\nScope: [entire app, specific module, particular feature set]\nDepth: [surface-level or deep inspection]\n```\n\n#### Step 2: Define Audit Criteria\n\nUse AskUserQuestion if needed:\n\n```markdown\n**Audit Focus:**\n\nWhich aspects should I audit?\n1. Functional - Do features work as expected?\n2. Consistency - Are patterns applied uniformly?\n3. Completeness - Are implementations finished?\n4. Quality - Is code maintainable?\n5. User-facing - Does UI\u002FUX work correctly?\n6. Integration - Do components work together?\n```\n\n#### Step 3: Create Audit Plan\n\n```markdown\n**Audit Plan**\n\n**Areas to Cover:**\n1. [Area 1: e.g., All form submissions]\n2. [Area 2: e.g., All API endpoints]\n3. [Area 3: e.g., All button states]\n4. [Area 4: e.g., All error handling]\n\n**Methodology:**\n- [ ] Identify all instances\n- [ ] Test each systematically\n- [ ] Document findings\n- [ ] Categorize by severity\n- [ ] Propose fixes\n\n**Estimated Coverage:** [X components, Y files, Z features]\n```\n\n\n### Phase 2: Discovery\n\n#### Step 1: Identify Audit Targets\n\nUse Glob and Grep to find all relevant code:\n\n```markdown\n**Finding Audit Targets:**\n\nSearching for: [pattern\u002Ffeature]\nMethod: [glob pattern or grep query]\n\n**Found:**\n1. [File 1:line]\n2. [File 2:line]\n3. [File 3:line]\n...\nN. [File N:line]\n\nTotal instances: [N]\n```\n\n#### Step 2: Create Audit Checklist\n\n```markdown\n**Audit Checklist:**\n\n- [ ] Item 1: [component\u002Ffeature to check]\n  - Location: [file:line]\n  - Expected: [what should happen]\n  - Test: [how to verify]\n\n- [ ] Item 2: [component\u002Ffeature to check]\n  - Location: [file:line]\n  - Expected: [what should happen]\n  - Test: [how to verify]\n\n...\n\nTotal items to audit: [N]\n```\n\nUse task plan tool to track audit progress.\n\n\n### Phase 3: Systematic Execution\n\n#### Step 1: Execute Audit Checklist\n\nFor each item:\n\n```markdown\n**Auditing Item [N]\u002F[Total]: [Description]**\n\n**Location:** [file:line]\n\n**Check 1: [Test name]**\n- Expected: [what should happen]\n- Method: [how to test - code review, runtime check, etc.]\n- Result: ✓ Pass \u002F ❌ Fail\n- Evidence: [what you observed]\n\n**Check 2: [Test name]**\n- Expected: [what should happen]\n- Method: [how to test]\n- Result: ✓ Pass \u002F ❌ Fail\n- Evidence: [what you observed]\n\n**Overall Status:** ✓ Pass \u002F ⚠️ Issues Found \u002F ❌ Broken\n\n**Issues:**\n[If any issues, list them here]\n\n```\n\n#### Step 2: Track Progress\n\n```\nAudit Progress:\n✓ [1\u002F50] User login form\n✓ [2\u002F50] Password reset form\n⚠️ [3\u002F50] Registration form (issues found)\n❌ [4\u002F50] Contact form (broken)\n⚙️ [5\u002F50] Newsletter signup (in progress)\n- [6\u002F50] Survey form\n...\n```\n\n\n### Phase 4: Analysis & Reporting\n\n#### Step 1: Categorize Findings\n\n```markdown\n**Audit Findings Summary**\n\n**Critical Issues (Broken Functionality):**\n1. [Issue 1]\n   - Location: [file:line]\n   - Impact: [what's broken]\n   - Severity: Critical\n\n2. [Issue 2]\n   - Location: [file:line]\n   - Impact: [what's broken]\n   - Severity: Critical\n\n**Major Issues (Degraded Functionality):**\n1. [Issue 1]\n   - Location: [file:line]\n   - Impact: [what's wrong]\n   - Severity: Major\n\n**Minor Issues (Inconsistencies\u002FPolish):**\n1. [Issue 1]\n   - Location: [file:line]\n   - Impact: [what's inconsistent]\n   - Severity: Minor\n\n**Passed Checks:**\n- [N] items fully functional\n- [List if relevant]\n```\n\n#### Step 2: Provide Statistics\n\n```markdown\n**Audit Statistics**\n\nTotal Items Audited: [N]\n✓ Passed: [N] ([X%])\n⚠️ Issues Found: [N] ([X%])\n❌ Broken: [N] ([X%])\n\n**By Category:**\n- Critical: [N]\n- Major: [N]\n- Minor: [N]\n\n**Coverage:**\n- Files reviewed: [N]\n- Components tested: [N]\n- Code paths verified: [N]\n```\n\n\n### Phase 5: Remediation Plan\n\n#### Step 1: Prioritize Issues\n\n```markdown\n**Recommended Fix Priority:**\n\n**Phase 1: Critical Fixes (Do First)**\n1. [Issue - file:line]\n   - Why critical: [reason]\n   - Estimated effort: [time]\n\n2. [Issue - file:line]\n   - Why critical: [reason]\n   - Estimated effort: [time]\n\n**Phase 2: Major Fixes (Do Next)**\n1. [Issue - file:line]\n   - Impact: [description]\n   - Estimated effort: [time]\n\n**Phase 3: Minor Fixes (Nice to Have)**\n1. [Issue - file:line]\n   - Impact: [description]\n   - Estimated effort: [time]\n\n**Total Estimated Effort:** [sum of all fixes]\n```\n\n#### Step 2: Offer to Execute Fixes\n\n```markdown\n**Next Steps:**\n\nI found [N] issues during the audit.\n\nWould you like me to:\n1. Fix all critical issues now (estimated [time])\n2. Fix issues one category at a time (critical → major → minor)\n3. Let you review findings first, then decide what to fix\n4. Create detailed tickets\u002Ftodos for each issue\n\nWhat's your preference?\n```\n\n\n## Common Patterns\n\n### Pattern 1: Audit Entire App for Broken Features\n\n```\nUser: \"Create a process to audit and check the entire app for things that might be broken\"\n\nImplementation:\n\n**Phase 1: Scope**\n- Audit all user-facing features\n- Check for runtime errors\n- Verify expected behavior\n\n**Phase 2: Discovery**\n- List all features (from routes, components, docs)\n- Create comprehensive checklist\n\n**Phase 3: Execute**\n- Test each feature systematically\n- Document working vs broken\n\n**Phase 4: Report**\n- Critical: Features that crash\n- Major: Features that work incorrectly\n- Minor: Features with UX issues\n\n**Phase 5: Fix**\n- Prioritized remediation plan\n```\n\n### Pattern 2: Audit for Specific Pattern\n\n```\nUser: \"Find all instances of direct DOM manipulation and check if they should use React state\"\n\nImplementation:\n\n**Phase 1: Scope**\n- Audit: Direct DOM manipulation patterns\n- Goal: Identify React anti-patterns\n\n**Phase 2: Discovery**\n- Grep for: document.querySelector, getElementById, etc.\n- Found: [N] instances\n\n**Phase 3: Execute**\n- Check each instance:\n  - Is there a good reason for direct DOM?\n  - Should it use React state instead?\n  - Is it causing bugs?\n\n**Phase 4: Report**\n- List instances that should migrate to React\n- List instances that are fine as-is\n\n**Phase 5: Fix**\n- Refactor problematic instances\n```\n\n### Pattern 3: Consistency Audit\n\n```\nUser: \"Audit the app for button style consistency\"\n\nImplementation:\n\n**Phase 1: Scope**\n- Audit: All button elements\n- Goal: Ensure consistent styling\n\n**Phase 2: Discovery**\n- Find all buttons in codebase\n- Identify button component(s)\n\n**Phase 3: Execute**\n- Check each button against style guide\n- Document inconsistencies\n\n**Phase 4: Report**\n- Buttons using correct component: [N]\n- Buttons with inconsistent styles: [N]\n- Buttons using deprecated patterns: [N]\n\n**Phase 5: Fix**\n- Standardize all buttons to design system\n```\n\n\n## Integration with Other Skills\n\n### With skill-debug\n\n```\nAudit found a broken feature?\n→ Use skill-debug to investigate root cause\n→ Use systematic debugging to fix\n```\n\n### With skill-visual-feedback\n\n```\nAudit found UI inconsistencies?\n→ Use skill-visual-feedback to fix visual issues\n→ Ensure consistency across app\n```\n\n### With skill-iterative-loop\n\n```\nLarge audit with many items?\n→ Use skill-iterative-loop to process in batches\n→ Loop through sections of the app\n```\n\n### With skill-security-audit\n\n```\nAudit includes security concerns?\n→ Delegate security-specific checks to skill-security-audit\n→ Use skill-audit for functional checks\n```\n\n\n## Best Practices\n\n### 1. Be Systematic, Not Random\n\n**Good:**\n```\nAuditing all form submissions:\n1. Login form\n2. Registration form\n3. Password reset form\n4. Contact form\n5. Newsletter signup\n...\n(Methodical, complete)\n```\n\n**Poor:**\n```\nChecking some forms:\n- Login form\n- Maybe that contact thing\n- Whatever else I find\n(Random, incomplete)\n```\n\n### 2. Document Everything\n\nFor each audit item, record:\n- What was checked\n- How it was checked\n- Result (pass\u002Ffail)\n- Evidence (what you observed)\n\n### 3. Use Categories\n\nGroup findings into meaningful categories:\n- By severity (critical, major, minor)\n- By type (functional, UI, consistency, performance)\n- By component (forms, navigation, data display)\n\n### 4. Make Findings Actionable\n\n**Good:**\n```\nIssue: Registration form submit button doesn't work\nLocation: src\u002Fcomponents\u002FRegisterForm.tsx:45\nRoot cause: onClick handler missing\nFix: Add onClick={handleSubmit}\nEffort: 5 minutes\n```\n\n**Poor:**\n```\nIssue: Some button broken somewhere\nFix: Fix it\n```\n\n\n## Red Flags - Don't Do This\n\n| Action | Why It's Wrong |\n|--------|----------------|\n| Skip creating checklist | Will miss things, duplicate work |\n| Test randomly without system | Incomplete coverage |\n| Not documenting findings | Can't prioritize or fix later |\n| Audit without clear criteria | Don't know what \"pass\" means |\n| Fix while auditing | Confuses audit with remediation |\n| Ignore patterns | Miss systemic issues |\n\n\n## Audit Templates\n\n### Template 1: Functional Feature Audit\n\n```markdown\n**Feature:** [Name]\n**Location:** [file:line]\n\n**Tests:**\n- [ ] Feature loads without errors\n- [ ] Feature responds to user input\n- [ ] Feature displays correct data\n- [ ] Feature handles errors gracefully\n- [ ] Feature works on mobile\n- [ ] Feature is accessible\n\n**Result:** ✓ Pass \u002F ⚠️ Issues \u002F ❌ Broken\n**Issues:** [if any]\n```\n\n### Template 2: Code Pattern Audit\n\n```markdown\n**Pattern:** [What to check]\n**Instance:** [file:line]\n\n**Checks:**\n- [ ] Follows current best practices\n- [ ] Consistent with codebase\n- [ ] No deprecated APIs used\n- [ ] Properly typed\u002Fdocumented\n- [ ] No obvious bugs\n\n**Result:** ✓ Good \u002F ⚠️ Needs update \u002F ❌ Problematic\n**Notes:** [any observations]\n```\n\n### Template 3: UI Consistency Audit\n\n```markdown\n**Component:** [Name]\n**Location:** [file:line]\n\n**Checks:**\n- [ ] Uses design system components\n- [ ] Follows spacing guidelines\n- [ ] Uses correct colors\n- [ ] Typography consistent\n- [ ] Responsive design works\n- [ ] States handled (hover, active, disabled)\n\n**Result:** ✓ Consistent \u002F ⚠️ Minor issues \u002F ❌ Inconsistent\n**Issues:** [if any]\n```\n\n\n## Quick Reference\n\n| Audit Type | Discovery Method | Check Method | Output |\n|------------|------------------|--------------|--------|\n| Functional | List features | Test each | Pass\u002Ffail report |\n| Pattern | Grep for code | Review each instance | Compliant\u002Fnon-compliant |\n| Consistency | Find all instances | Compare to standard | Consistent\u002Finconsistent |\n| Completeness | List requirements | Verify each exists | Complete\u002Fincomplete |\n\n\n## The Bottom Line\n\n```\nSystematic audit → Complete checklist + Methodical execution + Prioritized findings\nOtherwise → Missed issues + Duplicate work + No clear action plan\n```\n\n**Define scope. Create checklist. Execute systematically. Report findings. Prioritize fixes.**\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","05-技能与代理开发\u002Fskill-audit",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":24},[35,38,41],{"tool":36,"command":37},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill skill-audit",{"tool":39,"command":40},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill skill-audit",{"tool":42,"command":43},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill skill-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fskill-audit\u002FSKILL.md",[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",166,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fskill-audit\u002Fagents\u002Fopenai.yaml",[53,60,65,72,79,86],{"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},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],{"skillNo":61,"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":62,"categories":63,"keywords":64,"publishedAt":19},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]