[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-83926":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":10,"languages":10,"totalLinesOfCode":10,"stars":11,"forks":12,"watchers":13,"openIssues":14,"contributorsCount":14,"subscribersCount":14,"size":14,"stars1d":15,"stars7d":16,"stars30d":16,"stars90d":14,"forks30d":14,"starsTrendScore":17,"compositeScore":18,"rankGlobal":10,"rankLanguage":10,"license":19,"archived":20,"fork":20,"defaultBranch":21,"hasWiki":22,"hasPages":20,"topics":23,"createdAt":10,"pushedAt":10,"updatedAt":33,"readmeContent":34,"aiSummary":10,"trendingCount":14,"starSnapshotCount":14,"syncStatus":35,"lastSyncTime":36,"discoverSource":37},83926,"guard-skills","amElnagdy\u002Fguard-skills","amElnagdy","Guard skills for coding agents, quality gates that catch AI-generated failure modes in code, tests, and docs","https:\u002F\u002Fskills.sh\u002FamElnagdy\u002Fguard-skills",null,570,63,4,0,21,129,171,99.42,"MIT License",false,"master",true,[24,25,26,27,28,29,30,31,32],"agent-skills","ai","claude","claude-code","code-review","codex","skills-sh","woocommerce","wordpress","2026-06-12 04:01:42","# guard-skills\n\n[![skills.sh](https:\u002F\u002Fskills.sh\u002Fb\u002FamElnagdy\u002Fguard-skills)](https:\u002F\u002Fskills.sh\u002FamElnagdy\u002Fguard-skills)\n\nFocused **guard skills** for coding agents: second-pass quality gates that catch the systematic failure modes of AI-generated code, tests, and docs before they ship.\n\nBest use: let your agent do the work, then invoke the relevant guard on the diff before you present, commit, or merge it. These skills can guide writing when you explicitly ask for that, but they are strongest as reactive review passes.\n\n## Install\n\nBrowse the package first:\n\n```bash\nnpx skills add amElnagdy\u002Fguard-skills --list\n```\n\nInstall the package:\n\n```bash\nnpx skills add amElnagdy\u002Fguard-skills\n```\n\nOr install one guard:\n\n```bash\nnpx skills add amElnagdy\u002Fguard-skills --skill clean-code-guard\nnpx skills add amElnagdy\u002Fguard-skills --skill test-guard\nnpx skills add amElnagdy\u002Fguard-skills --skill docs-guard\nnpx skills add amElnagdy\u002Fguard-skills --skill wp-guard\nnpx skills add amElnagdy\u002Fguard-skills --skill woo-guard\n```\n\nInstall for a specific agent:\n\n```bash\nnpx skills add amElnagdy\u002Fguard-skills --skill clean-code-guard --agent codex\nnpx skills add amElnagdy\u002Fguard-skills --skill test-guard --agent claude-code\nnpx skills add amElnagdy\u002Fguard-skills --skill '*' --agent cursor\n```\n\nInstall globally:\n\n```bash\nnpx skills add amElnagdy\u002Fguard-skills --global\n```\n\nWorks with Claude Code, Codex, Cursor, OpenCode, and other supported agents via the [Skills CLI](https:\u002F\u002Fgithub.com\u002Fvercel-labs\u002Fskills).\n\n## How to use them\n\nRun a guard after your agent produces work:\n\n```text\nUse $clean-code-guard on the diff you just produced.\nUse $test-guard on the tests you just wrote.\nUse $docs-guard on this README update before we ship it.\nUse $wp-guard on this WordPress plugin change.\nUse $woo-guard on this WooCommerce checkout change.\n```\n\nUse a guard up front only when you want that constraint active while writing:\n\n```text\nUse $wp-guard while implementing this REST endpoint, then self-check before delivery.\n```\n\n## Which guard to run\n\n| Guard | Use after the agent changed | Catches | Pair with |\n| --- | --- | --- | --- |\n| `clean-code-guard` | Production code in any language | LLM code smells, over-abstraction, broad error swallowing, bad names, SOLID\u002FDRY\u002FKISS\u002FYAGNI violations | Platform-specific guards |\n| `test-guard` | Test code | Mock abuse, duplicate tests, implementation-detail assertions, tests that catch nothing | `clean-code-guard` when test helpers contain real logic |\n| `docs-guard` | READMEs, docstrings, API docs, changelogs, tutorials | Hallucinated symbols, broken samples, docs-vs-code drift, unverifiable claims | Any guard whose behavior is documented |\n| `wp-guard` | WordPress plugin, theme, block, REST, AJAX, shortcode, query, or WP-CLI code | Escaping, sanitization, nonces, capabilities, prepared queries, i18n, query\u002Fcaching mistakes | `clean-code-guard`; `woo-guard` when Woo APIs appear |\n| `woo-guard` | WooCommerce extension, checkout, order, product, gateway, shipping, or HPOS code | Direct order meta, HPOS breakage, missing compatibility declarations, checkout bypasses, money errors | `wp-guard` for the WordPress layer |\n\n## The skills\n\n### clean-code-guard\n\nApplies Clean Code, SOLID, DRY\u002FKISS\u002FYAGNI to generated or changed code in any language, plus an AI-specific layer most rule packs miss: catch-all error swallowing, hardcoded \"success\" returns, hallucinated APIs, premature abstraction, comment pollution, and copy-from-similar bugs.\n\nWhy the AI layer matters: the skill references published research on duplication growth, package hallucination, and agents declaring success despite failed tests.\n\n**You'll feel it when:** your agent refactors without silently changing behavior, asks before changing a contract, justifies what it deliberately left out, and stops wrapping everything in `try\u002Fcatch -> return ok`.\n\n### test-guard\n\nA quality gate for generated or changed test code in any language: pytest, PHPUnit\u002FPest, Jest\u002FVitest, Go tests, WordPress\u002FWooCommerce tests, and more. Nine universal rules catch AI test bloat: mock only at system boundaries, never mock your own state objects, parametrize instead of copy-pasting, delete tests that catch nothing, and treat production regression tests as sacred.\n\nFramework specifics live in progressive-disclosure references the agent loads only when relevant, including a dedicated reference for LLM applications.\n\n**You'll feel it when:** a generated test file with `MagicMock()` state, duplicated test bodies, and log-message assertions comes back as \"do not merge\" with rule-by-rule fixes.\n\n### docs-guard\n\nA documentation accuracy gate for READMEs, API references, docstrings, PHPDoc\u002FJSDoc, changelogs, and tutorials. Its core move: treat documentation as a list of claims and verify every one against the codebase.\n\n**You'll feel it when:** a generated README stops referencing functions that do not exist, `@param` tags match the real signature, samples run on a clean machine, and \"blazingly fast\" leaves the building.\n\n### wp-guard\n\nA WordPress shipping guard for generated or changed plugins, themes, blocks, REST endpoints, AJAX handlers, shortcodes, WP-CLI commands, and queries. It enforces the layer generic clean-code guidance misses: escaping and sanitization, nonce plus capability checks, prepared database queries, core APIs before custom plumbing, translation-ready strings, and query\u002Fcaching discipline.\n\n**You'll feel it when:** a generated plugin stops echoing raw request data, a writing REST route gets a real permission callback, every string ships translation-ready, and a million-row site does not get handed `posts_per_page => -1`.\n\n### woo-guard\n\nA WooCommerce shipping guard for generated or changed extensions, payment and shipping integrations, checkout customizations, and order\u002Fproduct logic. It sits on top of `wp-guard` and enforces what is WooCommerce-specific: HPOS-safe order access, CRUD over direct meta, truthful feature-compatibility declarations, server-side checkout validation, money-handling discipline, and hooks over template overrides.\n\n**You'll feel it when:** order code survives HPOS, stock updates stop racing, checkout rules hold without JavaScript, and `'$' . $amount` never reaches a store that sells in dirhams.\n\n## How this differs\n\nThis is not a full process framework and not a broad platform catalog. Repos like [WordPress\u002Fagent-skills](https:\u002F\u002Fgithub.com\u002FWordPress\u002Fagent-skills) teach agents how to build across the WordPress ecosystem. `guard-skills` is narrower: it gives agents review gates to run after they have produced work, so common AI failure modes get caught before the work reaches your repo.\n\n## Repository shape\n\nEach skill is a folder with a `SKILL.md` entrypoint, lightweight agent metadata, and progressive-disclosure references:\n\n```text\nskills\u002F\n├── clean-code-guard\u002F\n│   ├── SKILL.md\n│   ├── agents\u002Fopenai.yaml\n│   └── references\u002F\n├── docs-guard\u002F\n│   ├── SKILL.md\n│   ├── agents\u002Fopenai.yaml\n│   └── references\u002F\n├── test-guard\u002F\n│   ├── SKILL.md\n│   ├── agents\u002Fopenai.yaml\n│   └── references\u002F\n├── woo-guard\u002F\n│   ├── SKILL.md\n│   ├── agents\u002Fopenai.yaml\n│   └── references\u002F\n└── wp-guard\u002F\n    ├── SKILL.md\n    ├── agents\u002Fopenai.yaml\n    └── references\u002F\n```\n\nThe `SKILL.md` stays small so it loads cheaply; deeper guidance loads only when the task needs it.\n\n## Trust and validation\n\nThis package is intentionally inspectable:\n\n- Skill content is Markdown plus lightweight `agents\u002Fopenai.yaml` metadata.\n- There are no executable scripts, network calls, MCP server dependencies, or credentials.\n- External source URLs live in each skill's `references\u002Fsources.md`.\n\nMaintainer checks before publishing:\n\n```bash\nnpx skills add . --list --full-depth\n```\n\nWith SkillSpector installed:\n\n```bash\nfor skill in skills\u002F*; do\n  skillspector scan \"$skill\" --no-llm\ndone\n```\n\nWhen authoring with a local skill-creator validator, each skill is also checked with `quick_validate.py` before release.\n\n## License\n\nMIT — see [LICENSE](LICENSE).\n",2,"2026-06-11 04:11:50","CREATED_QUERY"]