#726 by GitHub stars
amElnagdy/guard-skills
Guard skills for coding agents, quality gates that catch AI-generated failure modes in code, tests, and docs
History
Review weekly changes to SKILL.md before updating. Dates mark the weeks in which we observed each version; checks apply to the recorded commits.
View weekly changes
skills/clean-code-guard/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
ffa26036b7b5 → ffa26036b7b5
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → ffa26036b7b5
No earlier version was observed for comparison.
skills/docs-guard/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
ffa26036b7b5 → ffa26036b7b5
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → ffa26036b7b5
No earlier version was observed for comparison.
skills/test-guard/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
ffa26036b7b5 → ffa26036b7b5
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → ffa26036b7b5
No earlier version was observed for comparison.
skills/woo-guard/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
ffa26036b7b5 → ffa26036b7b5
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → ffa26036b7b5
No earlier version was observed for comparison.
skills/wp-guard/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
ffa26036b7b5 → ffa26036b7b5
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → ffa26036b7b5
No earlier version was observed for comparison.
Heat
4.8- Star growth, last 7 daysAhead of 79% of tracked repositories
- Star growth, last 24 hoursAhead of 71% of tracked repositories
- Rank movement, last 7 daysAhead of 26% of tracked repositories
- Commits, last 30 daysAhead of 0% of tracked repositories
- Accounts asking about it through MCP, last 7 daysNot available
- Hot votes this weekAhead of 0% of tracked repositories
Heat never changes the order by stars, and sponsorship never touches it. How heat works
Stars over time
Individual skills in this repository
- clean-code-guard
skills/clean-code-guard - docs-guard
skills/docs-guard - test-guard
skills/test-guard - woo-guard
skills/woo-guard - wp-guard
skills/wp-guard
How it works
clean-code-guard
When your agent uses it
Review generated or changed production code before it ships, using Clean Code, SOLID, DRY, KISS, YAGNI, and LLM-specific failure-mode checks in any programming language. Best used reactively after an agent writes, edits, refactors, or fixes code, before presenting, committing, or merging the result. Use when the user asks "review this PR", "is this safe to merge?", "make this cleaner", "audit this code", "refactor this", "fix this bug", or after a coding agent produced implementation code. Can also guide writing when explicitly invoked before a risky edit. Invoke it on your own initiative the moment you finish writing, editing, or refactoring non-trivial production code, before presenting or committing — don't wait to be asked. DO NOT USE for factual/conceptual questions, CI/tooling config, git workflow, running/debugging tests, pure architecture discussion, prose writing, data analysis, or test-code review (use test-guard).
What it loads into context
Frontmatter
211 tokensAlways available to the agent
SKILL.md
3,921 tokensWhen the skill is activated
Reference documents
14,148 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Compatibility
- How to use this skill
- Examples
- Success criteria
- Why this skill exists
- Always-applied imperatives
- Self-check before delivery
- When the user pushes back on a rule
- Troubleshooting
- What this skill does not do
Files
SKILL.mdcore17,438 bytesSKILL.mdcore17,438 bytesSKILL.mdcore17,438 bytesSKILL.mdcore17,438 bytesSKILL.mdcore17,438 bytesagents/openai.yamlasset232 bytesreferences/ai-failure-modes.mddoc16,079 bytesreferences/comments-and-formatting.mddoc5,203 bytesreferences/dry-kiss-yagni.mddoc8,819 bytesreferences/naming-and-functions.mddoc6,494 bytesreferences/review-checklist.mddoc9,159 bytesreferences/solid.mddoc10,279 bytesreferences/sources.mddoc3,250 bytes
Read SKILL.md
# clean-code-guard
You are reviewing generated or changed code before it ships. Apply the rules below as a guard pass after the first implementation pass — and once this skill is active, keep applying it to every later code change in the same session, re-running the self-check before delivery after each edit rather than reverting to unguarded output because the skill loaded earlier. If the user explicitly invokes this skill before writing code, use the same rules while writing and still run the self-check before delivery.
## Compatibility
This is a portable instruction skill. It requires no MCP server, network access,
API key, shell command, local executable, or bundled script. It can be used in
any runtime that supports `SKILL.md` plus directly linked [references/](references/)
files; `agents/openai.yaml` is lightweight display metadata.
This skill does not replace project linters, formatters, type checkers, or test
runners. Use the project's own tools for mechanical verification; use this skill
for the judgement layer around code quality and review.View the complete source on GitHubdocs-guard
When your agent uses it
Review generated or changed documentation before it ships — READMEs, API references, docstrings, PHPDoc/JSDoc, changelogs, tutorials, and doc sites. Best used reactively after an agent writes or edits docs, after code changes documented behavior, or before publishing docs. Use when the user says 'review the docs', 'is this documentation accurate', 'update the docs', 'write a README', 'document this API', 'add a docstring', or 'add a changelog entry'. Core job: verify every referenced function, flag, endpoint, config key, and code sample against the source; catch docs-vs-code drift; strip filler and unverifiable claims. DO NOT USE for production code review (use clean-code-guard), test review (use test-guard), marketing copy or blog posts, prose style editing of non-technical writing, or documentation site theming.
What it loads into context
Frontmatter
191 tokensAlways available to the agent
SKILL.md
1,779 tokensWhen the skill is activated
Reference documents
2,846 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- How to use this skill
- Adapt to the project first
- The Rules
- Self-check before delivery
- Reporting format (review mode)
- Severity guide
- References
- What this skill does not do
Files
SKILL.mdcore8,333 bytesSKILL.mdcore8,333 bytesSKILL.mdcore8,333 bytesSKILL.mdcore8,333 bytesSKILL.mdcore8,333 bytesagents/openai.yamlasset254 bytesreferences/code-samples.mddoc2,895 bytesreferences/docstrings.mddoc2,771 bytesreferences/review-checklist.mddoc2,142 bytesreferences/sources.mddoc1,572 bytesreferences/verification.mddoc3,032 bytes
Read SKILL.md
# Docs Guard
You are reviewing generated or changed documentation before it ships. Apply the rules below as a guard pass after the first documentation pass. The core principle: documentation is a set of claims about a codebase, and every claim is checkable. Your job is to check them.
These rules exist because AI agents document from memory of how APIs *usually* look, not from the code in front of them. Published research: half of AI answers to programming questions contain incorrect information, and models produce valid invocations for infrequent APIs barely a third of the time — yet the prose sounds authoritative either way. Readers cannot tell verified docs from hallucinated docs. You can, because you have the source.
## How to use this skill
**Guard-pass mode** (recommended): after documentation or docstrings have been generated or edited, verify every claim against the source and run the self-check before delivery.
**Live mode** (explicit): when the user invokes this skill before writing docs, verify before you write — read the actual implementation, then document what it does. Run the self-check before delivery.
**Review mode** (the user asks you to review, audit, or fact-check docs): walk [references/review-checklist.md](references/review-checklist.md) against the target docs and produce a findings report with file:line evidence. Do not rewrite in review mode unless asked.
View the complete source on GitHubtest-guard
When your agent uses it
Review generated or changed test code against universal testing rules before it ships. Best used reactively after an agent writes, edits, generates, or refactors tests, before presenting, committing, or merging them. Use for pytest (test_*.py, *_test.py), PHPUnit/Pest (*Test.php), Jest/Vitest (*.test.ts, *.spec.js), Go (*_test.go), files under tests/, __tests__/, or spec/, and review requests like 'write tests for X', 'add tests', 'test this', 'review these tests', or PR diffs containing tests. Can also guide test writing when explicitly invoked before the work. This skill is the quality gate that prevents AI-generated test bloat. DO NOT USE for production or implementation code review (use clean-code-guard), CI or test-runner configuration, running or debugging tests, or general architecture discussion.
What it loads into context
Frontmatter
187 tokensAlways available to the agent
SKILL.md
1,848 tokensWhen the skill is activated
Reference documents
2,299 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- When this skill activates
- Adapt to the project first
- What to do
- The Nine Rules
- Reporting format
- Severity guide
- References
- What this skill does NOT do
Files
SKILL.mdcore8,561 bytesagents/openai.yamlasset225 bytesreferences/jest.mddoc2,125 bytesreferences/llm-app-testing.mddoc2,146 bytesreferences/phpunit.mddoc2,993 bytesreferences/pytest.mddoc2,563 bytes
Read SKILL.md
# Test Guard
You are reviewing generated or changed test code before it ships. Enforce the rules below after the first test-writing pass and before the tests are presented, committed, or merged. Be a sharp reviewer, not a pedantic one: flag what wastes maintenance effort or hides real bugs, ignore cosmetic preferences.
These rules exist because coding agents over-generate tests. The common failure modes: mock-heavy unit tests that assert implementation details, near-duplicate test bodies that differ by one value, and tests that re-verify the framework instead of the project's logic. Each looks productive in a diff and costs maintenance forever.
## When this skill activates
- A coding agent has just written new test functions or test files, in any language
- You are editing existing tests
- You are reviewing a diff that contains test changes
- The user asks you to write, add, or review tests
## Adapt to the project firstView the complete source on GitHubwoo-guard
When your agent uses it
Review generated or changed WooCommerce code — extensions, payment and shipping integrations, checkout customizations, and order/product logic — before it ships. Best used reactively after an agent writes, edits, or reviews code touching WooCommerce APIs: wc_get_order, wc_get_orders, wc_get_product, WC() cart or session, woocommerce_* hooks, Store API endpoints, payment gateways, order or product meta, HPOS, subscriptions, or bookings. Use on 'review this Woo plugin', 'is this HPOS compatible', or after tasks like 'write a WooCommerce extension', 'add a checkout field', 'hook into the order flow', or 'update stock'. Enforces HPOS-safe order access, CRUD over direct meta, feature-compatibility declarations, server-side checkout validation, money-handling discipline, and hooks over template overrides. DO NOT USE for WordPress code without WooCommerce APIs (use wp-guard), generic code review (use clean-code-guard), test review (use test-guard), or store configuration and admin-screen questions.
What it loads into context
Frontmatter
221 tokensAlways available to the agent
SKILL.md
1,911 tokensWhen the skill is activated
Reference documents
2,492 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- How to use this skill
- Adapt to the project first
- The Rules
- Self-check before delivery
- Reporting format (review mode)
- Severity guide
- References
- What this skill does not do
Files
SKILL.mdcore8,688 bytesagents/openai.yamlasset250 bytesreferences/checkout-and-money.mddoc3,538 bytesreferences/hpos-and-crud.mddoc3,931 bytesreferences/review-checklist.mddoc2,437 bytesreferences/sources.mddoc925 bytes
Read SKILL.md
# Woo Guard
You are reviewing generated or changed WooCommerce code before it ships. Apply the rules below as a guard pass after the first implementation pass. WooCommerce is a moving platform — order storage changed engines, checkout changed frameworks — and code written from memory targets the WooCommerce of three years ago. With money on the line, "works on my demo store" is not a standard.
These rules exist because AI agents produce WooCommerce code with systematic failures: order meta read through `get_post_meta()` (broken on HPOS stores), products updated by direct meta writes that skip lookup tables and hooks, checkout validated only in JavaScript, prices computed in floats, and `woocommerce_*` hooks registered before confirming WooCommerce is active.
## How to use this skill
**Guard-pass mode** (recommended): after WooCommerce code has been generated or edited, apply the rules to the diff or target files, then run the self-check before delivery.
**Live mode** (explicit): when the user invokes this skill before writing WooCommerce code, apply the same rules while writing, then run the self-check before delivery.
**Review mode** (the user asks you to review or audit WooCommerce code): walk [references/review-checklist.md](references/review-checklist.md) and produce a structured findings report. Do not edit code in review mode unless asked.
View the complete source on GitHubwp-guard
When your agent uses it
Review generated or changed WordPress code — plugins, themes, and blocks — before it ships. Best used reactively after an agent writes, edits, or reviews code touching WordPress APIs: add_action/add_filter, shortcodes, meta boxes, AJAX handlers, REST routes, WP_Query or $wpdb, widgets, or WP-CLI commands. Use on 'review this plugin', 'is this safe to ship', 'make this translatable', 'speed up this query', or after tasks like 'write a plugin' or 'add an endpoint/shortcode/meta box'. Enforces escaping and sanitization, nonces plus capability checks, prepared database queries, core-API-first development, translation-ready strings, and query/caching discipline. DO NOT USE for WooCommerce-specific order, product, or checkout logic (use woo-guard), non-WordPress PHP, generic code quality review (use clean-code-guard), test code review (use test-guard), server or hosting configuration, or conceptual WordPress questions.
What it loads into context
Frontmatter
214 tokensAlways available to the agent
SKILL.md
2,237 tokensWhen the skill is activated
Reference documents
4,425 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- How to use this skill
- Adapt to the project first
- The Rules
- Self-check before delivery
- Reporting format (review mode)
- Severity guide
- References
- What this skill does not do
Files
SKILL.mdcore9,796 bytesSKILL.mdcore9,796 bytesSKILL.mdcore9,796 bytesagents/openai.yamlasset235 bytesreferences/i18n.mddoc4,024 bytesreferences/performance.mddoc4,022 bytesreferences/review-checklist.mddoc3,064 bytesreferences/security.mddoc4,938 bytesreferences/sources.mddoc1,909 bytes
Read SKILL.md
# WP Guard
You are reviewing generated or changed WordPress code before it ships. Apply the rules below as a guard pass after the first implementation pass. Be a sharp reviewer, not a pedantic one: flag what creates vulnerabilities, breaks translations, or melts servers — ignore cosmetic preferences WPCS tooling already handles.
These rules exist because AI agents produce WordPress code with systematic failures: raw `echo` of request data, AJAX handlers with neither nonce nor capability check, SQL built by string interpolation, English hardcoded into user-facing strings, `posts_per_page => -1` on sites with a million posts, and hand-rolled replacements for APIs core already ships. Each one looks fine in a demo and fails in production.
## How to use this skill
**Guard-pass mode** (recommended): after WordPress code has been generated or edited, apply the rules to the diff or target files, then run the self-check before delivery. Fix violations before showing the user.
**Live mode** (explicit): when the user invokes this skill before writing WordPress code, apply the same rules while writing, then run the self-check before delivery.
**Review mode** (the user asks you to review, audit, or rate WordPress code): walk [references/review-checklist.md](references/review-checklist.md) against the target files and produce a structured findings report. Do not edit code in review mode unless asked.
View the complete source on GitHubSkills included
- clean-code-guard
- docs-guard
- test-guard
- woo-guard
- wp-guard
Repository facts
- License
- MIT
- Created
- Jun 6, 2026
- Last pushed
- Jul 4, 2026
- Forks
- 143
- Open issues
- 1
- Project activity
- Slowing
Rank over the last 12 weeks
Now #726 · best #503 · down 134 in 30 days
- #715 on Nov 1
- #716 on Nov 2
- #719 on Nov 3
- #722 from Nov 4 to Nov 5
- #723 on Nov 6
- #726 since Nov 7
67 earlier periods
- #494 on Aug 2
- #495 on Aug 8
- #497 on Aug 9
- #514 on Aug 11
- #513 on Aug 12
- #517 from Aug 13 to Aug 14
- #498 on Aug 15
- #507 on Aug 16
- #510 on Aug 17
- #519 on Aug 19
- #516 on Aug 20
- #521 on Aug 21
- #503 on Aug 22
- #524 on Aug 23
- #528 on Aug 24
- #537 on Aug 25
- #527 on Aug 26
- #538 on Aug 27
- #537 on Aug 28
- #520 on Aug 29
- #511 on Aug 30
- #537 on Aug 31
- #543 on Sep 1
- #535 on Sep 2
- #541 on Sep 3
- #524 on Sep 4
- #520 on Sep 5
- #535 on Sep 6
- #541 on Sep 7
- #556 on Sep 8
- #541 on Sep 9
- #549 on Sep 10
- #536 on Sep 12
- #559 on Sep 14
- #546 on Sep 15
- #558 on Sep 16
- #555 on Sep 17
- #559 on Sep 18
- #546 on Sep 19
- #574 on Sep 22
- #575 on Sep 23
- #556 on Sep 24
- #579 on Sep 28
- #600 on Sep 29
- #571 on Oct 1
- #580 on Oct 2
- #558 on Oct 3
- #571 on Oct 4
- #592 on Oct 6
- #608 on Oct 9
- #596 on Oct 11
- #612 on Oct 12
- #615 on Oct 13
- #627 on Oct 14
- #623 on Oct 15
- #629 on Oct 16
- #607 on Oct 18
- #636 on Oct 19
- #646 on Oct 20
- #652 on Oct 21
- #634 from Oct 22 to Oct 23
- #620 on Oct 24
- #697 on Oct 25
- #704 on Oct 28
- #705 on Oct 29
- #708 on Oct 30
- #712 on Oct 31
Before you install
Instructions onlyAutomated signals, not a guarantee
Checked Nov 3, 2026
Not fully analyzed: some files were too long, unreadable or missing. This never lowers the level.
Show 10 notes
skills/clean-code-guard/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/clean-code-guard/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/clean-code-guard/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/clean-code-guard/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/docs-guard/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/docs-guard/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/docs-guard/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/docs-guard/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/wp-guard/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/wp-guard/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzed
- No broad tool permissions
- No dangerous shell commands
- 56 network referencesin 4 files: clean-code-guard/references/sources.md:14 wp-guard/references/sources.md:12 docs-guard/references/sources.md:12 and 1 more
- No hidden or obfuscated text
- No instruction overrides
- No executable scripts
- 2 references to secretsin 2 files: docs-guard/references/code-samples.md:31 wp-guard/SKILL.md:47
- No requests to vote in Hot
Show all 58 signals by file
skills/clean-code-guard/references/sources.md
- Network accessline 14
- **Clean Code sample chapters**: https://ptgmedia.pearsoncmg.com/images/9780132350884/samplepages/9780132350884.pdf - Network accessline 15
- **Command Query Separation, Fowler**: https://martinfowler.com/bliki/CommandQuerySeparation.html - Network accessline 16
- **Refactoring, Fowler**: https://martinfowler.com/books/refactoring.html - Network accessline 17
- **YAGNI, Fowler**: https://martinfowler.com/bliki/Yagni.html - Network accessline 18
- **DRY, The Pragmatic Programmer excerpt**: https://media.pragprog.com/titles/tpp20/dry.pdf - Network accessline 19
- **The Wrong Abstraction, Sandi Metz**: https://sandimetz.com/blog/2016/1/20/the-wrong-abstraction - Network accessline 20
- **SOLID principles, Uncle Bob archive**: http://butunclebob.com/ArticleS.UncleBob.PrinciplesOfOod - Network accessline 21
- **SRP, Uncle Bob**: https://blog.cleancoder.com/uncle-bob/2014/05/08/SingleReponsibilityPrinciple.html - Network accessline 22
- **OCP, Uncle Bob**: https://blog.cleancoder.com/uncle-bob/2014/05/12/TheOpenClosedPrinciple.html - Network accessline 23
- **LSP, Liskov/Wing paper mirror**: https://www.labri.fr/perso/clement/enseignements/ao/LSP.pdf - Network accessline 24
- **DIP, Object Mentor archive**: https://web.archive.org/web/20150924054349/http://www.objectmentor.com/resources/articles/Principles_and_Patterns.pdf - Network accessline 28
- **GitClear AI code quality 2025**: https://www.gitclear.com/ai_assistant_code_quality_2025_research - Network accessline 29
- **Package Hallucinations, Spracklen et al., USENIX Security 2025**: https://www.usenix.org/system/files/conference/usenixsecurity25/sec25cycle1-prepub-742-spracklen.pdf - Network accessline 30
- **AI-Generated Code Considered Harmful**: https://arxiv.org/abs/2409.19182 - Network accessline 31
- **A Deep Dive Into LLM Code Generation Mistakes**: https://arxiv.org/abs/2411.01414 - Network accessline 32
- **Patterns for Reducing Friction in AI-Assisted Development, Fowler**: https://martinfowler.com/articles/reduce-friction-ai/ - Network accessline 33
- **Claude Code issue 6984, mock data generation bias**: https://github.com/anthropics/claude-code/issues/6984 - Network accessline 34
- **Karpathy on exception suppression**: https://x.com/karpathy/status/1976077806443569355 - Network accessline 35
- **Code Needs Comments**: https://arxiv.org/html/2402.13013v1 - Network accessline 36
- **Evaluating the Code Quality of AI-Assisted Code Generation Tools (Copilot, CodeWhisperer, ChatGPT)**: https://arxiv.org/abs/2304.10778 - Network accessline 37
- **On Mitigating Code LLM Hallucinations with API Documentation**: https://arxiv.org/abs/2407.09726 - Network accessline 38
- **LLM Hallucinations in Practical Code Generation (taxonomy)**: https://arxiv.org/abs/2409.20550 - Network accessline 39
- **When Names Disappear: Revealing What LLMs Actually Understand About Code**: https://arxiv.org/abs/2510.03178 - Network accessline 40
- **Neural Variable Name Repair**: https://arxiv.org/abs/2512.01141 - Network accessline 41
- **Vibe Coding in Practice**: https://arxiv.org/abs/2512.11922 - Network accessline 45
- **McCabe NIST 235r**: https://www.mccabe.com/pdf/mccabe-nist235r.pdf - Network accessline 46
- **Cognitive Complexity, SonarSource**: https://www.sonarsource.com/docs/CognitiveComplexity.pdf - Network accessline 47
- **ReSharper cyclomatic complexity threshold guidance**: https://github.com/JetBrains/resharper-cyclomatic-complexity/blob/master/docs/ThresholdGuidance.md
skills/docs-guard/references/code-samples.md
- Access to secretsline 31
[Credential-related source omitted]
skills/docs-guard/references/sources.md
- Network accessline 12
- Kabir et al., "Is Stack Overflow Obsolete? An Empirical Study of the Characteristics of ChatGPT Answers to Stack Overflow Questions", CHI 2024 — 52% of answers contained incorrect information; evaluators missed AI errors 39% of the time: - Network accessline 13
- CloudAPIBench, "On Mitigating Code LLM Hallucinations with API Documentation" (AWS, 2024) — 38.58% valid invocations for low-frequency APIs: https://arxiv.org/abs/2407.09726 - Network accessline 14
- De-Hallucinator (2024) — LLMs routinely invent non-existent APIs; project-API grounding fixed 63.2% of hallucination-caused failures: https://arxiv.org/abs/2401.01701 - Network accessline 15
- Spracklen et al., "We Have a Package for You!" (USENIX Security 2025) — package hallucination averages 19.6% across 16 models: https://www.usenix.org/conference/usenixsecurity25/presentation/spracklen - Network accessline 19
- Diátaxis — the four documentation modes (tutorial, how-to, reference, explanation): https://diataxis.fr/ - Network accessline 20
- Write the Docs — style guide collection: https://www.writethedocs.org/guide/writing/style-guides/ - Network accessline 21
- RFC 5737 — IPv4 address blocks reserved for documentation: https://www.rfc-editor.org/rfc/rfc5737 - Network accessline 22
- Google developer documentation style guide: https://developers.google.com/style
skills/woo-guard/references/sources.md
- Network accessline 11
- HPOS (High-Performance Order Storage): https://developer.woocommerce.com/docs/features/high-performance-order-storage/ - Network accessline 12
- HPOS recipe book (compatibility patterns): https://developer.woocommerce.com/docs/features/high-performance-order-storage/recipe-book/ - Network accessline 13
- CRUD objects: https://developer.woocommerce.com/docs/category/data-management/crud-objects/ - Network accessline 14
- Store API: https://developer.woocommerce.com/docs/apis/store-api/ - Network accessline 15
- Cart and Checkout Blocks — extensibility: https://developer.woocommerce.com/docs/category/cart-and-checkout-blocks/ - Network accessline 16
- Action Scheduler: https://actionscheduler.org/ - Network accessline 17
- Payment gateway API: https://developer.woocommerce.com/docs/woocommerce-payment-gateway-api/
skills/wp-guard/SKILL.md
- Access to secretsline 47
[Credential-related source omitted]
skills/wp-guard/references/sources.md
- Network accessline 12
- Plugin Handbook — Security: https://developer.wordpress.org/plugins/security/ - Network accessline 13
- Common APIs Handbook — Sanitizing Data: https://developer.wordpress.org/apis/security/sanitizing/ - Network accessline 14
- Common APIs Handbook — Escaping Data: https://developer.wordpress.org/apis/security/escaping/ - Network accessline 15
- Nonces: https://developer.wordpress.org/apis/security/nonces/ - Network accessline 16
- WordPress Coding Standards (WPCS ruleset): https://github.com/WordPress/WordPress-Coding-Standards - Network accessline 17
- Plugin Handbook — Internationalization: https://developer.wordpress.org/plugins/internationalization/ - Network accessline 18
- wpdb::prepare() reference: https://developer.wordpress.org/reference/classes/wpdb/prepare/ - Network accessline 19
- REST API Handbook — Adding Custom Endpoints: https://developer.wordpress.org/rest-api/extending-the-rest-api/adding-custom-endpoints/ - Network accessline 20
- Options autoloading (WP 6.6+): https://make.wordpress.org/core/2024/06/18/options-api-disabling-autoload-for-large-options/ - Network accessline 21
- Script loading strategies (WP 6.3+): https://make.wordpress.org/core/2023/07/14/registering-scripts-with-async-and-defer-attributes-in-wordpress-6-3/ - Network accessline 25
- Veracode, 2025 GenAI Code Security Report — 45% of AI-generated samples contained OWASP Top 10 vulnerabilities; XSS failed in 86% of XSS-prone tasks: https://www.veracode.com/resources/analyst-reports/2025-genai-code-security-report/ - Network accessline 26
- Perry et al., "Do Users Write More Insecure Code with AI Assistants?", ACM CCS 2023: https://arxiv.org/abs/2211.03622 - Network accessline 27
- GitGuardian, State of Secrets Sprawl 2025 — 40% higher secret-leak incidence in Copilot-active repos: https://www.gitguardian.com/state-of-secrets-sprawl-report-2025
How the signals fit together
Facts from a static read of the files at the pinned commit. They describe what the code does, not why.
Some files could not be read; the facts below still hold.
No combined signals at this commit.
Works with
| Agent | Status | Evidence | Install to |
|---|---|---|---|
| Claude Code | Compatible | Standard SKILL.md skills/clean-code-guard/SKILL.md | .claude/skills/<skill-name>/ |
| Codex | Compatible | Standard SKILL.md skills/clean-code-guard/SKILL.md | .agents/skills/<skill-name>/ |
| Cursor | Compatible | Standard SKILL.md skills/clean-code-guard/SKILL.md | .cursor/skills/<skill-name>/ |
| Gemini CLI | Compatible | Standard SKILL.md skills/clean-code-guard/SKILL.md | .gemini/skills/<skill-name>/ |
| GitHub Copilot | Compatible | Standard SKILL.md skills/clean-code-guard/SKILL.md | .github/skills/<skill-name>/ |
| OpenCode | Compatible | Standard SKILL.md skills/clean-code-guard/SKILL.md | .opencode/skills/<skill-name>/ |
- Native The repository ships a manifest, folder or frontmatter field for this agent.
- Compatible A standard SKILL.md that this agent can read.
- Unknown No evidence either way.
Derived automatically from paths, manifests and frontmatter. Not tested on each agent.
Explore alternatives and comparisons
Add this badge to your README
It updates every night and links to this page.
[](https://hotskills.dev/skill/amelnagdy-guard-skills/)