Easy agent skills that have proven useful in fixing bugs

What are agent skills? They're files that determine how an agent should behave and what tooling and workflows they should use. I think some are useful for now, but they will eventually be consumed by the models themselves and be integrated to the harnesses (some already have been). Project spesific workflows will provide value for a good while, since they are not generic.

I've used VSC and Kiro professionally in agentic engineering and Cursor & herdr on my hobby projects. This article focuses on relatively simple bugs, and isn't well suited for more complex items.

Kalle Tolonen
16.11.2026

How to use the stock agents/skills in Kiro

Kiro comes with some stock options, I haven't yet tested all of these, but Bug Fix, Plan and Default are good enough. All of them are really chatty, so using skills or steering is better than the output token maximixing default behavior.

Kiro agent panel selection

The bug fix flow does consume a fair amount of tokens, but it does get to a good enough solution even with auto-model on the router. In my experience Cursor's auto routing is superior to Kiro. To quantify my experience level with Cursor vs. Kiro, I've used Cursor for many hobby project of varying complexity (simple monoliths and serverless apps with automated etl-processes) and Kiro on a fairly complex AWS project professionally.

Custom skills & Hooks

You can use these quite simply by copying & pasting to your tool of choice and tell the genie to wire it up.

Signal path debugging - in Kiro's format. Just drop this into:

.kiro/agents/signal-path.md
---
name: signal-path
description: Lean bidirectional data/signal path debugger. Starts from symptom and finds the first break.
model: auto
tools: ["read", "write", "shell", "grep_search", "file_search", "list_directory"]
excludedTools: ["knowledge", "web", "subagent"]
welcomeMessage: Path debugger ready. Give the symptom and where you see it.
---

You debug data/signal paths. Find the first place a value becomes wrong, missing, or transformed incorrectly.

## Method
Default: start at the symptom (usually the sink/UI) and walk upstream until the data is still correct. The break is between the last good point and the first bad point.

Only go source → sink when the user starts from a known injection point.

At each step ask only: “Is the expected data present and correct here?”

Stop at the first divergence. Confirm with the smallest evidence. State root cause + exact location + minimal fix. Do not explore further unless asked.

## Token rules
- Prefer search over reading whole files.
- Read only the needed function/block.
- Replies stay short: findings first, then 1–3 concrete next actions or a patch.
- Autopilot: smallest safe change that restores the path, then verify.

## Output
**Symptom:** …
**Path:** Sink ← … ← [last good] ← [break] ← …
**Break:** file:line / function
**Evidence:** short
**Cause:** one sentence
**Fix:** minimal

Then you can use the skill via the UI panel with:

 /signal-path "symptoms go here".
Custom skill in Kiro

Some others I've started to use are from https://github.com/mattpocock/skills. Pocock has also said that there are useful workflows (calling skills in order), here are some that you may find useful. These aren't Kiro native, but can be used with it. Just ask the genie to wire them up, if you don't want to deal with the expected structure.

Pocock-lite

Kiro-hook for renaming sessions based on user input

Save this to .kiro/hooks/rename-session-by-ticket.json

{
  "version": "v1",
  "hooks": [
    {
      "name": "Rename session by ticket",
      "trigger": "UserPromptSubmit",
      "action": {
        "type": "agent",
        "prompt": "FIRST MESSAGE ONLY: Act on this rule only if the current user message is the very first message of the conversation (there are no prior assistant turns). If there is any earlier exchange in this conversation, do nothing and skip entirely.\n\nWhen it is the first message, set the session title:\n1. Look for a Jira ticket reference in the user's message matching the pattern XXX-<digits> (e.g. XXX-1234), case-insensitive. Normalize it to uppercase.\n2. If no ticket is found in the message and a Jira MCP tool is available, you may resolve the ticket from Jira context. If you still cannot determine a ticket, do nothing — do not guess or invent a ticket number.\n3. If the user's message contains the word \"review\" (case-insensitive), append \"-review\" to the title.\n4. Call update_session_information with title set to the ticket number, plus the \"-review\" suffix when applicable. Example: \"XXX-1234\" or \"XXX-1234-review\".\n\nDo this silently as a side task; do not mention it in your response unless the user asks."
      }
    }
  ]
}

The end result is that with Pococks' tdd-skill and my little hook we can one shot quite many bugs by saying:

/tdd <link to Jira goes here>

The automatic renaming makes the sessions easily searchable and a good reference point for later questions by peers and customers.

After the dev, you should run a separate review session on a separate agent, do fixes and preferably automate the loop.


Comments

No published comments yet.


Add a Comment

Your comment is held for review before it appears publicly.

Tick the box, then click Submit right away (Google expires the check after about two minutes).