Pester Failure Analysis
PowerShell/PowerShell
Investigates failing Pester tests in PowerShell CI jobs by following a six-step workflow from pull request status to documented fix recommendations.
Fix TeamCity project-leak test failures end to end. An agent skill from JetBrains/intellij-community.
Install Fix Project Leak From Tc Report
$ npx skills add JetBrains/intellij-community --skill fix-project-leak-from-tc-report -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install JetBrains/intellij-community fix-project-leak-from-tc-report --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/JetBrains/intellij-community.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/fix-project-leak-from-tc-report .claude/skills/fix-project-leak-from-tc-report && rm -rf skills-srcUse ~/.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/
Install the "fix-project-leak-from-tc-report" agent skill from https://github.com/JetBrains/intellij-community/tree/master/.agents/skills/fix-project-leak-from-tc-report into .claude/skills/fix-project-leak-from-tc-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-project-leak-from-tc-report", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/JetBrains/intellij-community/tree/master/.agents/skills/fix-project-leak-from-tc-reportType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add JetBrains/intellij-community --skill fix-project-leak-from-tc-report -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install JetBrains/intellij-community fix-project-leak-from-tc-report --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JetBrains/intellij-community.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/fix-project-leak-from-tc-report .agents/skills/fix-project-leak-from-tc-report && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "fix-project-leak-from-tc-report" agent skill from https://github.com/JetBrains/intellij-community/tree/master/.agents/skills/fix-project-leak-from-tc-report into .agents/skills/fix-project-leak-from-tc-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-project-leak-from-tc-report", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add JetBrains/intellij-community --skill fix-project-leak-from-tc-report -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install JetBrains/intellij-community fix-project-leak-from-tc-report --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JetBrains/intellij-community.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/fix-project-leak-from-tc-report .cursor/skills/fix-project-leak-from-tc-report && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "fix-project-leak-from-tc-report" agent skill from https://github.com/JetBrains/intellij-community/tree/master/.agents/skills/fix-project-leak-from-tc-report into .cursor/skills/fix-project-leak-from-tc-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-project-leak-from-tc-report", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/JetBrains/intellij-community.git --path .agents/skills/fix-project-leak-from-tc-report--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add JetBrains/intellij-community --skill fix-project-leak-from-tc-report -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install JetBrains/intellij-community fix-project-leak-from-tc-report --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JetBrains/intellij-community.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/fix-project-leak-from-tc-report .gemini/skills/fix-project-leak-from-tc-report && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "fix-project-leak-from-tc-report" agent skill from https://github.com/JetBrains/intellij-community/tree/master/.agents/skills/fix-project-leak-from-tc-report into .gemini/skills/fix-project-leak-from-tc-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-project-leak-from-tc-report", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install JetBrains/intellij-community fix-project-leak-from-tc-reportInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add JetBrains/intellij-community --skill fix-project-leak-from-tc-report -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/JetBrains/intellij-community.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/fix-project-leak-from-tc-report .github/skills/fix-project-leak-from-tc-report && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "fix-project-leak-from-tc-report" agent skill from https://github.com/JetBrains/intellij-community/tree/master/.agents/skills/fix-project-leak-from-tc-report into .github/skills/fix-project-leak-from-tc-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-project-leak-from-tc-report", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add JetBrains/intellij-community --skill fix-project-leak-from-tc-report -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install JetBrains/intellij-community fix-project-leak-from-tc-report --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JetBrains/intellij-community.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/fix-project-leak-from-tc-report .opencode/skills/fix-project-leak-from-tc-report && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "fix-project-leak-from-tc-report" agent skill from https://github.com/JetBrains/intellij-community/tree/master/.agents/skills/fix-project-leak-from-tc-report into .opencode/skills/fix-project-leak-from-tc-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-project-leak-from-tc-report", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
fix-project-leak-from-tc-report- GitHub stars
- 21k
- Token cost
- ~8.3k tokens
- SKILL.md length
- 3,461 words
- Files
- 3 (incl. scripts)
- Skills in repo
- 39
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Fix TeamCity project-leak test failures end to end. An agent skill from JetBrains/intellij-community.
- Works in 5 steps: identify the culprit test → reproduce locally 10 times → analyze every unique retention chain → …
- Tasks that involve Failing and flaky tests
- SKILL.md covers Phase 1 — identify the culprit…, Phase 2 — reproduce locally 10…, Phase 3 — analyze every unique… and Phase 4 — apply fixes, plus 4 more sections
- Runs Shell scripts from its folder; calls git
What it does
Fix Project Leak From Tc Report is an agent skill from JetBrains/intellij-community, published by the product's own GitHub organization. Fix TeamCity project-leak test failures end to end.
Its SKILL.md is about 8.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including scripts (for example `scripts/leak-loop.sh` and `scripts/summarize-runs.sh`).
It sits in Testing & QA, covering Failing and flaky tests. It works with JetBrains IDEs. The repository describes itself as: IntelliJ IDEA & IntelliJ Platform.
When your agent uses it
- Tasks that involve Failing and flaky tests
Example prompts
- “/fix-project-leak-from-tc-report”
Requirements
- A Bash shell
Workflow steps
5 steps, taken from the step headings in SKILL.md.
- identify the culprit test
- reproduce locally 10 times
- analyze every unique retention chain
- apply fixes
- verify
What it can do on your machine
Read from SKILL.md and the folder at commit 27dbc78. 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
Ships 2 files in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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
Fix Project Leak From Tc Report loads about 8.3k tokens when it runs. Until then it costs about 21 tokens; SKILL.md has 3,461 words of instructions outside code blocks.
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); the scripts in this folder are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 3,461 words (~8,254 tokens).
“This is the full fix workflow. Investigation-only tasks (identify + reproduce + analyze) are covered by the sibling leaking-test-investigation-by-tc-report skill; the two overlap in phases 1–3 but this one adds phases 4–5 (apply fix, verify).”
- name
- fix-project-leak-from-tc-report
Files
SKILL.md and 2 other files (scripts) in .agents/skills/fix-project-leak-from-tc-report of JetBrains/intellij-community.
- SKILL.md
- scripts/leak-loop.sh
- scripts/summarize-runs.sh
Open the folder on GitHubat commit 27dbc78
Compare with similar skills
Fix Project Leak From Tc Report 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Fix Project Leak From Tc Report this skillJetBrains/intellij-community | 21k | — | ~8.3k | Automated safety check: Pass | Custom licence | |
| Pester Failure AnalysisPowerShell/PowerShell | 56k | — | ~5.1k | Automated safety check: Pass | MIT | |
| Cucumber and Playwright E2E Testslanggenius/dify | 158k | — | ~682 | Automated safety check: Pass | Custom licence | |
| Diagnose Playwright Failure as Product Bugappsmithorg/appsmith | 41k | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Apple Container Test RunnerRustPython/RustPython | 22k | — | ~467 | Automated safety check: Pass | MIT | |
| Fix Failing Playwright Specappsmithorg/appsmith | 41k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Cucumber and Playwright E2E Tests
langgenius/dify
Guides changes and reviews of the Cucumber and Playwright end-to-end suite under `e2e/`: feature files, step definitions, support code, tags, locators and assertions.
Diagnose Playwright Failure as Product Bug
appsmithorg/appsmith
Investigates a stubbornly failing Playwright test as a possible product bug, using error output, screenshots, traces and server code, and writes a structured bug report.
Apple Container Test Runner
RustPython/RustPython
Runs RustPython tests inside a Linux container built with Apple's container CLI, so macOS users can compare Linux results with their local ones.
Fix Failing Playwright Spec
appsmithorg/appsmith
Fixes failing Playwright specs by reading the error, classifying the cause in the test code and applying corrections that follow project conventions.
Perf Regression Triage
mozilla-firefox/firefox
Handle a Perfherder performance regression bug end to end: read the alert bug, confirm whether the regression is real, find the cause, and iterate to a fix.
More from JetBrains/intellij-community
All 39 skills in this repo- Official
Youtrack Community
JetBrains/intellij-community
YouTrack CLI for a community checkout; the monorepo uses youtrack.
- Official
Compare Python Typecheckers
JetBrains/intellij-community
Compare Python type inference with ty, pyrefly, and basedpyright.
- Official
Sibling Checkout Commits
JetBrains/intellij-community
Take commits from a sibling checkout as patches, without a fetch.
- Official
Code Style
JetBrains/intellij-community
Apply IntelliJ Kotlin and Java code style when writing or reviewing.
- Official
Notebook For Experiment
JetBrains/intellij-community
Create reproducible Jupyter notebooks for performance experiments.
- Official
Jewel Markdown
JetBrains/intellij-community
Build or debug Jewel Markdown parsing, rendering, and styling.
Related
Works with
Categories
Questions about Fix Project Leak From Tc Report
What does Fix Project Leak From Tc Report do?
Fix TeamCity project-leak test failures end to end. An agent skill from JetBrains/intellij-community. Fix Project Leak From Tc Report is an agent skill from JetBrains/intellij-community, published by the product's own GitHub organization. Fix TeamCity project-leak test failures end to end.
When should I use Fix Project Leak From Tc Report?
Fix Project Leak From Tc Report fits situations like: tasks that involve Failing and flaky tests.
How do I install Fix Project Leak From Tc Report in Claude Code?
Run `npx skills add JetBrains/intellij-community --skill fix-project-leak-from-tc-report -a claude-code`. Or copy the skill folder (.agents/skills/fix-project-leak-from-tc-report in JetBrains/intellij-community) into .claude/skills/fix-project-leak-from-tc-report in your project. Claude Code loads it when a task matches its description.
How do I install Fix Project Leak From Tc Report in Codex?
Run `npx skills add JetBrains/intellij-community --skill fix-project-leak-from-tc-report -a codex`. Or copy the skill folder (.agents/skills/fix-project-leak-from-tc-report in JetBrains/intellij-community) into .agents/skills/fix-project-leak-from-tc-report in your project. Codex loads it when a task matches its description.
Can I use Fix Project Leak From Tc Report 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 JetBrains/intellij-community --skill fix-project-leak-from-tc-report -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fix-project-leak-from-tc-report, .gemini/skills/fix-project-leak-from-tc-report, .github/skills/fix-project-leak-from-tc-report and .opencode/skills/fix-project-leak-from-tc-report in your project.
What does Fix Project Leak From Tc Report need to run?
Going by SKILL.md and its folder, Fix Project Leak From Tc Report needs a shell for the scripts in its folder and the command-line tools its instructions call (git). Our summary lists: A Bash shell.
Does Fix Project Leak From Tc Report access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Fix Project Leak From Tc Report 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Fix Project Leak From Tc Report use?
Fix Project Leak From Tc Report has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Fix Project Leak From Tc Report use?
About 8.3k tokens (SKILL.md is roughly 33k 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 Fix Project Leak From Tc Report?
Skills that share tags, products or a category with Fix Project Leak From Tc Report: Pester Failure Analysis (PowerShell/PowerShell, 56k stars), Cucumber and Playwright E2E Tests (langgenius/dify, 158k stars), Diagnose Playwright Failure as Product Bug (appsmithorg/appsmith, 41k stars) and Apple Container Test Runner (RustPython/RustPython, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Fix Project Leak From Tc Report?
JetBrains (a GitHub organization, an official publisher) maintains it in JetBrains/intellij-community, which has 20,623 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on October 11, 2026.
Source: JetBrains/intellij-community on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.