Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

loop-issue-triage

Étoiles186

Forks32

Mis à jour4 juillet 2026 à 13:58

Proactive loop that keeps GitHub Issues in erp-mafia/accounted tidy (label, dedupe, close stale/already-fixed, reconcile with merged PRs) and auto-implements small, well-scoped fixes as PRs. Use on a schedule (cloud routine) or on-demand via /loop-issue-triage. Follows dev_docs/loops.md (propose-don't-merge).

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

erp-mafia

erp-mafia/accounted

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	loop-issue-triage
description	Proactive loop that keeps GitHub Issues in erp-mafia/accounted tidy (label, dedupe, close stale/already-fixed, reconcile with merged PRs) and auto-implements small, well-scoped fixes as PRs. Use on a schedule (cloud routine) or on-demand via /loop-issue-triage. Follows dev_docs/loops.md (propose-don't-merge).

loop-issue-triage

Goal: the open-issue list is accurately labeled and free of stale/duplicate/already-fixed items, and a couple of small fixes ship as PRs each run. Never merge. Read .claude/loops.md first.

Preflight

gh auth status, repo erp-mafia/accounted. If it fails, stop and report "environment not provisioned".

1. Triage every open issue

gh issue list --state open --limit 100 --json number,title,labels,createdAt,updatedAt,comments

For each issue lacking a type label:

Classify → apply one of bug / enhancement / question / documentation.
Dedupe → search for near-duplicates (gh issue list --search "<keywords> in:title,body state:all"). If a duplicate, label duplicate, comment linking the canonical issue, and close the newer one.
Stale → no activity > 30 days AND not actionable: comment asking if still relevant; don't close unilaterally unless clearly obsolete.

2. Reconcile with completed work (the "are tickets up to date?" job)

For each open issue, check whether a merged PR or recent commit already resolved it: gh pr list --state merged --search "<#num or keywords>", git log --oneline -S"<keyword>".
If resolved: comment with the PR/commit link, verify the fix exists in main, then close.
Conversely, if a merged PR said Closes #N but #N is still open, close it with a pointer.

3. Auto-fix small issues (propose-don't-merge): cap 2 PRs/run

Pick issues that are small, localized, and low-risk (a clear bug in one file, a copy/label fix, a missing empty/loading state, a validation gap). Never auto-fix anything touching the bookkeeping engine, money math, migrations/triggers, auth, or compliance logic: those get loop:needs-human.

Branch loop/issue-<n>, minimal fix, run the loop-verify gate.
Open PR with body Closes #<n> + a one-line summary. Label loop:auto, loop:triage.
If the fix turns out larger/riskier than expected mid-way, abandon the branch and instead add a scoping comment on the issue + loop:needs-human.

4. Anti-thrash & report

Don't re-triage issues already labeled this run. Summarize: labeled N, deduped N, closed N (with why), fix PRs opened, escalated N. That summary is the completion notification.

Plus depuis ce dépôt

même dépôt

loop-ignite

erp-mafia/accounted

Verify the agentic loops are actually running and ignite any that are not. Use at the start of any session, or whenever the user manually asks to "check the pr comments" / check logs / triage issues, which signals a loop is not firing. The loops exist (dev_docs/loops.md); the historical failure mode is that nobody initiates them.

2026-07-17185

create-extension

erp-mafia/accounted

Generate and implement extensions for Accounted: scaffold files, configure manifests, write event handlers, API routes, services, workspace UIs, settings panels, and testing. Use when creating new extensions, adding surfaces to existing extensions, or understanding the extension architecture. Covers the full lifecycle from scaffolding to registration.

2026-07-04185

create-ticket

erp-mafia/accounted

Create a detailed Linear ticket from a prompt. Asks 5 clarifying questions one at a time, scans the codebase, previews the ticket, and creates it via Linear MCP. Supports prompt templates: /create-ticket /security, /create-ticket /design <area>, /create-ticket <free text>.

2026-07-04185

erp-api-route

erp-mafia/accounted

Generate Next.js 16 API routes for Accounted with correct auth guards, Supabase client usage, event emission, journal entry creation, and error handling. Use when creating new API endpoints in app/api/. Handles the Next.js 16 async params pattern, ensureInitialized() for events, non-blocking journal entry wrapping, and defense-in-depth user_id filtering.

2026-07-04185

iso-27001-2022-compliance

erp-mafia/accounted

Authoritative reference for verifying ISO/IEC 27001:2022 compliance from a code repository. Use whenever a task involves auditing, automating, or generating evidence for ISO 27001 controls, the ISMS document set (Clauses 4-10), the Statement of Applicability (SoA), or Annex A controls (A.5 Organizational, A.6 People, A.7 Physical, A.8 Technological). Trigger on mentions of ISO 27001, ISO/IEC 27001, 27001:2022, ISMS, SoA, Annex A, "Statement of Applicability", a specific control identifier (A.5.x, A.6.x, A.7.x, A.8.x), Checkov/Trivy/Steampipe ISO compliance specs, the 2013-to-2022 control transition, NIST 800-53 / CIS Controls / SOC 2 crosswalks, agentic auditing of policy documents, or building CI/CD pipeline gates for security compliance. Trigger even when phrasing is indirect ("is our Terraform compliant", "scan our policies for audit readiness", "what does the standard require for cryptography", "map our controls to SOC 2", "build a compliance scanner"), these all qualify.

2026-07-04185

loop-design-scan

erp-mafia/accounted

Local loop that scans a given area of the Accounted UI against the locked design system (.claude/rules/design.md) for UX friction, visual inconsistency, missing states, motion gaps, and accessibility issues (rendering pages in Chrome), then files GitHub issues for approved findings. Run locally (needs npm run dev + Chrome). Usage: /loop-design-scan <area> (e.g. bookkeeping, invoices, settings).

2026-07-04185

name	loop-issue-triage
description	Proactive loop that keeps GitHub Issues in erp-mafia/accounted tidy (label, dedupe, close stale/already-fixed, reconcile with merged PRs) and auto-implements small, well-scoped fixes as PRs. Use on a schedule (cloud routine) or on-demand via /loop-issue-triage. Follows dev_docs/loops.md (propose-don't-merge).

loop-issue-triage

Goal: the open-issue list is accurately labeled and free of stale/duplicate/already-fixed items, and a couple of small fixes ship as PRs each run. Never merge. Read .claude/loops.md first.

Preflight

gh auth status, repo erp-mafia/accounted. If it fails, stop and report "environment not provisioned".

1. Triage every open issue

gh issue list --state open --limit 100 --json number,title,labels,createdAt,updatedAt,comments

For each issue lacking a type label:

Classify → apply one of bug / enhancement / question / documentation.
Dedupe → search for near-duplicates (gh issue list --search "<keywords> in:title,body state:all"). If a duplicate, label duplicate, comment linking the canonical issue, and close the newer one.
Stale → no activity > 30 days AND not actionable: comment asking if still relevant; don't close unilaterally unless clearly obsolete.

2. Reconcile with completed work (the "are tickets up to date?" job)

For each open issue, check whether a merged PR or recent commit already resolved it: gh pr list --state merged --search "<#num or keywords>", git log --oneline -S"<keyword>".
If resolved: comment with the PR/commit link, verify the fix exists in main, then close.
Conversely, if a merged PR said Closes #N but #N is still open, close it with a pointer.

3. Auto-fix small issues (propose-don't-merge): cap 2 PRs/run

Branch loop/issue-<n>, minimal fix, run the loop-verify gate.
Open PR with body Closes #<n> + a one-line summary. Label loop:auto, loop:triage.
If the fix turns out larger/riskier than expected mid-way, abandon the branch and instead add a scoping comment on the issue + loop:needs-human.

4. Anti-thrash & report

Don't re-triage issues already labeled this run. Summarize: labeled N, deduped N, closed N (with why), fix PRs opened, escalated N. That summary is the completion notification.