ado-get
Skill0 starsChanged 27 days agoMITView on GitHub
Mostra um resumo de um work item do Azure DevOps a partir do ID. Usa o MCP azure-devops.
In this repository28 other files it gives its agents.
- ado-closeSkill
- ado-commentSkill
- ado-refineSkill
- adrSkill
- approve-reviewSkill
- appSkill
- autoSkill
- challenge-specSkill
- completeSkill
- dart-clean-archSkill
- discoverySkill
- fixSkill
- flutter-clean-archSkill
- implementSkill
- jira-refineSkill
- kickoffSkill
- linear-refineSkill
- orcamentoSkill
- planSkill
- post-reviewSkill
- pr-openSkill
- pr-statusSkill
- refineSkill
- reviewSkill
- specifySkill
- statusSkill
- tasksSkill
- verifySkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
Apresentar: no chat com este formato:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Resumo rapido de um work item.
Defaults
- Org / Project: os do tracker da org do repo (
orgs[].trackerno.dashboard.json, configurado no app;python3 ~/.claude/bin/tracker.py resolve). Passe-os às tools do MCP.
Se o usuario passar --org=... ou --project=... nos args, sobrescreva. Se passar so um numero, e o ID.
Passos
- Validar entrada. Se nao houver ID nos args, pergunte e pare.
- Buscar o work item via tool do MCP
azure-devops(work item get / wit_get_work_item ou equivalente disponivel na sessao). Inclua os campos: title, state, assignedTo, workItemType, tags, iterationPath, areaPath, description, acceptanceCriteria, reproSteps (quando aplicavel). - Buscar comentários recentes (ate os 5 mais novos) via tool de comments do MCP.
- Apresentar no chat com este formato:
#<id> [<type>] <title>
Estado: <state> · Iteration: <iterationPath> · Assignee: <assignedTo or "—">
Tags: <tags or "—">
<description em texto plano, max 30 linhas; resumir se maior>
Criterios de aceite (se houver):
<acceptanceCriteria>
Comentários recentes:
- <autor, data relativa>: <primeira linha>
- ...- Pare. Nao tome ação nenhuma. Espere o usuario decidir o próximo passo (
/ado-refine,/ado-comment, etc).
Notas
- HTML em descricao do ADO: converta para texto plano legivel (remova tags, preserve quebras).
- Se o item nao existir ou o PAT nao tiver permissao, mostre o erro do MCP cru e sugira checar PAT/scope.
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.