Menu
Search across all KB files in docs/kb/ for a keyword, topic, or tag. Returns matching files and relevant excerpts.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | kb-search |
| description | Search across all KB files in docs/kb/ for a keyword, topic, or tag. Returns matching files and relevant excerpts. |
| disable-model-invocation | true |
You are a knowledge base search assistant. Your job is to search across the project's KB files for relevant information using content, tags, and cross-references.
Check if the user provided a search term after the command (e.g., /kb-search authentication or /kb-search tag:security).
Determine the search mode:
tag: (e.g., tag:security), search frontmatter tags arrays..md files under docs/kb/ (excluding docs/kb/README.md).docs/kb/. Run /kb-init to set up the knowledge base." and stop.For tag search:
tags array (case-insensitive).related references for files that link to matching files.For content search:
docs/kb/api-conventions.md).tags for matches (a content search for "security" should also surface files tagged security).docs/kb/_global-learnings.md if it exists (this is the dedicated global learnings KB file).### Global Learnings inline section (older KB setups may still have this). If found, search it too.Present results grouped by source, including frontmatter metadata:
KB Search Results for: "{query}"
================================
KB Files with matches:
1. docs/kb/api-conventions.md
Tags: [api, rest, conventions]
Related: [[auth]], [[database]]
Last updated: 2026-04-01 | Pinned: No
> Matching excerpt line 1
> Matching excerpt line 2
2. docs/kb/auth/tokens.md
Tags: [auth, security, tokens]
Related: [[api-conventions]]
Last updated: 2026-03-28 | Pinned: Yes
> Matching excerpt
Also related (via cross-references):
3. docs/kb/database.md — related to matched file api-conventions.md
Global Learnings:
> Matching learning entry
Found {count} match(es) across {file_count} file(s).
If no results found:
"No matches found for '{query}' in the knowledge base. The KB currently has {file_count} file(s) with tags: {unique tags list}."
Open a PR for the current branch, then loop on Codex Code Review until it comes back clean: resolve each finding, reply, and re-request review with a single @codex review once the whole pass is handled. Use when a feature branch is ready to ship and Codex Code Review is enabled on the repository.
Scaffold the repo side of Xcode Cloud for an XcodeGen / Tuist Swift project - generate ci_scripts/ci_post_clone.sh (regen + guarded CI_BUILD_NUMBER stamping), propose a unit-test-only CI scheme, print the exact App Store Connect workflow checklist, and optionally install an opt-in .githooks/pre-push gate. Shows diffs and confirms before writing.
Review Swift 6 strict-concurrency and SwiftUI code for idiom and build-breaking issues - non-Sendable across actor boundaries, @MainActor witness vs nonisolated protocol requirements, Combine/ObservableObject usage, force-unwraps, #Predicate macro limits, the 6.3.x Binding IRGen crash, missing #if os() guards, and unsafe escape hatches. Reports file:line with the fix and the why.
Diagnose a Swift / Xcode Cloud / TestFlight failure from a pasted red build log, an ITMS App Store rejection email, or a bare error code. Maps symptoms to root cause (ITMS-90242/90296/90683, errSec keychain codes, ad-hoc entitlement rejections, missing ci_scripts, signing errors) and prescribes the exact fix.
Audit a Swift / iOS / macOS repo for Xcode Cloud and TestFlight release blockers before upload - pbxproj drift, static build numbers, missing ci_scripts, macOS App Store entitlements/Info.plist, headless-CI keychain tests, ad-hoc signing entitlement rejections, and flaky-UITest release gating. Reports PASS/WARN/FAIL with file:line and fixes.
Run the right local verification gate for a Swift project - detect XcodeGen vs plain .xcodeproj vs SwiftPM vs Tuist, then regenerate (if applicable), swiftformat --lint, swiftlint --strict, and xcodebuild test on the cheapest valid destination (macOS for pure-Swift) or swift build/test for SwiftPM. Reports each stage; --fix lets SwiftFormat rewrite.