Reconcile this session's code delta back into the Living Blueprint and per-folder intent layer so they stay an accurate snapshot of the codebase. Mostly descriptive (what the code now is), not rules. Pure producer — edits files only, never commits or opens a PR.
Generates ViewDefinition, StructureDefinition (must-support), and markdown intro files from a ZIB FHIR profile URL or canonical (e.g. zib-Alert). Use this when asked to create technical artifacts for Zorginformatiebouwstenen (ZIBs) in FHIR.
[BETA] Detect, review, and fix code-quality and correctness issues in an AEM as a Cloud Service
project — locally, with no external services or network calls. Use whenever a user wants to
check, review, assess, audit, scan, modernize, upgrade, or fix AEM Java, Sling Models, OSGi,
or Maven code — for example: "check my Sling Models are implemented correctly", "review my
@Inject usage", "are my Maven dependencies up to date", "scan this AEM project for issues",
"modernize my Sling Models", or "fix code-quality problems". Name the files to assess, or ask
it to scan the repo; it detects issues, plans, and — only when you ask — applies surgical
edits on a branch or in place, then verifies with mvn compile. It recognises the intent and
handles each issue type itself, reporting anything it cannot yet fix.
This skill is in beta. Verify all outputs before applying them to production projects.
Load this skill when deciding which inputs and scenarios a test should cover, not how to wire the runner: partitions, boundaries, state transitions, properties, fuzzing, failing dependencies. Trigger on "what should I test", "cover the edge cases", or a test file with only a happy path.
This skill should be used when the user reports "macstack lint fails", "prototype does not resolve", "env keys missing", "scaffold broke my files", "cross-stack reference does not work", or any macstack-dev skill errors out. Diagnoses the common failure modes of the macstack.json toolchain.
Rebase an overridden WordPress or WooCommerce template onto the version currently installed, keeping its customizations and explaining what each one is for. The override can live in a theme or child theme, in a plugin that serves its own copies of another project's templates, or in a standalone file. Diffs the override against the pristine template of the release it was copied from, replays the customizations onto the current upstream template, annotates them with begin and end markers, and bumps the @version header. Covers WooCommerce templates, parent theme templates copied into a child theme, other plugins' templates, and WordPress core. Triggers: "update this template override", "this WooCommerce template is out of date", "rebase the overridden templates", "version X is out of date, the core version is Y", "refresh the theme's woocommerce templates", "bring in the new template but keep my changes", "outdated templates in the WooCommerce status report", "which templates is this theme overriding".
Parses and processes SARIF files from static analysis tools like CodeQL, Semgrep, or other scanners. Triggers on "parse sarif", "read scan results", "aggregate findings", "deduplicate alerts", or "process sarif output". Handles filtering, deduplication, format conversion, and CI/CD integration of SARIF data. Does NOT run scans — use the Semgrep or CodeQL skills for that.
Detect and strip AI provenance marks (invisible Unicode steganography, C2PA/EXIF/XMP metadata, container metadata) from text, images and documents. Use when asked to check or clean AI watermarks in a file or pasted text.
Skill designs must be unified under a single SKILL.md and labeled as strict mandatory directives rather than suggestions to prevent context fragmentation and drift. In multi-agent environments, separating core instructions into secondary reference files (like ruleset.md) causes other agent instances to treat the guidelines as optional recommendations instead of strict system boundaries.
Pre-commit i18n check. Scans changed files for untranslated strings, missing locale keys, and locale sync issues. Fast and focused — only checks what changed. Use before committing or as a review add-on.
Add a skill to the adk plugin, create a new /adk: command, modify an existing adk skill's workflow / rules, or register a skill in the marketplace. Derives the house convention from the repo itself (AGENTS.md, SAFETY.md, existing skills) rather than memory. Writes repo files only — never publishes, never commits.
Turn any GitHub repo, local folder, PR, or markdown/Obsidian vault into an interactive architecture map with CodeFlow — a zero-build single index.html browser app (React 18 + D3.js from pinned CDNs) that runs 100% client-side with no backend and no data collection. Pick an input (public repo, private repo with a local token, local files, PR URL, markdown vault), choose a visualization mode (folder/layer/churn/blast), and read the analysis — dependency graph, blast radius, code ownership, heuristic security scanner, pattern/anti-pattern detection, A–F health score, activity heatmap, PR impact — then export JSON/Markdown/text/SVG/PDF or wire the self-updating CodeFlow Card SVG onto a README.
Python resource management with context managers, cleanup patterns, and streaming. Use when managing connections, file handles, implementing cleanup logic, or building streaming responses with accumulated state.
Use when starting any creative work - creating features, building components, adding functionality, or modifying behavior - to explore user intent, requirements and design before implementation. Triggers: "brainstorm", "design this feature", "explore approaches", "help me think through this design". Do NOT use for executing an already-approved design (use executing-plans for that) or for trivial single-file changes.
Compress, extract, list, and encrypt ZIP archives in batch. Use when archiving files, extracting packages, listing contents, encrypting backups, or batching.
Editing specs/ROADMAP.md, specs/TODO.md, or specs/TOFIX.md, or normalizing raw input (ideas, bug reports) into backlog entries. Read before touching the backlog files or recording new tasks/defects.