AGENT SKILL

creating-debug-tests-and-iterating

Use this skill when faced with a difficult debugging task where you need to replicate some bug or behavior in order to see what is going wrong.

适用职业开发工程师
License 许可
MIT
最近更新
2026-11-14
Stars
★ 4.9k
Forks
590

01 前言 Front Matter

name
creating-debug-tests-and-iterating
description
Use this skill when faced with a difficult debugging task where you need to replicate some bug or behavior in order to see what is going wrong.

03 SKILL.md 正文

<required> CRITICAL Add the following steps to your Todo list using TodoWrite:

<system-reminder>From this point on, ignore any existing tests until you have a working example validated through a new test file.</system-reminder>

  1. Write a script that interacts with the application from the outside. The script should not call any internals. It should only interact with the external interfaces.
  2. Check to see if you require authentication. If you do, ask me for credentials. <system-reminder>Do NOT use mock mode or test harnesses. You should be testing the real thing.</system-reminder>
  3. Follow these steps in a loop until the bug is fixed:
  • Add many logs to the application. You MUST do this on every loop.
  • Run the debug script.
  • Analyze the output: read logs, identify errors, do whatever you need to.
  • Update the debug script. <system-reminder>If you get stuck: did you add logs?</system-reminder>
  1. Identify and fix the issue at hand.
  2. Clean up all background jobs, and remove extraneous logs.
  3. Make sure other tests pass. </required>

Debug Testing

To test different kinds of applications, write scripts that test the application interfaces. Your testing should be as close to 'real' as possible.

Example

Identify the application boundary to be tested and the tools you need to test it.

CLI Tool:

./path/to/cli.sh arg1 arg2
subprocess.run(["./path/to/cli.sh", "arg1", "arg2"])
exec('./path/to/cli.sh', (error, stdout, stderr) => {
  if (error) {
    console.error(`exec error: ${error}`);
    return;
  }
  console.log(`stdout: ${stdout}`);
  console.error(`stderr: ${stderr}`);
});

API:

Start the server:

cd backend && python server.py&
cd frontend && npm run dev&

Call to the server using scripting language of choice.

Do NOT get in a loop where you just keep running other tests. In this mode, you should ignore other tests entirely until it works.

Emulators for testing

Web servers or web apps: use Playwright (read .agency/plugins/nori/skills/webapp-testing/SKILL.md) TUI tools: use tmux with screen capture CLI tools: use bash

04 同仓库更多 Skills

microsoft
microsoft/FluidFramework

trigger-pipelines-for-copilot-pr

Trigger ADO pipelines for a Copilot-created PR by posting /azp run comments. Use when the user asks to trigger CI pipelines for a specific PR.

★ 4.9k
microsoft
microsoft/FluidFramework

review

Review changes relative to a prior state, such as a diff, pull request, branch, commit, or working-tree changes. Use for change-focused code review and regression analysis. Do not use to assess an existing file, API, design, implementation, or other artifact without a comparison; if the request is ambiguous, ask whether the user wants a change review and what prior state to compare against.

开发工程师代码审查后端与接口
★ 4.9k
microsoft
microsoft/FluidFramework

review-pr-local

The authority on pulling a pull request — Azure DevOps or GitHub — into an isolated local worktree so a human can review it in their editor, and on posting human-controlled review comments back to the PR (ADO via the ado PR-thread MCP tools or the Azure DevOps REST API, GitHub via the gh CLI). Auto-detects the platform and all identifiers from the PR URL; not tied to any specific repository. The AI assists an interactive human review and only ever posts comments the human explicitly requests. If you find yourself checking out a PR branch over the user's own working tree, or posting AI-authored review prose the human did not ask for, invoke this skill instead.

Skill与智能体开发
★ 4.9k
microsoft
microsoft/FluidFramework

policy-check

This skill should be used when the user asks to "run policy check", "check policy", "policy-check", or needs to validate package compliance. Provides guidance on running policy checks for specific packages or the entire repository.

★ 4.9k
microsoft
microsoft/FluidFramework

pipeline-test-triage

Triage test failures in an Azure DevOps pipeline run for Fluid Framework. Use when the user shares an ADO build/pipeline URL or build ID and wants failures analyzed, when they ask "why did this pipeline fail", "summarize the test failures", "is this test flaky or a real bug", "compare these runs", or wants bugs filed for genuine failures. Covers the Real Service End to End Tests pipeline as the worked example but applies to any FF test pipeline.

测试与质量
★ 4.9k
microsoft
microsoft/FluidFramework

fluid-release

Fluid Framework client release group — minor releases, patch releases, and post-release type test updates. Covers release prep, branching, version bumps, changelogs, release notes, and type test baselines. In autonomous mode, auto-detects state from the repo, attempts to execute, and falls back to a GitHub issue on failure. Triggers on "release", "do the release", "release status", version bump, release notes, changelog, release branch, or release engineering.

★ 4.9k