pikit

Recognizing context pressure before it degrades output quality.

Writing implementation plans — small testable steps, dependency ordering, upfront risk identification.

Evidence before claims, always — run verification commands and confirm output before making any completion or success claims.

Generate Architecture Decision Records — use when asked to document a decision, create an ADR, record why we chose X, or capture architectural rationale.

Generate a structured changelog from git history — use when asked to create a changelog, release notes, or summarize what changed between versions/tags/branches.

How to write pikit workflow YAML files — steps, loops, branches, interpolation.

Deep research with Analysis of Competing Hypotheses — use when asked to do deep research, deeply investigate, validate claims, or when correctness is critical and the user wants rigorous analysis with disconfirmation testing.

Generate documentation for code — use when asked to document a module, generate API docs, create a README for code, or write reference documentation.

Don't reinvent the wheel — use existing libraries, tools, and stdlib before building custom solutions. Every custom solution is maintenance burden.

Generate a codebase onboarding guide — use when asked to explain this codebase, help understand the architecture, give a tour of the repo, or onboard a new contributor.

Research workflow — use when asked to research a topic, investigate options, compare approaches, or find the best solution. For high-stakes or complex questions, use deep-research instead.

Scrape a URL to clean Markdown — use when asked to scrape, fetch, extract content from, or read a webpage and convert it to Markdown.

Persistent iteration memory — prevents Groundhog Day loops by recording what was tried, what failed, and what to try next.

Detect when an agent is looping or failing repeatedly, and trigger structured recovery — backtrack, simplify, or escalate.

Use when encountering any bug, test failure, or unexpected behavior — enforces root cause investigation before proposing fixes.

Test-driven development — write the test first, watch it fail, write minimal code to pass. Use when implementing features or fixing bugs.

Generate tests for code — use when asked to write tests, create a test suite, add test coverage, or generate unit/integration tests for a file or module.

Guide for collaborative ideation sessions — when to explore vs narrow, evaluating ideas, avoiding premature commitment.

Clean code principles — meaningful names, small functions, single responsibility, stepdown rule, flat nesting.

Executing implementation plans — work through steps methodically, verify each one, keep changes small and reviewable.

How to write new skills for pikit — SKILL.md format, frontmatter, progressive disclosure, keeping content concise.

Test writing guide — one assertion per behavior, test contracts not implementation, arrange-act-assert, mocking strategy.