Inki Pitfalls Check

Audit a documentation file against the known-pitfalls list: common mistakes, outdated patterns, deprecated APIs.

strapi Updated

File contents

/inki-pitfalls-check: known pitfalls audit

Step 1: Read the target file

$ARGUMENTS is a relative path.

Logging: unless --no-log is passed, write this skill's report to the run log per ../inki-references/logging.md (--log-dir <path> and --short-log are also accepted). When invoked as part of an orchestrator (e.g. /inki-review), write into that run's existing directory instead of creating a new one.

Step 2: Load the known-pitfalls catalog

Read ../inki-references/prompts/integrity-known-pitfalls.md. This file is a reference catalog of documented hallucination patterns (organized by category, with tables mapping the wrong pattern to the correct one and a short context note). For each entry, check whether the target file matches the hallucinated pattern.

Step 3: Report

Target: <path>
Pitfalls found:
- <pitfall name>: <line or section reference>: <suggested fix>

strapi/documentation commit 7287a99f27

Frequently asked questions

npx get-skill add strapi/inki-pitfalls-check