Agent skill

Phpunit Testing

by AdamKyle in AdamKyle/flare

A skill your agent uses when writing, reviewing, or refactoring PHPUnit tests in this repository.

MITAuto-check passedDevelopment

Install Phpunit Testing

skills CLI
$ npx skills add AdamKyle/flare --skill phpunit-testing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install AdamKyle/flare phpunit-testing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/AdamKyle/flare.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/phpunit-testing .claude/skills/phpunit-testing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
phpunit-testing
GitHub stars
162
Token cost
~656 tokens
SKILL.md length
389 words
Files
1
Skills in repo
3
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when writing, reviewing, or refactoring PHPUnit tests in this repository.

  • Refactoring PHPUnit tests in this repository
  • SKILL.md covers Scope, Test Structure, What Not To Test and Mocking, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Tasks that involve Refactoring

What it does

Phpunit Testing is an agent skill from AdamKyle/flare. Use this skill when writing, reviewing, or refactoring PHPUnit tests in this repository.

Its SKILL.md is about 660 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Refactoring. The repository describes itself as: A Simple Browser Based Game. The licence is MIT.

When your agent uses it

  • Refactoring PHPUnit tests in this repository
  • Tasks that involve Refactoring

Example prompts

  • “/phpunit-testing”

What it can do on your machine

Read from SKILL.md and the folder at commit e22bc47. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Phpunit Testing loads about 656 tokens when it runs. Until then it costs about 26 tokens; SKILL.md has 389 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~26
When it runs · the whole SKILL.md, loaded when a task matches
~656

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from AdamKyle/flare at commit e22bc47, republished under its MIT licence (© AdamKyle). 389 words, ~656 tokens.

