Florian BRUNIAUX

Test a web application using branch changes, selected pages, or the whole app as scope. Choose among three testing levels, document issues with evidence, fix them in separate commits, and verify results in a release-readiness report.

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

• Checking changed pages before opening a pull request
• Running a quick check for major bugs before committing
• Reviewing a release candidate for visual and functional issues

Learn programming concepts through a short definition, a minimal code example, and a practical use case. Explanations adapt to experience level, highlight common mistakes, and suggest related topics and a small practice exercise.

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

• Learning React hooks from small examples
• Understanding how async/await works
• Exploring SQL joins in depth

Remove a specific Git worktree, a separate working directory for a branch, after checking uncommitted work and merge status. Clean up branches and stale references, protect important branches, and provide reminders for related database cleanup.

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

• Remove a worktree after finishing a task
• Check for unmerged or uncommitted work before removal
• Remove a worktree while keeping its branch

Analyze security logs through four agent roles that parse events, detect anomalies, classify risk, and write an incident report. Use nginx, authentication, or system logs to review suspicious activity and receive a risk summary with recommended actions.

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

• Investigate suspicious access in nginx logs
• Analyze anomalies in authentication logs
• Classify risks found in security logs

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

Create a reusable command with explicit preconditions, numbered actions, checks after each step, and error handling. This template provides a structure to customize so Claude verifies the required context before starting a defined workflow.

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

• Turning a recurring task into a reusable command
• Defining checks for files, permissions, and configuration before work
• Adding validation after each workflow step

Analyze code, database queries, or systems for performance problems involving speed, memory, and frontend file size. Get prioritized recommendations with code examples, expected impact, implementation effort, risks, and a roadmap for improvements.

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

• Investigate a slow function or module
• Review memory usage and possible leaks
• Find inefficient database queries

Build an MCP integration skill using a template that reads server-specific reference notes before calling tools. The Sentry example gathers unresolved errors, groups them by likely root cause, and produces a report with investigation suggestions.

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

• Design a skill that integrates with an MCP server
• Document server-specific query pitfalls
• Group Sentry errors by likely root cause

Check background type checks, tests, and builds in a Git worktree, a separate working directory. Read verification logs to see results, failure counts, and errors, with suggested next actions while development continues.

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

• Checking background verification while continuing development
• Reviewing type errors and failed test names
• Distinguishing running checks from checks that have not run

Investigate bugs by tracing symptoms through code and recent changes, reproducing failures, and testing a specific cause before fixing it. Produce a focused correction, a regression test to catch recurrence, and an evidence-based debugging report.

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

• Investigate errors that keep returning after fixes
• Trace a regression through recent changes
• Analyze failures that occur only in certain environments

Prepare a branch for a pull request by running local tests, checking types for Node projects, pushing commits, and showing the CI pipeline link. Failed checks stop the workflow before the push.

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

• Running tests before opening a pull request
• Checking Node types before pushing commits
• Getting the CI link after a push

Turn CHANGELOG.md entries into French and English drafts for LinkedIn, Twitter/X, newsletters, and Slack. Select a release or week, highlight changes that matter to users, and optionally save the resulting announcements.

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

• Prepare social announcements after a release
• Summarize a week of updates
• Draft newsletters in French and English

Assess your Claude Code knowledge through multiple-choice questions with immediate feedback. Choose a quick check or a comprehensive assessment to identify gaps and receive a prioritized learning path, with practice projects included in the comprehensive mode.

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

• Checking your current Claude Code knowledge
• Choosing which topics to learn next
• Planning team training around knowledge gaps

Research new security advisories for coding agents and MCP, the protocol connecting agents to tools. Update AgentSec Triage records with source evidence and regression tests, then validate generated artifacts and synchronize the approved feed with dependent guides and pages.

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

• Refreshing threat records from recent security advisories
• Checking affected versions and fixes against primary sources
• Testing detector behavior for accepted threat records

Evaluate Claude Code agents, skills, and commands with weighted quality criteria. Get scores, readiness grades, template comparisons, and practical improvement suggestions in Markdown or JSON reports to guide reviews before release.

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

• Review skills before release
• Compare agent definitions with reference templates
• Quickly check critical quality criteria

Push the current Git branch and get a link to its GitLab CI or GitHub Actions runs. The workflow checks for uncommitted changes and blocks direct pushes to main, master, and production before proceeding.

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

• Pushing a committed feature branch
• Finding the GitLab CI tracking link after a push
• Finding GitHub Actions runs for the current branch

Monitor a live application after deployment and compare it with a saved baseline, a record of its earlier state. Check page responses, loading times, and new errors, flag persistent changes, and produce a per-page health report.

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

• Recording a healthy baseline before deployment
• Monitoring production immediately after deployment
• Checking key pages for slower responses or failures

Troubleshoot Claude Code problems by comparing reported symptoms with configuration scans and a troubleshooting guide. It asks follow-up questions when needed and proposes targeted fixes for permission prompts, tool connections, hooks, installation errors, and performance issues.

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

• Investigating repeated permission prompts
• Diagnosing MCP server connection failures
• Checking why settings or hooks are ignored

Analyze files or modules for duplicated code, excessive complexity, and violations of SOLID, five software design principles. Get prioritized refactoring suggestions with affected locations, risks, estimated effort, and testing needs to guide code improvements.

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

• Reviewing responsibilities in oversized files and classes
• Finding duplicated code and deeply nested logic
• Prioritizing refactoring by impact, risk, and effort

Read staged Git changes and suggest a message in Conventional Commits format, a structured way to describe changes. Include a concise subject and relevant details, then request confirmation before creating the commit.

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

• Draft a message for staged changes
• Use a consistent commit message format
• Document the purpose of a change

Organize open pull requests by size, automated check results, inactivity, and overlapping files. Review selected changes in depth, prepare comments for approval, and optionally create separate local working directories for hands-on review.

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

• Prioritize a backlog of open pull requests
• Find overlapping changes and failing automated checks
• Draft and approve review comments before posting

Trace how AI tooling developed in a Git repository by identifying configuration file origins, monthly commit activity, major changes, and relevant releases. Produce a Markdown report that explains adoption phases and turning points using Git evidence.

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

• Finding when AI configuration files were first introduced
• Reviewing monthly activity around AI tooling changes
• Tracing major integrations and workflow changes

Sort open GitHub issues by category, risk, inactivity, and possible duplication. Examine selected reports in detail, identify missing information, and prepare comments, labels, or closures for user approval before taking action.

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

• Sort accumulated bug reports and feature requests
• Check possible duplicates against open and closed issues
• Review inactive issues for follow-up or closure

Audit Claude Code and Codex hooks, actions triggered by agent events. Check commands, trigger conditions, blocking behavior, and timeouts to identify why hooks fail to run, fail to block actions, or delay the agent.

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

• Validate hook settings before committing
• Investigate hooks that never run
• Check policy hooks that fail to block actions