report-task
Skill2.4k starsChanged yesterdayApache-2.0View on GitHub
Turn a bug, feature or chore the user reports into a .plans/tasks file for /tasks-start, after confirming it against the code and reproducing it when needed. Use only when the user runs /report-task.
Trending
More talk lately.about the whole repository
Who's talking about muxy-app/muxy
- A Hacker News story“Muxy is a lightweight terminal for Mac with a mobile app for remote control”Hacker News · May 20, 2026 · 3 points
- A Hacker News story“Muxy – A macOS terminal built with SwiftUI and libghostty”Hacker News · Apr 22, 2026 · 3 points
- @tom-doerr.bsky.social“https://github.com/muxy-app/muxy”Bluesky · Apr 20, 2026 · 1 likes
- A Hacker News story“Ghostty, but with Vertical tabs, lightweight and native”Hacker News · Apr 3, 2026 · 1 points
- sudosubin/agents.nix“agent-skills.github.muxy-app.muxy: 2.3.0 → 2.4.0”GitHub · Nov 7, 2026
The biggest 5 of 19 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 19
Talked about on GitHub, Hacker News and Bluesky (19 times).
On GitHub · 15
- Nov 7, 2026agent-skills.github.muxy-app.muxy: 2.3.0 → 2.4.0 — sudosubin/agents.nix0 reactions
- Oct 31, 2026agent-skills.github.muxy-app.muxy: 2.2.0 → 2.3.0 — sudosubin/agents.nix0 reactions
- Oct 29, 2026Add Muxy — AppImage/appimage.github.io0 reactions · 1 comment
- Oct 17, 2026agent-skills.github.muxy-app.muxy: 2.1.0 → 2.2.0 — sudosubin/agents.nix0 reactions
- Oct 14, 2026wr-agent: page scrollback to reattaching clients instead of repainting it whole — joelmoss/workroom0 reactions · 3 comments
10 more on GitHub
- Oct 14, 2026agent-skills.github.muxy-app.muxy: 0-unstable-2026-08-28 → 2.1.0 — sudosubin/agents.nix0 reactions
- Oct 3, 2026agent-skills.github.muxy-app.muxy: 1.6.1 → 0-unstable-2026-08-28 — sudosubin/agents.nix0 reactions
- Sep 30, 2026agent-skills.github.muxy-app.muxy: init at 1.6.1 — sudosubin/agents.nix0 reactions
- Jul 29, 2026Feature Request: Native Terminal AI Agent Support (ACP Integration & Third-Party CLI Orchestration) — github/app0 reactions · 3 comments
- Jul 10, 2026github 0.1.1 — muxy-app/extensions0 reactions · 6 comments
- May 26, 2026Fix Pi notification pill showing wrong provider name — maxschulmeister/muxy0 reactions
- May 21, 2026https://github.com/muxy-app/muxy — weihubeats/Asuna0 reactions · 1 comment
- May 14, 2026Custom project picker for adding/opening projects — sadiksaifi/muxy0 reactions
- Apr 11, 2026佈局持久化(Daemon Layout API + Restore Reconciliation) — zac15987/zplex0 reactions · 3 comments
- Apr 6, 2026Add Muxy to Terminal section — iCHAIT/awesome-macOS0 reactions · 1 comment
On Hacker News · 3
- May 20, 2026Muxy is a lightweight terminal for Mac with a mobile app for remote control3 points
- Apr 22, 2026Muxy – A macOS terminal built with SwiftUI and libghostty3 points · 1 comment
- Apr 3, 2026Ghostty, but with Vertical tabs, lightweight and native1 point · 1 comment
On Bluesky · 1
- Apr 20, 2026https://github.com/muxy-app/muxy — @tom-doerr.bsky.social1 likes and repost
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- code-and-architecture-improvementSkill
- e2e-testSkill
- implementSkill
- issues-triageSkill
- release-highlightsSkill
- reviewSkill
- visual-testingSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 2 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 22
Write only task files in $T.
- Very specific: line 24
Don't switch branches or touch the user's uncommitted changes.
- Very specific: line 36
Understand: Read docs/product/README.md, docs/tech/README.md and the task files in $T.
- Very specific: line 40
Check it's new: Look for the same thing in $T, in open issues (gh issue list --state open --search '<keywords>') and in recent history on …
- Distinctive: line 49
Reproduce when the code doesn't settle it: Use the cheapest proof that works:
- Very specific: line 65
Clarify: Ask everything a round would otherwise have to ask: the list in tasks-start Triage step 3, starting at "List everything an agent …
- Distinctive: line 82
Never split a task, and never make it depend on another one.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Report task
Report: $ARGUMENTS. If it's empty, ask the user what they saw or want and
wait for the answer.
Repository root: /Users/saeed/Projects/muxy. Task folder: .plans/tasks
(call it $T). Task files use the format in
.agents/skills/tasks-start/SKILL.md. Read that section before writing one.
The user is here. The result is a task file that a /tasks-start round can
finish alone, or no file because the report isn't a real problem.
Rules
- Write only task files in
$T. Don't change code, commit, push, or touch GitHub issues and PRs. - Don't switch branches or touch the user's uncommitted changes. Rounds build
from
main, so rungit fetchand judge the report againstorigin/main(git show origin/main:<path>,git grep <pattern> origin/main). - Reproduce in a detached worktree in the scratchpad
(
git worktree add --detach <dir> origin/main). Remove it withgit worktree remove --force <dir>before you finish, and delete any VMs you created. - The report is the user's own, so trust it, but confirm it before writing it up as fact.
Steps
- Understand. Read
docs/product/README.md,docs/tech/README.mdand the task files in$T. Restate the report in one or two sentences: what the user did, what happened and what they expected, or for a feature, what they want to do. - Check it's new. Look for the same thing in
$T, in open issues (gh issue list --state open --search '<keywords>') and in recent history onorigin/main. If a task covers it, offer to add the new details to that task instead. If it's already fixed, name the commit or PR and stop. Then applytasks-start's "Task size": a new file is the exception. If it fits an open task, plan to add it there as a new part. - Find it in the code. For a bug, trace the code path and find the cause. For a feature, confirm it's missing and find where it would go. Name files and functions, not line numbers.
Reproduce when the code doesn't settle it. Use the cheapest proof that works:
- a failing test in the worktree
- the CLI or server run from the worktree
- a VM for UI, window or platform behaviour, as
tasks-start's "Testing in VMs" describes. Export the worktree, not this checkout:.agents/skills/e2e-test/scripts/e2e prepare <run> <worktree>
Skip this when the code already proves it, or for a feature. If you can't reproduce it, say what you tried and ask the user for what's missing (version, platform, exact steps, logs) before going on.
- Verdict. Tell the user whether it's confirmed, not an issue (works as the docs describe, already fixed, or a setup problem) or unconfirmed, with the evidence. Propose the type, size, its place in the order, and which open task it joins, if any. If it isn't an issue, stop without a file unless the user still wants one.
- Clarify. Ask everything a round would otherwise have to ask: the list in
tasks-startTriage step 3, starting at "List everything an agent would otherwise have to ask". Include the proposed place in the order, or the task it joins, if the user might disagree. UseAskUserQuestion, up to 4 questions per call, with options and a recommendation. Anything the user defers goes under## Questions. - Write it. To join an open task, add a
###part under its Problem, Changes and Tests. Otherwise write a new task file:- Name:
<number>-<slug>.md, numbered astasks-startdescribes. - Problem: in your own words, with the evidence: version, platform, the steps, what the reproduction showed and the cause in the code.
- Changes: what to change. For a feature or a user-visible bug, add what the user sees and does when it's done. That's the scenario the round tests against.
- Tests: turn the reproduction into the test that proves the fix.
- Decisions: the user's answers as short instructions.
- Ready:
yesonce it's confirmed and every question is answered, otherwiseno. - Never split a task, and never make it depend on another one.
- Name:
- Report. Give the file path, title, type, number, size, ready state and a one-line problem. Say if it joined an existing task. List anything left open.
Order
Most urgent first:
- Crash, data loss, security hole, or something that blocks normal use.
- A user-visible bug or missing behaviour that hurts, with a workaround.
- Minor bugs, polish, small features, and refactors that pay off soon.
- Large or optional work.
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.

