activity-plan-2026

Deep-dive analysis of an open-source repository. Clones the repo, explores architecture/patterns/internals, and produces up to 30 structured Markdown files in analysis/<repo-name>/. Use when analyzing a GitHub repo for learnings, comparison, or adoption roadmap.

Review code changes for quality, security, and correctness. Use this before merging PRs, after significant refactors, or when reviewing agent output.

Review and optimize LLM API costs in the orchestrator. Analyze model routing, budget tracking, prompt caching, and retry logic for cost efficiency.

Deploy services using Docker/OrbStack. Use this to build and deploy containers, run health checks, and manage deployments.

Review production code and update all documentation under docs/ to match the current codebase state.

Build and manage Docker containers via OrbStack. Use this to build images, run containers, check service health, and manage docker-compose services.

End-to-end feature development — implement, iterate with user feedback, test, SOLID review, document, commit & push. Use when building a new feature or making a significant code change that needs quality assurance.

Fetch GitHub starred repos, analyze one with LLM, and propose improvements via PR

Run linting and formatting checks via Docker/OrbStack. Use this before commits to ensure code quality, fix style issues, and enforce project standards.

Read bookmarks from .claude/bookmarks.json, fetch each URL, analyze content, and propose orchestrator improvements.

Search GitHub for new Claude Code skills, agents, patterns and create a PR with findings. Use this for weekly pattern discovery runs or when you want to find new AI engineering patterns.

Analyze the codebase to find untested code, generate unit and integration tests, then run them. Use this to improve test coverage or bootstrap tests for new/changed code.

Run the project test suite via Docker/OrbStack. Use this after code changes to verify correctness, run specific test files, or check coverage.

Run comprehensive pre-PR verification (tests, lint, format, docs sync, security scan, diff review). Use before creating PRs or after significant changes.

Search the internet to find solutions, documentation, tutorials, and best practices when you don't know how to do something. Use this when facing unfamiliar APIs, libraries, errors, or techniques that require up-to-date knowledge beyond the training cutoff.

Develop, build, and preview the project documentation website. Use this for docs updates, site builds, and local preview.

Full ship pipeline — run tests, update docs, CI safety checks, commit, and push in one go.