Download SKILL.mdSave it as .claude/skills/phpunit-testing/SKILL.md (or your agent's skills folder).
name
phpunit-testing
description
Use this skill when writing, reviewing, or refactoring PHPUnit tests in this repository.

PHPUnit Testing

Scope

Use this skill for PHPUnit tests only.

Do not use this skill for production PHP/Laravel app code. Those rules belong in the back-end-conventions skill.

Before writing or changing a test, inspect the existing test class, nearby tests in the same module, relevant factories, models, value objects, enums, and the production code under test.

Test Structure

  • One behavior per test method.
  • Inline all setup directly inside each test method body.
  • Do not add private, protected, or public helper methods to a test class.
  • Do not extract shared setup into a method and call it from multiple tests.
  • Do not use PHPUnit data providers.
  • Do not use loops inside a test to cover multiple independent behaviors or inputs.
  • If two scenarios are independent behaviors, write two separate test methods, not one test with a loop or a data provider.
  • A test method name should describe the single behavior being verified.

What Not To Test

  • Do not call private or protected methods directly from a test.
  • Do not use reflection to bypass visibility, invoke private/protected methods, or read private/protected properties.
  • Test behavior through the class's public API only.

Mocking

  • Use Mockery only where the existing project test patterns already use it for that class or collaborator.
  • Do not introduce Mockery mocking for classes the surrounding tests exercise concretely (models, factories, value objects).
  • Prefer real model/factory instances over mocks when the existing test patterns in that module do so.
Show full SKILL.md (151 more words)Show less

Assertions And Fixtures

  • Use model factories from database/factories to build test data.
  • Keep assertions specific to the single behavior under test.
  • Do not assert on unrelated side effects that are not part of the behavior being verified.

Running Tests

  • Run each required targeted test command exactly once.
  • Do not run the same test command repeatedly.
  • Do not run test loops such as for i in 1 2 3; do ...; done around a test command.
  • Do not run the full suite unless explicitly asked.
  • Do not run coverage unless explicitly asked.
  • If a required command fails, make one relevant fix, then rerun that command exactly once more.
  • Do not rerun a passing command again just to prove stability unless explicitly asked.

Output Rules

  • Do not claim a test command was run unless it was actually run.
  • If a command cannot be run, say exactly why.
  • Report actual pass/fail results, not assumed results.

© AdamKyle, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/phpunit-testing of AdamKyle/flare.

Open the folder on GitHubat commit e22bc47

Compare with similar skills

Phpunit Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Phpunit Testing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Phpunit Testing this skillAdamKyle/flare162—~656Automated safety check: PassMIT
Guidelinesakash-network/node1.1k22 repos~577Automated safety check: PassMIT
Component Refactoringlangflow-ai/langflow156k—~3.5kAutomated safety check: PassMIT
Migrate Core Code to Submodulestinyhumansai/openhuman42k—~2.6kAutomated safety check: PassGPL-3.0
Systematic Code Refactoringluongnv89/claude-howto42k—~3kAutomated safety check: PassMIT
Codexskills-directory/skill-codex1.5k3 repos~1.8kAutomated safety check: PassMIT

Similar skills

  • Guidelines

    akash-network/node

    Behavioral guidelines to reduce common LLM coding mistakes. An agent skill from akash-network/node.

    1.1k GitHub starsUsed in 22 repos~577 tokens
    DevelopmentAuto-check passed
  • Component Refactoring

    langflow-ai/langflow

    Refactor high-complexity React components in Langflow frontend.

    156k GitHub stars~3.5k tokensUpdated today
    DevelopmentAuto-check passed
  • Migrate Core Code to Submodules

    tinyhumansai/openhuman

    Plans and carries out moving non-host-specific code and its tests from the OpenHuman core into vendored tiny submodule libraries, then releases the submodule and re-pins the host.

    42k GitHub stars~2.6k tokensUpdated today
    DevelopmentAuto-check passed
  • Systematic Code Refactoring

    luongnv89/claude-howto

    Guides refactoring in phases based on Martin Fowler's method: research, test coverage check, planning and small tested steps, with your approval at each phase.

    42k GitHub stars~3k tokensUpdated 7 days ago
    DevelopmentAuto-check passed
  • Codex

    skills-directory/skill-codex

    A skill your agent uses when the user asks to run Codex CLI (codex exec, codex resume) or references OpenAI Codex for code analysis, refactoring, or automated editing

    1.5k GitHub starsUsed in 3 repos~1.8k tokens
    DevelopmentAuto-check passed
  • Ponytail

    DavidObando/gsharp

    Forces the laziest solution that actually works, simplest, shortest, most minimal.

    565 GitHub starsUsed in 8 repos~1.7k tokens
    DevelopmentAuto-check passed

More from AdamKyle/flare

  • Back End Conventions

    AdamKyle/flare

    A skill your agent uses when writing, reviewing, or refactoring PHP/Laravel app code in this repository.

    162 GitHub stars~5.6k tokensUpdated 2 days ago
    Auto-check passed
  • Readonly Shell

    AdamKyle/flare

    Allows Claude to inspect files with safe read-only shell commands without asking for permission.

    162 GitHub stars~274 tokensUpdated 2 days ago
    Auto-check passed

Categories

Questions about Phpunit Testing

What does Phpunit Testing do?

A skill your agent uses when writing, reviewing, or refactoring PHPUnit tests in this repository. Phpunit Testing is an agent skill from AdamKyle/flare. Use this skill when writing, reviewing, or refactoring PHPUnit tests in this repository.

When should I use Phpunit Testing?

Phpunit Testing fits situations like: refactoring PHPUnit tests in this repository; tasks that involve Refactoring.

How do I install Phpunit Testing in Claude Code?

Run `npx skills add AdamKyle/flare --skill phpunit-testing -a claude-code`. Or copy the skill folder (.agents/skills/phpunit-testing in AdamKyle/flare) into .claude/skills/phpunit-testing in your project. Claude Code loads it when a task matches its description.

How do I install Phpunit Testing in Codex?

Run `npx skills add AdamKyle/flare --skill phpunit-testing -a codex`. Or copy the skill folder (.agents/skills/phpunit-testing in AdamKyle/flare) into .agents/skills/phpunit-testing in your project. Codex loads it when a task matches its description.

Can I use Phpunit Testing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add AdamKyle/flare --skill phpunit-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/phpunit-testing, .gemini/skills/phpunit-testing, .github/skills/phpunit-testing and .opencode/skills/phpunit-testing in your project.

What does Phpunit Testing need to run?

SKILL.md names no scripts, command-line tools or credentials: Phpunit Testing is instructions for the agent only.

Does Phpunit Testing access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Phpunit Testing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Phpunit Testing use?

Phpunit Testing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Phpunit Testing use?

About 656 tokens (SKILL.md is roughly 2.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Phpunit Testing?

Skills that share tags, products or a category with Phpunit Testing: Guidelines (akash-network/node, 1.1k stars), Component Refactoring (langflow-ai/langflow, 156k stars), Migrate Core Code to Submodules (tinyhumansai/openhuman, 42k stars) and Systematic Code Refactoring (luongnv89/claude-howto, 42k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Phpunit Testing?

AdamKyle (a GitHub user) maintains it in AdamKyle/flare, which has 162 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 5, 2026.

Source: AdamKyle/flare on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.