9bc2dd91e2
Add a super-intensive, adversarial plan-reviewer agent that runs after the plan is drafted and BEFORE the approval gate, to catch wasteful or wrong design before any implementation effort is spent. Verdict can be REDESIGN REQUIRED; findings are sorted into Critical Gaps (block) vs Suggestions (non-blocking) so the two never get conflated at the approval gate. It must open the codebase to verify claims (files exist, "no existing impl" holds, "parallel" phases are disjoint). Conditional trigger: 4+ phases / Orchestrator / Automated / security|data-sensitive. Wired into SKILL.md, discovery-and-planning (Step 5.5), agent-spawning (spawn pattern + opus model profile + cost), and modes-and-strategies (most valuable in Automated mode, the only human gate). Review hardening also addressed: - test-writer derives assertions from acceptance criteria, not the diff, so a failing test is signal (impl bug) rather than something to "fix" to match buggy behavior - early per-phase security/data pass for sensitive phases (not only final review) - Outstanding Warnings ledger in PLAN.md so non-blocking warnings can't accumulate invisibly across phases - Automated-mode global circuit breaker (cost / agent-count cap) - new `data` domain tag carrying a migration-safety addendum Bump README Last updated date.
32 lines
1.9 KiB
Markdown
32 lines
1.9 KiB
Markdown
# Claude Code Facts
|
|
|
|
> Last updated: 2026-06-01
|
|
|
|
A collection of interesting and useful facts, tips, tools, and guides for working with Claude and Claude Code.
|
|
|
|
## Contents
|
|
|
|
### [Claude Code Tools & Extensions](claude-code-tools.md)
|
|
|
|
MCP servers, skills, and plugins that extend Claude Code — including Context7 (library docs), AST Index, and vex (fast code search with semantic embeddings).
|
|
|
|
### [Gitea Release Workflow (Minimal)](gitea-release-workflow.md)
|
|
|
|
Minimal Gitea Actions workflow: push a `v*` tag → create a Gitea release with optional `RELEASE_NOTES.md`. No builds, no artifacts — just a release entry.
|
|
|
|
### [CI/CD for Python Apps on Gitea](gitea-python-ci-cd.md)
|
|
|
|
Reusable reference for building CI pipelines, release automation, and installer packaging for Python apps on Gitea — covering lint/test workflows, cross-compiled Windows builds (embedded Python + NSIS), Linux tarballs, Docker images, and Gitea REST API release management.
|
|
|
|
### [Windows Code Signing for Open-Source Projects](windows-code-signing.md)
|
|
|
|
Review of code signing options for Windows executables — Azure Trusted Signing ($9.99/mo, immediate SmartScreen trust), SignPath.io (free but GitHub-only), SSL.com, Certum, and self-signed. Includes CI/CD integration examples for Gitea Actions.
|
|
|
|
### [Gitea Act Runner — Worker Capacity (TrueNAS)](gitea-runner.md)
|
|
|
|
How to configure parallel job capacity for Gitea Act Runner on TrueNAS. Covers the `CONFIG_FILE` env var requirement, custom `config.yaml` mount, and capacity tuning.
|
|
|
|
### [Code Search: vex vs ast-index — Benchmark Notes](code-search-vex-vs-ast-index.md)
|
|
|
|
Point-in-time benchmark of `vex` and `ast-index` on a real mixed-language repo — indexing footprint, query latency, precision findings, and when to fall back from one to the other. Refreshed for `vex 1.9.1` / `ast-index 3.41.0`, with a summary of what flipped since the previous snapshot.
|