Results for “bugherd”

Systematically find and fix bugs using proven debugging techniques, tracing from symptoms to root cause, implementing fixes, and preventing regression.

Investigates bugs, regressions, and crashes by dispatching four parallel read-only sub-agents, then ranks hypotheses and recommends the fastest proof or fix path.

Burn HUD

Writes Behavior-Driven Development scenarios using Gherkin syntax to create executable specifications and test behavior.

Implements Behavior-Driven Development with Cucumber, Gherkin scenarios, and step definitions.

Behavior-driven development: Discovery → Formulation → Automation. Use when the user wants to build features or fix bugs via Gherkin scenarios and the BDD lifecycle, or mentions BDD/Gherkin/Executable Specifications. Delegates test implementation to /mattpocock:tdd.

Walk every branching path and boundary condition in content, report only unhandled edge cases. Orthogonal to adversarial review - method-driven not attitude-driven. Use when you need exhaustive edge-case analysis of code, specs, or diffs.

Walk every branching path and boundary condition in content, report only unhandled edge cases. Orthogonal to adversarial review - method-driven not attitude-driven. Use when you need exhaustive edge-case analysis of code, specs, or diffs.

Initializes bug bounty hunt workspaces, logs vulnerability findings with severity and evidence, and enriches them throughout a session.

Walk every branching path and boundary condition in content, report only unhandled edge cases. Orthogonal to adversarial review - method-driven not attitude-driven. Use when you need exhaustive edge-case analysis of code, specs, or diffs.

Applies behavior-driven development principles including Gherkin scenarios and test-driven development. This skill should be used when the user asks to implement features, fix bugs, or when writing executable specifications and tests before writing production code.

Enhance bug reports with reproduction steps, environment details, and severity classification

Diagnoses and operates Kubernetes clusters: pods, deployments, ingress, HPA, PVC, StorageClass, NetworkPolicy, Secrets, Helm, ArgoCD, cert-manager. Reads before changing; mutations require confirmation and diff review.

Scaffolds new Blazor web applications with the correct render mode, project structure, and authentication setup.

BDD spec authoring — create, update, or delete .feature files following best practices

提供奉俊昊导演风格的创意建议，涵盖视觉方案、叙事建议、场景设计和执行要点，适用于剧本创作和影像设计。

Implements any user intent, requirement, story, bug fix or change request by producing clean working code artifacts that follow the project's existing architecture, patterns and conventions. Use when the user wants to build, fix, tweak, refactor, add or modify any code, component or feature.

Documents the Bugatti brand design system: a black-and-white interface with custom typefaces, no accent color, and full-bleed photography as the only visual element.

Spawns parallel reasoning branches under different cognitive frames to explore non-obvious solutions for open-ended design, architecture, naming, and fuzzy debugging problems, then scores, clusters, and deepens the most promising ideas.

Extend and upgrade Hermes Agent's context compression system — StagedArchiver, knowledge fingerprinting, /uncompress command, look-ahead triggers, and schema migration patterns.

Build and audit Kubernetes operators with tools that validate CRD design, lint reconcile loops, and score OperatorHub capability levels.

Analyzes current state and user query to answer BMad questions or recommend the next skill(s) to use. Use when user asks for help, bmad help, what to do next, or what to start with in BMad.

Use when asked to fix, build, refactor, review, verify, or release software and the work is non-trivial — including delivering a change request (issue, ticket, or request) from intake through planning, gates, implementation, review, verified PR, and authorized post-merge release. neckbeard routes the change through framing, discovery, design, implementation, review, verification, delivery, and learning — choosing the smallest *safe* intervention, proving it at the real delivery boundary, and leaving an inspectable evidence ledger. For change-request / issue-to-PR work, conditionally loads a 9-phase journey with gates, delivery packet, and lifecycle integration. Composes specialist catalog skills rather than replacing them. Not a persona, not a '10x developer' prompt, not a LOC-minimizer. The journey is not loaded for plain fixes, refactors, or reviews that lack an issue/ticket trajectory.

Analyzes current state and user query to answer BMad questions or recommend the next skill(s) to use. Use when user asks for help, bmad help, what to do next, or what to start with in BMad.

Benchmarks zero-shot in-context learning on BIG-Bench Hard multiple-choice tasks, comparing self-generated demonstrations against direct prompting and chain-of-thought baselines, and reports accuracy.

Audit Kubernetes RBAC configurations to identify overly permissive roles, wildcard permissions, dangerous bindings, service account abuse, and privilege escalation paths using kubectl, rbac-tool, KubiScan, and Kubeaudit.

Dolt-powered issue tracker for multi-session work with dependencies and persistent memory across conversation compaction. Use when work spans sessions, has blockers, or needs context recovery after compaction. Trigger with "create task", "what's ready", "track this work", "resume after compaction". Make sure to use this skill whenever managing multi-session work, tracking dependencies, or recovering context.

Restructure any response for an ADHD brain — TL;DR first, ELI16 clarity, short punchy steps, one clear next action, zero walls of text. Use this skill whenever the user says "elihadhd", "adhd mode", "tldr", "eli16", "eli5", "too long", "overwhelmed", "shorter", "just tell me what to do", "break this down", "snap it", "gauntlet", or shows signs of overwhelm (e.g. "wait what", "I'm lost", "too much"). Also use it when the user asks for the simple version, the quick version, or the punchy version of anything — explanations, plans, debugging help, docs, decisions. When in doubt about whether a response is too heavy, use this skill.

This skill should be used when working with BMAD (BMad-CORE) v6-alpha projects. BMAD is a universal human-AI collaboration platform with specialized modules for software development (BMM), agent building (BMB), creative intelligence (CIS), and project management (BMD). Use this skill to understand agent workflows, command patterns, scale-adaptive methodology, and effective utilization of the four-phase development system.

Fetch and display BBC News stories from various sections and regions via RSS feeds. Use when the user asks for BBC news, UK news headlines, world news from BBC, or news from specific BBC sections (technology, business, politics, science, health, entertainment, regional UK news, or world regions).

Diagnose and fix retention problems using the Fogg Behavior Model (B=MAP), covering motivation, ability, prompts, and tiny habits.

Documents PostHog's design system: a warm cream canvas, hand-drawn hedgehog mascots, IBM Plex Sans typography, and a single yellow-orange CTA pill, with detailed color, typography, and component specifications.

Skill: Aider-Expert (仓颉执行器)

Assess Active Directory security posture using PingCastle, BloodHound, and Purple Knight to identify misconfigurations, privilege escalation paths, and attack vectors.

Domain-Driven Design patterns. Bounded contexts, aggregates, entities, value objects, domain events, repositories, and application services. Strategic and tactical DDD for complex business domains. USE WHEN: user mentions "DDD", "Domain-Driven Design", "bounded context", "aggregate", "value object", "domain event", "ubiquitous language", "aggregate root", "domain service" DO NOT USE FOR: database schema design - use database skills; CQRS/Event Sourcing specifics - use `event-sourcing-cqrs`