Updates Claude Code CLI release tracking within the Claude Code Ultimate Guide, following its documented workflows. It can also handle an explicitly requested guide version bump and report changes, verification results, and unresolved checks.
Carry out a validated development plan in an isolated Git worktree, a separate working directory. Coordinate parallel implementation, run quality checks, update documentation, and take the changes through pull request creation, merging, execution metrics, and cleanup.
Fetch official documentation from Anthropic and save local snapshots through an MCP tool. Initialize both baseline and current copies, then report the section count and storage path so later refreshes can be compared against the baseline.
Check Claude Code configuration against a supplied threat database. Review installed skills, MCP servers that connect external tools, hooks, permissions, and exposed credentials, then receive findings grouped by severity with prioritized actions.
Coordinate threat research and updates in AgentSec, then synchronize validated results to the guide and landing page. Check compatibility data and the searchable catalogue, and report the status of each repository separately.
Suggests running verbose shell commands through RTK, a tool that condenses command output, and executes them after confirmation. It helps reduce the text an AI agent processes when reviewing Git history, tests, builds, and files.
Develop a confirmed talk angle and title into a five-act script with speaker notes and timing. Receive a slide-by-slide specification and a completed prompt to paste into Kimi for presentation generation.
Check release readiness by reviewing tests, type checks, linting, builds, security findings, documentation, and environment settings. Get a report separating deployment blockers from warnings, plus action items and checks for post-deployment health and rollback preparation.
Compare a saved baseline of Anthropic documentation with the current local snapshot, showing added, removed, and modified sections, line changes, and unchanged counts without making a network request.
Validate an implementation plan before execution through structural checks and specialist agent reviews. Check dependencies, files, tests, and architectural decisions, then update the plan to resolve findings, requesting human decisions when existing guidance is insufficient.
Turn articles, transcripts, or notes into a structured talk summary. Identify whether the material centers on practical experience or ideas, then extract its narrative, themes, sourced metrics, and gaps to guide further preparation.
Turn talk scripts, slides, and concept notes into reference sheets with section navigation, definitions, shareable links, a glossary, and six to ten anticipated questions with short answers for live Q&A and attendee follow-up.
Review code changes for concrete defects. Use it to examine modified code when you want to check whether a change contains a bug, with the review focused on specific problems in the changes.
Turn CHANGELOG.md entries into English and French announcement drafts for LinkedIn, Twitter/X, newsletters, and Slack. Select a release or week, highlight useful changes, and optionally choose the audience, format, and language.
Turn Git commits and pull request details into release notes in three formats: a changelog section, a release PR description, and a user announcement. Group changes, explain user impact, and flag database migrations.
Turn a feature request into an implementation plan before coding. Five planning phases cover requirements, interface design, technical choices, research, and metrics, producing ordered tasks, a test plan, and records explaining major decisions.
Check a Proofpack release candidate before packaging by running tests, validating the candidate, and inspecting the package locally. Compare the source state and command results with the evidence log, then report passed, failed, or unknown checks.
Turn articles, notes, or code history into talk preparation materials, including angles, titles, scripts, slide drafts, and revision sheets. Coordinate the stages with user checkpoints, or run an individual stage again.
Audit a project and its Claude Code configuration for exposed credentials, vulnerable dependencies, malicious instructions, and hook security. Receive a scored report with evidence, severity levels, and a prioritized plan for addressing the findings.
Prepare evidence for a talk about project experience by comparing git history, release notes, and a source summary. Produce commit and contributor metrics, release analysis, and a factual timeline that flags conflicting or unverified information.
Read recent releases from CHANGELOG.md and display their version numbers, dates, and complete change sections. Choose how many entries to show, or view the full history while preserving the document’s formatting.
Create a custom Claude Code skill with a structured SKILL.md file and optional scripts, reference documents, and templates. Follow checks for metadata and usage examples, test a real task, and package the skill for distribution.
Analyze a project's code, existing automation, and connected services to suggest Routines, cloud-based Claude Code sessions triggered by schedules, API calls, or GitHub events. Receive prioritized proposals with inputs, outputs, expected value, and setup blockers.
Review a pull request for code quality, correctness, security, tests, and documentation. Receive structured findings ranked by severity, with file references, approval status, positive highlights, and questions that need clarification.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)