fix-bug
Skill538 starsChanged yesterdayAGPL-3.0View on GitHub
Canonical workflow for investigating and fixing bugs in torrust-tracker. Use when work is substantively a bug, even if issue metadata or labels are missing or wrong. Requires source analysis, real-artifact reproduction or infeasibility evidence, regression-test selection, red/green validation, code fix, and like-for-like final recheck.
46 other projects use a version of this.
Adopted by
Most recently taken up by
- flegaspi700/pmo-project-standardizationtheir own version, first seen Nov 16, 2026
- Crypto69/claude-skillstheir own version, first seen Nov 16, 2026
- seancabalse/agentic-playbooktheir own version, first seen Nov 16, 2026
- Slama-Consulting/proofbenchtheir own version, first seen Nov 15, 2026
- todoist/todoist-clitheir own version, first seen Nov 15, 2026
- Doist/todoist-aitheir own version, first seen Nov 9, 2026
Used with
Projects with it also use improvement, build-feature and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
kiminmonacoSkillimprovement
Guide for making improvements to existing ClaudeBar functionality using TDD. Use this skill when: (1) Enhancing existing features (not adding new ones) (2) Improving UX, performance, or code quality (3) User asks "improve X", "make Y better", or "enhance Z" (4) Small enhancements that don't require full architecture design For NEW features, use implement-feature skill instead.
Also in 4 projects that use this
sirakinbSkillbuild-feature
Autonomous task loop that picks ready tasks, implements them, updates progress.txt, commits, and repeats. Use when asked to 'build feature', 'run the loop', or 'implement these tasks'.
Also in 7 projects that use this
kiminmonacoSkillimplement-feature
Guide for implementing features in ClaudeBar following architecture-first design, TDD, rich domain models, and Swift 6.2 patterns. Use this skill when: (1) Adding new functionality to the app (2) Creating domain models that follow user's mental model (3) Building SwiftUI views that consume domain models directly (4) User asks "how do I implement X" or "add feature Y" (5) Implementing any feature that spans Domain, Infrastructure, and App layers
Also in 7 projects that use this
SentrySkillwrite-tests
Write tests following project conventions. Use when adding new tests or modifying existing ones.
Also in 7 projects that use this
DockerSkillreview-changes
Review uncommitted or recently committed documentation changes for correctness, coherence, and style compliance. Use before creating a PR to catch issues. "review my changes", "review the diff", "check the fix before submitting", "does this look right".
Also in 4 projects that use this
MicrosoftSkilladd-feature
Add new T-SQL features to ScriptDOM parser. Asks questions about SQL Server version and feature type, then guides through grammar changes, AST updates, script generation, and testing using existing instruction files. Handles syntax additions, new functions, data types, index types, and validation rules.
Also in 3 projects that use this
Other versions46 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 46
- remix-run/react-router★ 57ksame name
- ktorio/ktor★ 15ksame name
- JetBrains/Exposed★ 9.3ksame name
- bytebase/dbhub★ 3.9ksame name
- The-OpenROAD-Project/OpenROAD★ 3.3ksame name
- JamieMason/syncpack★ 2.1ksame name
- tddworks/ClaudeBar★ 1.6ksame name
- Harry-kp/vortix★ 779same name
- Doist/todoist-ai★ 565same name
- tddworks/asc-cli★ 393same name
36 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository59 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- .github/workflows/AGENTS.mdAGENTS.md
- packages/AGENTS.mdAGENTS.md
- src/AGENTS.mdAGENTS.md
- tests/AGENTS.mdAGENTS.md
- add-new-skillSkill
- add-rust-dependencySkill
- add-workspace-memberSkill
- catalog-security-vulnerabilitiesSkill
- check-runner-healthSkill
- cleanup-completed-issuesSkill
- commit-changesSkill
- create-adrSkill
- create-feature-branchSkill
- create-issueSkill
- create-markdown-templateSkill
- create-refactor-planSkill
- fetch-review-threadsSkill
- fix-clippy-warningsSkill
- handle-errors-in-codeSkill
- handle-secretsSkill
- implement-workflowSkill
- install-linterSkill
- link-subissue-to-parent-issueSkill
- manual-http-download-completion-e2eSkill
- manual-torrent-cleanup-e2eSkill
- manual-udp-download-completion-e2eSkill
- merge-pull-requestSkill
- open-pull-requestSkill
- process-copilot-suggestionsSkill
- process-pr-review-feedbackSkill
- process-pr-reviewSkill
- public-trackers-for-testingSkill
- push-changesSkill
- release-new-versionSkill
- release-workspace-packageSkill
- reopen-issueSkill
- resolve-review-threadsSkill
- review-prSkill
- review-taskSkill
- run-benchmarksSkill
- run-lintersSkill
- run-manual-docker-security-scanSkill
- run-pre-commit-checksSkill
- run-pre-push-checksSkill
- run-tracker-locallySkill
- setup-dev-environmentSkill
- structured-runtime-loggingSkill
- triage-github-security-findingsSkill
- update-dependenciesSkill
- update-github-workflow-actionsSkill
- use-rest-apiSkill
- use-tracker-clientSkill
- wait-for-pr-reviewSkill
- watch-pull-request-checksSkill
- write-markdown-docsSkill
- write-unit-testSkill
- add-new-skillSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. 0 are common, 14 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 46 edited versions we read keep these.
14
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 46 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

