manoel-freitas/amare
1
0
Fork 0
Code Issues Pull Requests 2 Actions Packages Projects Releases Wiki Activity
Files
research/man-135-classify-amare-mvp
amare/docs/agents/issue-tracker.md
manoel freitas 93b680c172
All checks were successful
CI / static (push) Successful in 2m25s
Details
CI / unit (push) Successful in 3m34s
Details
CI / feature (push) Successful in 3m17s
Details
CI / container (push) Successful in 20s
Details
CI / browser (push) Successful in 3m43s
Details
docs: require Linear issues and auto-ship PRs (#4) 
## WHAT

- `AGENTS.md` e `docs/agents/issue-tracker.md`: todo trabalho e todo PR precisam de issue Linear.
- SDLC automático: trabalho feito → testes feitos ou atualizados → pre-commit verde → commit → PR, sem perguntar.
- Templates de PR idênticos no Gitea (`.gitea/PULL_REQUEST_TEMPLATE.md`) e no GitHub (`.github/pull_request_template.md`) com WHAT / WHY / HOW / Linear Issue / Comments.

## WHY

Agentes estavam soltos no tracker e paravam pra perguntar se podiam commitar. O contrato precisa ser o ciclo completo, com issue Linear e template de PR.

## HOW

Docs e templates only. Sem mudança de runtime. Pre-commit (`composer pint:check` + `composer phpstan`) passou.

## Linear Issue

- [MAN-132](https://linear.app/maneco-workspace/issue/MAN-132/exigir-issue-linear-em-todo-trabalho-e-pr)
- [MAN-133](https://linear.app/maneco-workspace/issue/MAN-133/adicionar-pr-template-no-gitea-e-no-github)

## Comments

GitHub é o mirror legado; o PR canônico é este no Gitea.

Reviewed-on: #4
Co-authored-by: manoel freitas <manoel.josefneto@gmail.com>
Co-committed-by: manoel freitas <manoel.josefneto@gmail.com>
2026-08-13 11:46:36 +00:00

2.1 KiB
Raw Permalink Blame History

Issue tracker: Linear

Issues and specs for this repo live in Linear. Use the Linear MCP tools for all operations.

Conventions

  • Create an issue: save_issue with title, team (Maneco-workspace), and markdown description. Assign via assignee ("me" for the current user).
  • Read an issue: get_issue by identifier (e.g. LIN-123).
  • List issues: list_issues filtered by team, assignee, state, or project.
  • Comment on an issue: save_comment with issueId and markdown body.
  • Apply / remove labels: save_issue with labels (replaces the full set).
  • Move workflow state: save_issue with state (e.g. Todo, In Progress, Done, Canceled).
  • Link work: save_issue with project, cycle, parentId, blocks / blockedBy (relations are append-only).
  • Cross-link to a PR: attach the PR URL via save_issue links.

Required: issue before work and before PR

Every branch, worktree, and pull request in this repo must be tied to a Linear issue.

  1. Starting work: require an identifier (e.g. MAN-132). If the user did not give one, search Linear. If none fits, create the issue with save_issue on team Maneco-workspace before creating a branch or worktree.
  2. Branch: include the identifier (docs/man-132-…, feat/man-126-…).
  3. PR: cite identifier + URL in the body. An OpenSpec change is extra context, not a substitute.
  4. After the PR exists: attach the PR URL on the issue via save_issue links. Do this as part of the automatic SDLC in AGENTS.md — do not ask before opening the PR.
  5. If Linear MCP is unavailable, stop and report — do not start untracked work.

When a skill says "publish to the issue tracker"

Create a Linear issue with save_issue on team Maneco-workspace.

When a skill says "fetch the relevant ticket"

Run get_issue on the identifier and read the description, state, labels, and assignee.

Reference in New Issue View Git Blame Copy Permalink