Florian BRUNIAUX

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Updating threat information through AgentSec
• Synchronizing validated security feeds
• Checking new records in the searchable catalogue

Evaluate staged Git changes before committing using an LLM, a language model acting as a reviewer. Receive correctness, completeness, and safety scores, plus issues by severity, to decide whether to fix, commit, or stop.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Evaluate significant changes before committing
• Review changes in unfamiliar code
• Check changes to security-sensitive code

Audit French and English whitepapers and recap cards for outdated versions, missing language counterparts, and metadata problems. Receive document scores, an overall health report, and prioritized update suggestions, with optional proposed patches.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find whitepapers that lag behind the current guide
• Check French and English document pairs
• Identify missing or inconsistent metadata

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating a custom skill for a project
• Standardizing skill structure across a team
• Preparing a skill with scripts and templates

Diagnose command failures before attributing them to sandbox restrictions, which limit access to files and networks. Check execution methods, command matching, and network behavior, then prepare an evidence-based report for the person responsible for settings.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating permission errors such as EPERM
• Separating network restrictions from hostname failures
• Checking why an excluded command still fails

Diagnose failures in an application or while it is running. Use it to investigate an application problem or a runtime error, meaning an error that occurs during execution.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating an error during execution
• Diagnosing an application failure
• Asking an agent to examine a running application's problem

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Planning a feature that touches several files
• Resolving unclear requirements before implementation
• Recording architecture and interface decisions

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing project security before production deployment
• Checking credentials against Git history
• Inspecting Claude Code settings and security hooks

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing changes after editing code
• Checking a bug fix for further defects
• Reviewing code changes that add a feature

Save an unfinished session as a timestamped Markdown handoff. Capture changed files, decisions and their reasons, current progress, blockers, and ordered next steps so work can resume later or continue in another Claude instance.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Saving unfinished work before ending a session
• Preserving progress before switching tasks
• Recording decisions before context compaction

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing announcements after a release
• Summarizing a week of releases
• Adapting updates for different posting channels

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing the five most recent releases
• Checking changes across ten releases
• Reading the complete release history

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding recurring maintenance tasks to automate
• Planning automated responses to GitHub events
• Identifying manual work between connected services

Turns Git commits and pull request details into release notes for CHANGELOG.md, a release pull request, and Slack. It categorizes changes, explains user impact in plain language, and flags database migrations that need attention.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing release notes since the last release
• Summarizing changes across a specified version range
• Drafting a release pull request body

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking readiness before a production deployment
• Reviewing staging environment settings
• Adding release checks to CI/CD

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Writing a full script after confirming the talk direction
• Planning speaking time and pauses
• Preparing slide specifications for a designer

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review configuration after installing skills or MCP servers
• Find overly broad permissions and dangerous settings
• Check configuration files for exposed keys and tokens

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking a Proofpack candidate before packaging
• Comparing local verification with recorded evidence
• Finding unverified checks or uncovered changes

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prepare a changelog for a release
• Draft a release pull request description
• Explain updates to users in plain language

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Verifying development metrics for an experience report talk
• Building a timeline of releases and features
• Analyzing monthly commits and contributor activity

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing a pull request before merging
• Checking changes against the original plan
• Auditing error handling and validation of AI output

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Starting a talk from an article or notes
• Assessing source material before committing to a talk
• Organizing measurable results with their sources

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Implementing a validated development plan
• Running dependent tasks in parallel stages
• Preparing failing tests before implementation

Take an existing pull request through automated check results, user approval, merging, deployment verification, and a production health check. Report outcomes and timings, with investigation or rollback options when deployment problems appear.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Merge a pull request after CI and test checks
• Verify deployment after a merge
• Check production status, response time, and page content