← ClaudeAtlas

report_upstream_issuelisted

Files a bug/issue in the right place — routes bugs in shared project-init machinery (hooks, CI templates, lifecycle scripts, board automation, rules, skills) upstream to the project-init repo so they are fixed once for every project, and keeps project-specific bugs local. Use whenever the user asks to report, register, or file a bug or issue.
VytCepas/project-init · ★ 0 · Data & Documents · score 72
Install: claude install-skill VytCepas/project-init
Route a bug report to the repo that owns the defect. A bug in *shared scaffolding* (the machinery project-init generated into this project) should be filed **upstream** in project-init so it is fixed once for every project — not re-reported per project. A bug in *this project's own code* is filed locally. ## Step 1 — Classify: project-level vs tooling/upstream Decide who owns the faulty behavior. Use the heuristics; when a signal points upstream, it is almost certainly upstream. | Signal | Project-level → file **locally** | Tooling / scaffolding → file **upstream (project-init)** | |---|---|---| | Where the faulty file lives | the project's own `src/`, app code, business logic, its own tests | `.agents/hooks/`, `.agents/scripts/`, `.agents/skills/`, `.agents/rules/`, scaffolded `.github/workflows/*`, board automation, the DAG/command guard, governance policy, `config.yaml` machinery | | Who wrote it | this project's team | generated by `project-init` scaffold/upgrade (you did not hand-write it here) | | Would other project-init projects hit it? | No — specific to this repo | **Yes** — the same defect reproduces in any scaffolded project | | Examples | "login endpoint returns 500", "pagination off-by-one", "our parser drops empty rows" | "the pre-commit gate blocks a valid commit", "board automation ignores `- Field:` bullet metadata", "the command guard false-positives on a safe command", "the issue-creation helper crashes with `--parent`", "a scaffolded rule file is wrong