[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70HAP4RSAQKPKSDQCDDEMCF":3,"skill-same:01M70HAP4RSAQKPKSDQCDDEMCF":81},{"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":31,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":59,"commitSha":60,"skillDirectory":61,"forksCount":62,"repositoryHtmlUrl":63,"repositoryHomepageUrl":6,"ownerHtmlUrl":64,"ownerBlogUrl":6,"ownerDescription":65,"updatedAt":66,"install":67,"resources":80},"01M70HAP4RSAQKPKSDQCDDEMCF","verification-loop",null,"Run a six-phase verification of a Claude Code session's work — build, type check, lint, tests with coverage, security grep, and diff review — then produce a PASS\u002FFAIL verification report. Use when verifying work after completing a feature or refactor, before creating a PR, or when quality gates must pass.","mdnaimul22\u002Fhuman-skills","mdnaimul22","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F64520358?v=4","01M70FH95MH2H796Q01TYSFZ03","Naimul","01M70FH96798CQR4YHA13F17GA",3,"MIT","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fverification-loop\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"verification","loop","verification loop","work","when","phase","diff review","feature","tests","diff","use","session","coverage","review","refactor","produce","code","run","pr","security","2026-11-10 10:12:30",false,"---\nname: verification-loop\ndescription: Run a six-phase verification of a Claude Code session's work — build, type check, lint, tests with coverage, security grep, and diff review — then produce a PASS\u002FFAIL verification report. Use when verifying work after completing a feature or refactor, before creating a PR, or when quality gates must pass.\nlicense: MIT\nmetadata:\n  origin: ECC\n---\n\n# Verification Loop Skill\n\nA comprehensive verification system for Claude Code sessions.\n\n## When to Use\n\nInvoke this skill:\n- After completing a feature or significant code change\n- Before creating a PR\n- When you want to ensure quality gates pass\n- After refactoring\n\n## Verification Phases\n\n### Phase 1: Build Verification\n```bash\nset -o pipefail  # report the build's exit status, not tail's\n# Check if project builds\nnpm run build 2>&1 | tail -20\n# OR\npnpm build 2>&1 | tail -20\n```\n\nIf build fails, STOP and fix before continuing.\n\n### Phase 2: Type Check\n```bash\nset -o pipefail\n# TypeScript projects\nnpx --no-install tsc --noEmit 2>&1 | sed -n '1,30p'\n\n# Python projects\npyright . 2>&1 | sed -n '1,30p'\n```\n\nReport all type errors. Fix critical ones before continuing.\n\n### Phase 3: Lint Check\n\nUse `sed` to limit displayed output while consuming the whole stream. This keeps a\nsuccessful linter from failing on SIGPIPE when `pipefail` is enabled.\n```bash\nset -o pipefail\n# JavaScript\u002FTypeScript\nnpm run lint 2>&1 | sed -n '1,30p'\n\n# Python\nruff check . 2>&1 | sed -n '1,30p'\n```\n\n### Phase 4: Test Suite\n```bash\nset -o pipefail\n# Run tests with coverage\nnpm run test -- --coverage 2>&1 | tail -50\n\n# Check coverage threshold\n# Target: 80% minimum\n```\n\nReport:\n- Total tests: X\n- Passed: X\n- Failed: X\n- Coverage: X%\n\n### Phase 5: Security Scan\n```bash\n# Check for secrets\ngrep -rn \"sk-\" --include=\"*.ts\" --include=\"*.js\" . 2>\u002Fdev\u002Fnull | head -10\ngrep -rn \"api_key\" --include=\"*.ts\" --include=\"*.js\" . 2>\u002Fdev\u002Fnull | head -10\n\n# Check for console.log\ngrep -rn \"console.log\" --include=\"*.ts\" --include=\"*.tsx\" src\u002F 2>\u002Fdev\u002Fnull | head -10\n```\n\n### Phase 6: Diff Review\n```bash\n# Show what changed\ngit diff --stat\ngit diff HEAD~1 --name-only\n```\n\nReview each changed file for:\n- Unintended changes\n- Missing error handling\n- Potential edge cases\n\n## Target Acceptance\n\nWhen the requested outcome requires deployment or target-environment verification,\nreport target acceptance separately from local checks. Record the environment and\ninstalled version when known, the evidence, and the next permitted check or precise\naccess dependency. Passing local checks, review, merge, or release does not establish\ntarget acceptance. Report VERIFIED or FAILED for an executed target check, with its evidence.\nDo not access production or make external changes without authorization. For\nlocal-only tasks, mark target acceptance as not applicable.\n\nFor example: local checks PASS; staging verification NOT PERFORMED (no access);\nnext step: an authorized maintainer runs the staging smoke test.\n\n## Output Format\n\nAfter running all phases, produce a verification report:\n\n```\nVERIFICATION REPORT\n==================\n\nBuild:     [PASS\u002FFAIL]\nTypes:     [PASS\u002FFAIL] (X errors)\nLint:      [PASS\u002FFAIL] (X warnings)\nTests:     [PASS\u002FFAIL] (X\u002FY passed, Z% coverage)\nSecurity:  [PASS\u002FFAIL] (X issues)\nDiff:      [X files changed]\n\nOverall:   [READY\u002FNOT READY] for PR\nTarget:    [VERIFIED\u002FFAILED\u002FNOT PERFORMED\u002FNOT APPLICABLE] (environment\u002Fversion, evidence)\nNext permitted step: [check or access dependency; none if complete\u002Fnot applicable]\n\nIssues to Fix:\n1. ...\n2. ...\n```\n\n## Continuous Mode\n\nFor long sessions, run verification every 15 minutes or after major changes:\n\n```markdown\nSet a mental checkpoint:\n- After completing each function\n- After finishing a component\n- Before moving to next task\n\nRun: \u002Fverify\n```\n\n## Integration with Hooks\n\nThis skill complements PostToolUse hooks but provides deeper verification.\nHooks catch issues immediately; this skill provides comprehensive review.\n","# Verification Loop Skill\n\nA comprehensive verification system for Claude Code sessions.\n\n## When to Use\n\nInvoke this skill:\n- After completing a feature or significant code change\n- Before creating a PR\n- When you want to ensure quality gates pass\n- After refactoring\n\n## Verification Phases\n\n### Phase 1: Build Verification\n```bash\nset -o pipefail  # report the build's exit status, not tail's\n# Check if project builds\nnpm run build 2>&1 | tail -20\n# OR\npnpm build 2>&1 | tail -20\n```\n\nIf build fails, STOP and fix before continuing.\n\n### Phase 2: Type Check\n```bash\nset -o pipefail\n# TypeScript projects\nnpx --no-install tsc --noEmit 2>&1 | sed -n '1,30p'\n\n# Python projects\npyright . 2>&1 | sed -n '1,30p'\n```\n\nReport all type errors. Fix critical ones before continuing.\n\n### Phase 3: Lint Check\n\nUse `sed` to limit displayed output while consuming the whole stream. This keeps a\nsuccessful linter from failing on SIGPIPE when `pipefail` is enabled.\n```bash\nset -o pipefail\n# JavaScript\u002FTypeScript\nnpm run lint 2>&1 | sed -n '1,30p'\n\n# Python\nruff check . 2>&1 | sed -n '1,30p'\n```\n\n### Phase 4: Test Suite\n```bash\nset -o pipefail\n# Run tests with coverage\nnpm run test -- --coverage 2>&1 | tail -50\n\n# Check coverage threshold\n# Target: 80% minimum\n```\n\nReport:\n- Total tests: X\n- Passed: X\n- Failed: X\n- Coverage: X%\n\n### Phase 5: Security Scan\n```bash\n# Check for secrets\ngrep -rn \"sk-\" --include=\"*.ts\" --include=\"*.js\" . 2>\u002Fdev\u002Fnull | head -10\ngrep -rn \"api_key\" --include=\"*.ts\" --include=\"*.js\" . 2>\u002Fdev\u002Fnull | head -10\n\n# Check for console.log\ngrep -rn \"console.log\" --include=\"*.ts\" --include=\"*.tsx\" src\u002F 2>\u002Fdev\u002Fnull | head -10\n```\n\n### Phase 6: Diff Review\n```bash\n# Show what changed\ngit diff --stat\ngit diff HEAD~1 --name-only\n```\n\nReview each changed file for:\n- Unintended changes\n- Missing error handling\n- Potential edge cases\n\n## Target Acceptance\n\nWhen the requested outcome requires deployment or target-environment verification,\nreport target acceptance separately from local checks. Record the environment and\ninstalled version when known, the evidence, and the next permitted check or precise\naccess dependency. Passing local checks, review, merge, or release does not establish\ntarget acceptance. Report VERIFIED or FAILED for an executed target check, with its evidence.\nDo not access production or make external changes without authorization. For\nlocal-only tasks, mark target acceptance as not applicable.\n\nFor example: local checks PASS; staging verification NOT PERFORMED (no access);\nnext step: an authorized maintainer runs the staging smoke test.\n\n## Output Format\n\nAfter running all phases, produce a verification report:\n\n```\nVERIFICATION REPORT\n==================\n\nBuild:     [PASS\u002FFAIL]\nTypes:     [PASS\u002FFAIL] (X errors)\nLint:      [PASS\u002FFAIL] (X warnings)\nTests:     [PASS\u002FFAIL] (X\u002FY passed, Z% coverage)\nSecurity:  [PASS\u002FFAIL] (X issues)\nDiff:      [X files changed]\n\nOverall:   [READY\u002FNOT READY] for PR\nTarget:    [VERIFIED\u002FFAILED\u002FNOT PERFORMED\u002FNOT APPLICABLE] (environment\u002Fversion, evidence)\nNext permitted step: [check or access dependency; none if complete\u002Fnot applicable]\n\nIssues to Fix:\n1. ...\n2. ...\n```\n\n## Continuous Mode\n\nFor long sessions, run verification every 15 minutes or after major changes:\n\n```markdown\nSet a mental checkpoint:\n- After completing each function\n- After finishing a component\n- Before moving to next task\n\nRun: \u002Fverify\n```\n\n## Integration with Hooks\n\nThis skill complements PostToolUse hooks but provides deeper verification.\nHooks catch issues immediately; this skill provides comprehensive review.\n",{"name":5,"license":15,"metadata":57,"description":7},{"origin":58},"ECC","main","7092b664627bf326748a6fcbf27fee6a34c4da1d","skills\u002Fstorage\u002Faffaan-m_ECC\u002Fverification-loop",0,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills","https:\u002F\u002Fgithub.com\u002Fmdnaimul22","AI Agents Workflows Automation | Specializing in Python, FastAPI, MCP Agents & Custom ERP.","2026-11-11 21:16:57",{"source":8,"skillName":5,"commands":68,"prompt":78,"zipAvailable":79},[69,72,75],{"tool":70,"command":71},"npx","npx skills add mdnaimul22\u002Fhuman-skills --skill verification-loop",{"tool":73,"command":74},"bunx","bunx skills add mdnaimul22\u002Fhuman-skills --skill verification-loop",{"tool":76,"command":77},"pnpm","pnpm dlx skills add mdnaimul22\u002Fhuman-skills --skill verification-loop","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fverification-loop\u002FSKILL.md",true,[],[82,90,98,105,112,119],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":89},"01M767791C1KRP2ZRW2Z73VZ5Q","system-lifecycle-designer","Universal architectural methodology for designing granular, atomic, and sub-atomic lifecycles and end-to-end workflows for single functionality integrations across any domain (daemons, batch jobs, request transactions, resource pools). Provides patterns for deterministic identity, pre-commit validation, differential reconciliation, sticky leasing, state machines, transactional persistence, and closed-loop feedback.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fmy_skills\u002Fsystem-lifecycle-designer\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":97},"01M748ABPN5F1FANHH6HKZQMXT","style-sampling","Make a new episode in a proven video style - Collage Explainer, Finance Explainer, Animated Science Explainer, 3D Brand Explainer, 3D True Crime - on the person's topic. Use for \"an episode of\", \"in the style of\", \"sample this style\", 「用这个风格做一集」. One video to copy is reverse-any-video.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Fstyle-sampling\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":97},"01M748A59V04PKW4HA0XQ81FGP","reverse-any-video","Rebuild any video file as an editable HyperFrames project - motion graphics, talking heads, live action or AI-generated footage - checked against the original frame by frame. Use to reverse, recreate, remake, replicate or copy a video, or 「复刻这个视频」「照着这个视频做一个」.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Freverse-any-video\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":97},"01M7487T50P55CSXMWXZ0G9KRG","typescript-patterns","TypeScript patterns for strict, type-safe, maintainable code in modern TypeScript and JavaScript applications. Covers strict compiler configuration, type design, narrowing, discriminated unions, generics, async and error handling, module boundaries, dependency hygiene, and type-level testing. Use when writing or reviewing TypeScript or JavaScript code.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftypescript-patterns\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":97},"01M7487ERZRGPC5NJ75077Y238","test-collaboration","Inventory and govern a project's test assets. Connect requirements, business rules, risks, bugs, and cross-boundary contracts to stable TEST-IDs and executable evidence in the repository's existing test registry or TESTS.md. Use for test inventory, test gap analysis, unit\u002Fintegration\u002Fcontract\u002FE2E\u002Fsmoke classification, bug-to-test regression protection, consumer\u002Fprovider contract testing, test-necessity review, and pre-delivery evidence review.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftest-collaboration\u002FSKILL.md",[],[],{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":97},"01M748721J3GKR2WS6K0QWFC35","story-lifecycle","Manage a file-based epic → story → sprint development loop without requiring an external project management tool. Creates and tracks epics, breaks them into user stories, assigns them to sprints, and drives implementation story by story. Use when starting a new feature initiative or when the team has no Jira\u002FLinear\u002FTaiga but needs structured delivery tracking.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fstory-lifecycle\u002FSKILL.md",[],[]]