Skip to content
TrustedSkillsbeta
Back to all skills

File Test Bug

Official
microsoft·vlatest·testing

Automatically runs file tests to identify bugs and regressions in Microsoft software builds.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add microsoft/github-copilot-for-azure --skill file-test-bug -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

microsoft

Matched to the vendor's own GitHub organisation.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned microsoft/github-copilot-for-azure at f2526ae581.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
f2526ae581
Manifest
.github/skills/file-test-bug/SKILL.md
Scanned
1 file, 70 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill enables AI agents to execute file-based testing workflows, specifically designed to validate bug fixes or verify code changes within a repository. It streamlines the verification process by automating test runs directly against specific files or directories.

When to use it

  • You need to quickly confirm that a recent code change resolves a reported issue without manual intervention.
  • Your workflow requires automated validation of file modifications before merging pull requests.
  • You are debugging an application and want the AI to run targeted tests on specific source files.
  • You need to ensure regression stability after updating a particular module or library.

Key capabilities

  • Executes testing commands against specified files in a repository context.
  • Integrates with GitHub Copilot for Azure environments.
  • Automates the verification of bug fixes and code updates.
  • Provides immediate feedback on test results for targeted file changes.

Example prompts

  • "Run unit tests specifically on the auth-service.js file to verify my latest fix."
  • "Execute integration tests for the updated payment-gateway module in this repository."
  • "Validate that my recent changes to config.yaml do not break existing test suites."

Tips & gotchas

Ensure your repository has a defined testing framework (e.g., Jest, Mocha) configured before invoking this skill, as it relies on existing scripts. The skill is most effective when used in environments where the AI agent has read/write access to the file system and execution permissions.