Claude Skills by FlorianBruniaux

Transform CHANGELOG entries into social content (LinkedIn, Twitter/X, Newsletter, Slack) in FR + EN. Use after releases or weekly to generate ready-to-post content from guide updates.

Interactive skill assessment with personalized learning path generation

Add descriptive prose to bare sections in whitepapers (FR + EN) using 9 parallel agents

Audit version freshness, FR/EN parity, and metadata quality of all whitepapers and recap cards

Daily update check — official Anthropic docs diff + guide/CC releases digest

Compare official Anthropic docs baseline vs current snapshot (no network — instant)

Fetch official Anthropic Codex docs and store as local baseline snapshot

Re-fetch official Anthropic Codex docs and update current snapshot (baseline unchanged)

View recent CHANGELOG entries

Analyzes your codebase and asks 3 targeted questions to recommend the right AI-assisted development methodology stack

Check guide/landing synchronization status

Search for new online mentions of the Codex Ultimate Guide and update the tracker

Update Codex releases tracking (guide + landing + version bump)

Audit Claude Code agents, skills, and commands for quality and production readiness. Use when evaluating skill quality, checking production readiness scores, or comparing agents against best-practice templates.

Codebase health audit scoring 7 categories with progression plan

Autonomous improvement loop — scan codebase metrics, scaffold experiment files, run agent-driven iterations until metric improves

Post-deploy monitoring — watch production after a deploy and alert on regressions

Restore context after /clear by summarizing recent work and project state

Launch and navigate the ccboard TUI/Web dashboard for Claude Code. Use when monitoring token usage, tracking costs, browsing sessions, or checking MCP server status across projects.

Audit Claude Code setup for cache bugs (CC#40524) — sentinel, --resume/--continue, attribution header + ArkNill B3/B4/B5

Full CI pipeline: run local tests, type check, push branch, and return the pipeline URL. The only command you need before opening a PR.

Push current branch and return the pipeline tracking URL (GitLab or GitHub Actions)

Show current pipeline status for the active branch — GitLab CI or GitHub Actions

Run the test suite for the current repo — auto-detects Python (pytest/uv), Node (vitest/pnpm), or Rust (cargo test)

Generate a conventional commit message for staged changes

Orchestrate a 4-agent cyber defense pipeline to analyze log files for threats. Use when investigating security logs, detecting anomalies in access patterns, classifying breach severity, or generating incident reports from nginx/auth/syslog files.

Interactive troubleshooting assistant for Claude Code issues

Audit .claude/rules/ files for structural correctness, glob validity, and real-world usefulness. Resolves each paths: pattern against actual project files, then asks the user whether each rule is still relevant and useful. Can update rules in-place based on answers. Use when setting up rules for the first time, debugging rules that fire too often or never, or doing a periodic rules hygiene pass.

Audit all skills in the current project for frontmatter completeness, effort level appropriateness, allowed-tools scoping, and content quality. Produces a scored report with effort-level recommendations for each skill. Use when onboarding to a new project, reviewing skill quality before shipping, or adding effort fields to an existing skill library.

Explain code, concepts, or system behavior with adjustable depth levels

Generate comprehensive tests for specified code

Analyze AI config evolution in a git repo. Use when mapping AI adoption history, finding when configs were first introduced, charting commit velocity by month, or identifying maturity phases in a project's AI tooling.

Clean up stale git worktrees with merged branch detection and disk usage report

Safely remove a git worktree with branch cleanup and safety checks

Check status of background verification tasks running in a git worktree

Create isolated git worktrees for feature development without switching branches

Generate a structured handoff document from the current session. Captures scope, relevant files with line numbers, key discoveries, work completed, current status, next steps, and code snippets. Use before ending a session or handing work to another agent.

Load a handoff document and resume work from where a previous session left off. Parses scope, file references, completed work, and next steps, then confirms understanding before proceeding.

Update an existing handoff document with current session progress. Applies section-specific merge rules: append-only for Work Done (never deletes history), replace for Status and Next Steps, merge for Files and Discoveries. Falls back to creating a new handoff if no source file is found.

Systematic root-cause debugging — find the cause before writing any fix

Merge PR, wait for CI, verify deploy, run canary — the complete landing pipeline

Generate complete, deploy-ready landing pages from any repository. Use when creating a homepage for an open-source project, building a project website, converting a README into a marketing page, or standardizing landing pages across multiple repos.

Compare different approaches to solve the same problem

Test understanding of recently written or accepted code

Step-by-step explanation of a concept with progressive depth

Template for skills that integrate with an MCP server. Demonstrates the reference file pattern: Claude reads a domain-specific MCP cheatsheet before making any tool calls, reducing query failures caused by server-specific gotchas. Fork this skill and replace the Sentry example with your target MCP.

Analyzes your codebase and asks 3 targeted questions to recommend the right AI-assisted development methodology stack

Analyze and suggest performance improvements for code, queries, or systems

Orchestrates the complete planning pipeline: product direction (ceo-review) → architecture (eng-review) → implementation plan (start) → validation (validate) → execution (execute). Run stages individually or let the orchestrator coordinate the full flow.

Strategic product gate — challenge the brief, find the 10-star product hiding inside the request, before writing any code