Skill Claude Code
Gera documento de release em PT-BR a partir do diff entre duas tags git. Uso manual.
not rated 11 1mo ago A 25 tokens
archived
abort
02Skill Claude CodeCodex
Abandon the active feature. This is irreversible — aborted features cannot be resumed.
not rated 11
changed 1mo ago A 0 tokens
archived
Skill Claude CodeCodex
Walk through the review comments on the current branch's open pull request one at a time, evaluate each, let the user decide which to address, then produce a plan for the approved ones. This skill is read-only: it never edits code. Fixes happen later, after the plan is approved.
not rated 11
changed 1mo ago A 0 tokens
archived
Skill Claude CodeCodex
Resolve every Figma component the layout uses to its original component, in the file where it is declared, then emit a verdict per node — verified against the real codebase — and confirm every verdict with the user before returning.
not rated 11
changed 1mo ago A 0 tokens
archived
autodoc
05Skill Claude CodeCodex
Language: Always write the documentation in Brazilian Portuguese (pt-BR) — prose, headings, and explanations. Keep in English the technical and product terms that are conventionally used in English in software/product work (e.g. Tech Stack, endpoint, deploy, queue, worker, cron, payload, index, request/response…
not rated 11 1mo ago A 0 tokens
archived
completing
06Skill Claude CodeCodex
Finalize the feature: verify everything works, merge or create PR, produce completion summary.
not rated 11
changed 1mo ago A 0 tokens
archived
design
07Skill Claude CodeCodex
Help turn ideas into fully formed technical designs through natural collaborative dialogue.
not rated 11
changed 1mo ago A 0 tokens
archived
features
08Skill Claude CodeCodex
List all features and their current states.
not rated 11 1mo ago A 0 tokens
archived
Skill Claude CodeCodex
Before EVERY Figma MCP tool call, you MUST check.
not rated 11
changed 1mo ago A 0 tokens
archived
history
10Skill Claude CodeCodex
Display the full event timeline for the active feature.
not rated 11 1mo ago A 0 tokens
archived
implementing
11Skill Claude CodeCodex
Orchestrate plan execution by delegating to subagent-driven-development.
not rated 11
changed 1mo ago A 0 tokens
archived
new
12Skill Claude CodeCodex
You are starting a new feature workflow. Follow these steps exactly.
not rated 11
changed 1mo ago A 0 tokens
archived
next
13Skill Claude CodeCodex
You are advancing the active feature to the next workflow phase. Follow these steps exactly.
not rated 11
changed 1mo ago A 0 tokens
archived
Skill Claude CodeCodex
Read Figma designs during the design phase: parse the URL, inventory the screens and components, extract all Dev Mode data annotations, and capture the theme-correct token values of the screens. Produces the ## Recursos do Figma section (including ### Anotações de Design) and the artifacts/figma-tokens.md artifact for…
not rated 11
changed 1mo ago B 0 tokens
archived
reviewing
15Skill Claude CodeCodex
Perform a comprehensive 2-step code review of the completed feature implementation.
not rated 11
changed 1mo ago A 0 tokens
archived
status
16Skill Claude CodeCodex
Display the current state of the active feature.
not rated 11 1mo ago A 0 tokens
archived
Skill Claude CodeCodex
Execute plan by dispatching subagents per task. Tasks with no mutual dependencies run in parallel waves for faster execution.
not rated 11
changed 1mo ago A 0 tokens
archived
switch
18Skill Claude CodeCodex
Switch the active feature context. This command accepts an optional argument: the feature name or slug.
not rated 11 1mo ago A 0 tokens
archived
Skill Claude CodeCodex
Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, step-by-step instructions, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized…
not rated 11
changed 1mo ago A 0 tokens
archived
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: