[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DPHHQMAFX911PD6Y27HWWK":3,"skill-same:01M7DPHHQMAFX911PD6Y27HWWK":51},{"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":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M7DPHHQMAFX911PD6Y27HWWK","repo-maintainer",null,"Audit and repair repository hygiene across artifacts, dependencies, CI, docs, Git state, and code-quality signals. Use for repository maintenance, cleanup, health checks, or pre-release hardening.","Hazek-dc\u002FPresensiGuru_FaceNet_EMAR","Hazek-dc","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F75208960?v=4","01M7DEQV5B4YGS86A81DYH81DR","Hazek","01M7DEQV5XP4TM0C6NTHXCXCHR",1,"MIT","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frepo-maintainer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: repo-maintainer\ndescription: \"Audit and repair repository hygiene across artifacts, dependencies, CI, docs, Git state, and code-quality signals. Use for repository maintenance, cleanup, health checks, or pre-release hardening.\"\nrisk: critical\nsource: https:\u002F\u002Fgithub.com\u002FWolfe-Jam\u002Ffaf-skills\u002Ftree\u002Fmain\u002Fskills\u002Frepo-maintainer\nsource_repo: Wolfe-Jam\u002Ffaf-skills\nsource_type: community\ndate_added: 2026-07-01\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002FWolfe-Jam\u002Ffaf-skills\u002Fblob\u002Fmain\u002FLICENSE\n---\n\n# Repository Maintainer\n\n## Overview\n\nAudit repository health, apply authorized repairs narrowly, and finish through the repository's own protected workflow.\n\n## When to Use\n\nUse when the user asks to maintain, clean, audit, harden, or prepare a repository for release. Use a more specific security, database, deployment, or release skill when that is the dominant task.\n\n## Repository Policy Gate\n\nBefore mutation:\n\n1. Read root and nested `AGENTS.md`, contributor guidance, maintainer docs, and release instructions.\n2. Inspect the current branch, worktree, staged files, remotes, default branch, and effective branch protection.\n3. Discover repository-native validation, synchronization, merge, and release commands.\n4. Preserve unrelated user work and generated outputs that are not in scope.\n\nIf the repository names a mandatory maintainer skill or guarded command, delegate to it instead of inventing a parallel branch, merge, sync, or release path. In `agentic-awesome-skills`, use `antigravity-maintainer-batch-release` and `npm run merge:batch`; `main` is pull-request-only.\n\nThe routine protected checks for `agentic-awesome-skills` are `pr-policy`, `pr-evidence`, `source-validation`, and `artifact-preview`. The supported AAS Core preview uses targeted unit tests plus one packed Linux\u002FNode LTS smoke path and Workbench review. Do not resurrect the retired certified-v1 baseline, benchmark, tuning-gold, transaction-fault, race, or frozen OS\u002Fruntime matrix as routine merge gates.\n\n## Usage\n\n### 1. Establish the baseline\n\n```bash\ngit status --short --branch\ngit diff --stat\ngit diff --cached --stat\ngit remote -v\ngit log -5 --oneline\n```\n\nRecord the repository's required runtime versions and test commands. Use a clean temporary clone or worktree when existing user changes cannot be isolated safely.\n\n### 2. Audit independent lanes\n\nRun independent read-only checks in parallel where possible.\n\n#### Artifacts and Git hygiene\n\n- untracked caches, coverage, build output, editor files, and test leftovers;\n- tracked large or binary files, accidental secrets, executable-mode drift, and ignored-file gaps;\n- stale branches, detached HEAD, existing staged changes, submodules, and symlinks;\n- generated files whose ownership belongs to CI or a canonical-sync workflow.\n\nDo not delete or rewrite history during the audit.\n\n#### Dependencies and packaging\n\n- lockfile and manifest agreement;\n- outdated, vulnerable, duplicate, unused, or end-of-life dependencies;\n- runtime imports incorrectly placed in development dependencies;\n- clean-install, package-content, and executable-entrypoint behavior.\n\nTreat audit-tool output as evidence to verify, not automatic permission to upgrade or remove packages.\n\n#### CI and release health\n\n- failing, cancelled, skipped, or stale workflow runs;\n- stale, redundant, or unjustifiably broad runtime matrices and unpinned or obsolete actions;\n- required checks, branch protection, release permissions, and secret boundaries;\n- mismatch between documented and implemented release commands.\n\n#### Documentation and repository metadata\n\n- README, changelog, version, examples, links, badges, credits, and support metadata;\n- contribution instructions and PR templates versus current CI policy;\n- generated catalog, site, or API documentation drift.\n\n#### Code-quality signals\n\n- dead code, stale implementation markers, debug logging, commented-out code, and missing tests;\n- unsafe defaults, suppressed errors, credential exposure, and environment-specific paths.\n\nFor FAF projects only, also inspect declared `.faf`, `.faf-dna`, sync, score, and MCP contracts with the project's installed FAF commands.\n\n### 3. Produce a prioritized decision set\n\nFor each finding report:\n\n- evidence and affected paths;\n- severity and user impact;\n- whether it is safe to fix now, needs approval, or belongs to another workflow;\n- exact validation that proves the repair.\n\nDeduplicate symptoms with the same root cause. Do not mix optional modernization with release blockers.\n\n### 4. Apply authorized repairs\n\nMake the smallest coherent change set. Keep source and generated-file ownership separate, update tests with behavior changes, and rerun the targeted failing check after each repair group.\n\nNever delete data, rewrite history, rotate credentials, change branch protection, or upgrade across breaking versions without explicit authorization.\n\n### 5. Validate and publish safely\n\nRun the repository's required pre-PR suite, then inspect the final diff for unrelated files and secrets. Commit on a topic branch and create a pull request when the target branch is protected.\n\nUse required checks and the repository-native merge path. A user request to “push to main” describes the desired final state; it does not bypass branch protection. For releases, use the scripted release workflow and verify external publication rather than inferring success from a local tag.\n\n## Stop Condition\n\nFinish when every in-scope finding is repaired or has one exact blocker, required validation passes, the remote integration path is verified when requested, and unrelated user work remains unchanged.\n\n## Limitations\n\n- Maintenance findings can depend on repository-specific ownership and release policy; read local instructions before acting.\n- Dependency and security scanners can produce false positives or incomplete reachability evidence.\n- This skill does not authorize destructive cleanup, branch-policy changes, direct protected-branch pushes, merges, deployments, or releases beyond the user's request.\n","# Repository Maintainer\n\n## Overview\n\nAudit repository health, apply authorized repairs narrowly, and finish through the repository's own protected workflow.\n\n## When to Use\n\nUse when the user asks to maintain, clean, audit, harden, or prepare a repository for release. Use a more specific security, database, deployment, or release skill when that is the dominant task.\n\n## Repository Policy Gate\n\nBefore mutation:\n\n1. Read root and nested `AGENTS.md`, contributor guidance, maintainer docs, and release instructions.\n2. Inspect the current branch, worktree, staged files, remotes, default branch, and effective branch protection.\n3. Discover repository-native validation, synchronization, merge, and release commands.\n4. Preserve unrelated user work and generated outputs that are not in scope.\n\nIf the repository names a mandatory maintainer skill or guarded command, delegate to it instead of inventing a parallel branch, merge, sync, or release path. In `agentic-awesome-skills`, use `antigravity-maintainer-batch-release` and `npm run merge:batch`; `main` is pull-request-only.\n\nThe routine protected checks for `agentic-awesome-skills` are `pr-policy`, `pr-evidence`, `source-validation`, and `artifact-preview`. The supported AAS Core preview uses targeted unit tests plus one packed Linux\u002FNode LTS smoke path and Workbench review. Do not resurrect the retired certified-v1 baseline, benchmark, tuning-gold, transaction-fault, race, or frozen OS\u002Fruntime matrix as routine merge gates.\n\n## Usage\n\n### 1. Establish the baseline\n\n```bash\ngit status --short --branch\ngit diff --stat\ngit diff --cached --stat\ngit remote -v\ngit log -5 --oneline\n```\n\nRecord the repository's required runtime versions and test commands. Use a clean temporary clone or worktree when existing user changes cannot be isolated safely.\n\n### 2. Audit independent lanes\n\nRun independent read-only checks in parallel where possible.\n\n#### Artifacts and Git hygiene\n\n- untracked caches, coverage, build output, editor files, and test leftovers;\n- tracked large or binary files, accidental secrets, executable-mode drift, and ignored-file gaps;\n- stale branches, detached HEAD, existing staged changes, submodules, and symlinks;\n- generated files whose ownership belongs to CI or a canonical-sync workflow.\n\nDo not delete or rewrite history during the audit.\n\n#### Dependencies and packaging\n\n- lockfile and manifest agreement;\n- outdated, vulnerable, duplicate, unused, or end-of-life dependencies;\n- runtime imports incorrectly placed in development dependencies;\n- clean-install, package-content, and executable-entrypoint behavior.\n\nTreat audit-tool output as evidence to verify, not automatic permission to upgrade or remove packages.\n\n#### CI and release health\n\n- failing, cancelled, skipped, or stale workflow runs;\n- stale, redundant, or unjustifiably broad runtime matrices and unpinned or obsolete actions;\n- required checks, branch protection, release permissions, and secret boundaries;\n- mismatch between documented and implemented release commands.\n\n#### Documentation and repository metadata\n\n- README, changelog, version, examples, links, badges, credits, and support metadata;\n- contribution instructions and PR templates versus current CI policy;\n- generated catalog, site, or API documentation drift.\n\n#### Code-quality signals\n\n- dead code, stale implementation markers, debug logging, commented-out code, and missing tests;\n- unsafe defaults, suppressed errors, credential exposure, and environment-specific paths.\n\nFor FAF projects only, also inspect declared `.faf`, `.faf-dna`, sync, score, and MCP contracts with the project's installed FAF commands.\n\n### 3. Produce a prioritized decision set\n\nFor each finding report:\n\n- evidence and affected paths;\n- severity and user impact;\n- whether it is safe to fix now, needs approval, or belongs to another workflow;\n- exact validation that proves the repair.\n\nDeduplicate symptoms with the same root cause. Do not mix optional modernization with release blockers.\n\n### 4. Apply authorized repairs\n\nMake the smallest coherent change set. Keep source and generated-file ownership separate, update tests with behavior changes, and rerun the targeted failing check after each repair group.\n\nNever delete data, rewrite history, rotate credentials, change branch protection, or upgrade across breaking versions without explicit authorization.\n\n### 5. Validate and publish safely\n\nRun the repository's required pre-PR suite, then inspect the final diff for unrelated files and secrets. Commit on a topic branch and create a pull request when the target branch is protected.\n\nUse required checks and the repository-native merge path. A user request to “push to main” describes the desired final state; it does not bypass branch protection. For releases, use the scripted release workflow and verify external publication rather than inferring success from a local tag.\n\n## Stop Condition\n\nFinish when every in-scope finding is repaired or has one exact blocker, required validation passes, the remote integration path is verified when requested, and unrelated user work remains unchanged.\n\n## Limitations\n\n- Maintenance findings can depend on repository-specific ownership and release policy; read local instructions before acting.\n- Dependency and security scanners can produce false positives or incomplete reachability evidence.\n- This skill does not authorize destructive cleanup, branch-policy changes, direct protected-branch pushes, merges, deployments, or releases beyond the user's request.\n",{"name":5,"risk":24,"source":25,"license":15,"date_added":26,"description":7,"source_repo":27,"source_type":28,"license_source":29},"critical","https:\u002F\u002Fgithub.com\u002FWolfe-Jam\u002Ffaf-skills\u002Ftree\u002Fmain\u002Fskills\u002Frepo-maintainer",1782864000000,"Wolfe-Jam\u002Ffaf-skills","community","https:\u002F\u002Fgithub.com\u002FWolfe-Jam\u002Ffaf-skills\u002Fblob\u002Fmain\u002FLICENSE","main","b1e4ffadb4f933bbbcaa03a83f8b9929171ac28b",".agents\u002Fskills\u002Frepo-maintainer",0,"https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR","https:\u002F\u002Fgithub.com\u002FHazek-dc","2026-10-22 08:36:44",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill repo-maintainer",{"tool":43,"command":44},"bunx","bunx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill repo-maintainer",{"tool":46,"command":47},"pnpm","pnpm dlx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill repo-maintainer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frepo-maintainer\u002FSKILL.md",true,[],[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7DS6GGYRZAYD33PFPS8Z2T3","testing-best-practices","Laravel test design and review. Use when selecting coverage, naming or structuring tests, choosing assertions or test data, isolating dependencies, testing HTTP or security boundaries, improving suite performance, or reviewing test value. Use framework guidance or search-docs for Pest and PHPUnit syntax.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Ftesting-best-practices\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7DS6BC3AW7HTPRHE2TTVKWM","tailwindcss-development","Always invoke when the user's message includes 'tailwind' in any form. Also invoke for: building responsive grid layouts (multi-column card grids, product grids), flex\u002Fgrid page structures (dashboards with sidebars, fixed topbars, mobile-toggle navs), styling UI components (cards, tables, navbars, pricing sections, forms, inputs, badges), adding dark mode variants, fixing spacing or typography, and Tailwind v3\u002Fv4 work. The core use case: writing or fixing Tailwind utility classes in HTML templates (Blade, JSX, Vue). Skip for backend PHP logic, database queries, API routes, JavaScript with no HTML\u002FCSS component, CSS file audits, build tool configuration, and vanilla CSS.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Ftailwindcss-development\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7DS66GE6B11MYJDVC74HXM4","laravel-best-practices","Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance issues, caching strategies, authorization and security patterns, validation, error handling, queue and job configuration, route definitions, and architectural decisions. Also use for Laravel code reviews and refactoring existing Laravel code to follow best practices. Covers any task involving Laravel backend PHP code patterns.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Flaravel-best-practices\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7DS5ZW717DMS6P1E90AQCKV","infer-conventions","Use this skill to analyze how a Laravel application is actually written and record its conventions as shared rules. Trigger when the user wants to detect, infer, document, or standardize project conventions or coding style, set up or grow `.ai\u002Frules`, resolve mixed or conflicting patterns (e.g. \"are we using Form Requests or inline validation?\"), or onboard agents and teammates to \"how we do things here\". Covers: a systematic sweep of ~49 Laravel convention dimensions (validation, models, architecture, testing, frontend, database, console), open-ended house-pattern discovery, conflict reporting, and recording rules scoped to the right paths via the Boost `record-rule` MCP tool. Only run this skill when the user explicitly asks for it; never start a sweep as part of another task. Do not use for one-off code review, enforcing formatting a linter already handles, or editing `.ai\u002Frules` files by hand.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Finfer-conventions\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7DS5W12RGCVJTFQJ1N0GB8E","inertia-react-development","Develops Inertia.js v2 React client-side applications. Activates when creating React pages, forms, or navigation; using \u003CLink>, \u003CForm>, useForm, or router; working with deferred props, prefetching, or polling; or when user mentions React with Inertia, React pages, React forms, or React navigation.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Finertia-react-development\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7DS5PVDPMPCWSK2RXPDC9BB","deploying-to-cloud","Deploys and manages Laravel applications on Laravel Cloud using the `cloud` CLI. Use when the user wants to deploy an app, ship to Cloud, create or manage applications, environments, databases, caches, object storage, queues, domains, instances, background processes, secrets, compute, scheduled tasks, or Laravel Cloud infrastructure; or check billing, usage, or spend. Triggers on deployment, shipping, Cloud management, environment setup, database provisioning, billing or usage queries, the `cloud` CLI, and Laravel Cloud deployment troubleshooting.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Fdeploying-to-cloud\u002FSKILL.md",[],[]]