What is posttask-workspace-lint?

A post-work checklist for running the appropriate linting, type checks, builds, and tests in the parts of a monorepo that were changed. A monorepo is one repository containing several projects or applications.

Finding the affected subprojects, reading their local instructions, and running the right validation commands for Java, frontend, and other touched modules.

It avoids declaring work complete after checking only root-level scripts when the changed application or library has its own required checks.

posttask-workspace-lint — Skill by Joaonic

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/joaonic/agentkit/posttask-workspace-lint

Any agent

npx skills add Joaonic/agentkit --skill posttask-workspace-lint

Clone the repo

git clone --depth 1 https://github.com/Joaonic/agentkit

Made for: Claude Code, Codex.

Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 610 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00045	$0.00610
Opus 5	$0.00023	$0.00305
Sonnet 5	$0.00009	$0.00122
Haiku 4.5	$0.00005	$0.00061

Measured 2d ago against content hash aef584c761f9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

posttask-workspace-lint scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

src/core/skills/posttask-workspace-lint/SKILL.md · 46 lines

What it actually says

Posttask Workspace Lint

Objetivo

No monorepo YourProject, qualidade local vive no subprojeto. Antes de declarar conclusão, rodar os comandos que o próprio módulo define (README, package.json, pom.xml), agrupados por pasta tocada.

Quando é obrigatório

Qualquer alteração sob apps/<serviço>/, web/<app>/, ou libraries/<lib>/.
Consultar AGENTS.md e README do subprojeto quando existirem (40-submodule-governance.mdc).

Detecção de escopo

A partir de git diff, lista de ficheiros, ou instrução explícita do utilizador → extrair prefixos de primeiro nível (apps/foo, web/bar, …).
Agrupar por subprojeto (segmento imediato após apps/, web/, libraries/).
Mudanças só em docs/, .cursor/, scripts na raiz sem tocar código de app → pode não haver módulo Maven/Yarn; marcar comandos como n/a com motivo.

Comandos padrão (sobrescrever pelo README local)

Área	Onde executar	Comandos típicos
Backend Java	Diretório com `pom.xml` do serviço	`./mvnw verify` ou `./mvnw test`
Library Java	Raiz da biblioteca	`./mvnw verify` / `./mvnw test`
Frontend	Raiz do app (`package.json`)	`yarn lint`, `yarn build`, `yarn test` (se scripts existirem)

Se só uma classe ou pacote mudou e verify for pesado, pode usar alvo restrito desde que o README/CI do projeto aceite (ex.: ./mvnw -pl modulo test quando multi-módulo).

Relatório obrigatório

Tabela:

Qualquer fail bloqueia conclusão (alinhado a posttask / 30-posttask.mdc).
n/a só com razão explícita (ex.: alteração só em Markdown na raiz).

Relação com outras skills

posttask — gate global de evidência; esta skill especializa por workspace no monorepo.
lint-fix — usar quando falhas forem corrigíveis por autofix seguro no escopo tocado.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2d ago First seen · 46 lines · 45 tokens per session scan A aef584c761f9

Subscribe to this mod's changes

posttask-workspace-lint is a skill published in the GitHub repository Joaonic/agentkit (2 stars, last pushed 3mo ago), licensed MIT. It adds 45 tokens to every session and 610 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens