pychivalry

Author Architecture Decision Records (ADRs) for the ck3-language-support (pychivalry) VS Code extension. Trigger this skill when asked to create, draft, or write a new ADR, or when a technical decision needs to be formally documented.

After-action report skill for producing structured, succinct summaries of completed missions. Use after any multi-step task, implementation, review, or operational mission to give the user a clear picture of what happened, what changed, and what remains. Covers mission debrief, change inventory, officer contributions, decision log, and follow-up items.

Systematic methodology for converting unknowns to knowns through structured investigation. Use when performing root-cause analysis, debugging complex issues, conducting codebase audits, or any investigative task requiring evidence-based findings. Provides confidence-level classification (Proven/Observed/Inferred), gap tracking templates, investigation techniques (log tracing, component isolation, binary search debugging, POC execution, upstream tracing), and a structured handoff protocol for multi-agent workflows.

Author Architectural Decision documents for the docs/architecture/decisions/ directory. Trigger this skill when asked to create, draft, or write a new architectural decision, or when a technology choice, design pattern, or infrastructure strategy needs formal documentation.

Common software architecture patterns, ADR templates, and anti-pattern detection. Supports architectural review, design decisions, and system documentation.

Produce ASCII flow charts using Unicode box-drawing characters in a specific visual style with double-line title banners, single-line phase boxes, numbered steps, nested sub-boxes, decision branches, and a key/legend footer. Use when the user asks for a flowchart, diagram, flow diagram, order of operations, process chart, decision tree, state machine visualization, pipeline diagram, or any visual representation of a workflow, pipeline, module, or multi-phase process. Also use when asked to "chart this," "diagram this," "map out the flow," or "show me how X works visually."

Structured code review criteria for pre-implementation plan review (Critic) and post-implementation security/quality review. Covers security, performance, maintainability, and correctness with severity ratings.

Code review checklist, severity definitions, and document templates. Load when performing code reviews or defining review criteria.

Enforce type safety and contract adherence for APIs spanning multiple repositories. Use when implementing or consuming cross-repo API endpoints, syncing contract definitions between repos, proposing contract changes, or validating that request/response shapes match a shared contract. Covers contract discovery, standard directory structure (api-contract/ or .contracts/), implementation guidelines for both backend and frontend, contract change proposals, CI sync workflows, and type validation testing.

Unified document lifecycle management. Defines terminal statuses, unified numbering via .next-id, close procedures, and orphan detection. Load at session start.

Core software engineering principles (SOLID, DRY, YAGNI, KISS) with detection patterns and refactoring guidance. Load when reviewing code quality, planning architecture, or identifying technical debt.

Git commit workflow for creating clean, atomic, well-messaged commits. Use when committing code changes, checkpointing work, or preparing commits for review. Covers conventional commit format, pre-commit safety checks, co-author attribution, and recovery from hook failures.

Unified Memory Contract for MCP Knowledge Graph integration. Defines when and how to retrieve and store structured knowledge. Load at session start - memory is core to agent reasoning, not optional.

Orchestrate a structured periodic review of project health across six areas — code health, security posture, documentation currency, architecture alignment, test coverage, and dependency freshness. Use when asked to run a health check, periodic review, audit, or project assessment.

Run a comprehensive health check on the project including linting, tests, security scanning, dependency audits, and code quality metrics. Use this when asked to assess project health, run diagnostics, perform a checkup, or validate that the codebase is in good shape before a release or deployment.

Version management, release verification, and deployment procedures for software releases. Includes semver guidance, version consistency checks, and platform-specific constraints.

Security vulnerability detection patterns including OWASP Top 10, language-specific vulnerabilities, and remediation guidance. Load when reviewing code for security issues, conducting audits, or implementing authentication/authorization.

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

TDD workflow and test strategy patterns including test pyramid, coverage strategies, mocking approaches, and anti-patterns. Load when writing tests, designing test strategies, or reviewing test coverage.