feat: review Gustavo and Marcos submitted skills
This commit is contained in:
@@ -0,0 +1,24 @@
|
||||
---
|
||||
name: confluence-page
|
||||
description: Create or update a reviewed Confluence page from a local storage-format draft. Use when the user asks to prepare or publish through an available, approved Confluence connector; require confirmation immediately before publication.
|
||||
---
|
||||
|
||||
# confluence-page
|
||||
|
||||
## Inputs
|
||||
Draft file, target space and title, parent or page ID when applicable, and the requested publication intent.
|
||||
|
||||
## Workflow
|
||||
1. Check that the configured connector is available and approved. If it is not, prepare the draft and report the exact next step.
|
||||
2. Create one storage-format draft per page, using a configured draft root or a repository-relative path.
|
||||
3. Run the package preflight checks; resolve title collisions and compare updates with the current server body.
|
||||
4. Show the destination, operation, and content summary. Request explicit confirmation for this create or update.
|
||||
5. Publish only after confirmation, then return the page ID, URL, and version.
|
||||
|
||||
## Rules
|
||||
- Never include secrets, tokens, PII, or local-machine paths in page content.
|
||||
- Do not delete pages or attachments.
|
||||
- Keep the local mirror read-only until the user requests a publication.
|
||||
|
||||
## Output
|
||||
Return the draft path, validation results, target, confirmation status, and—after publication—the page identifier and URL.
|
||||
@@ -0,0 +1,23 @@
|
||||
---
|
||||
name: diagram-plantuml
|
||||
description: Create a PlantUML diagram and a Confluence storage-format macro for a reviewed page. Use when a user needs a diagram embedded in a supported Confluence page.
|
||||
---
|
||||
|
||||
# diagram-plantuml
|
||||
|
||||
## Inputs
|
||||
The relationship to explain, target page context, and any approved diagram conventions.
|
||||
|
||||
## Workflow
|
||||
1. Choose a diagram type with `references/diagram-types.md`.
|
||||
2. Build a small local `.puml` source with a caption and only approved includes.
|
||||
3. Run a local syntax check when the configured renderer is available.
|
||||
4. Return the storage macro and state whether syntax and target rendering were independently verified.
|
||||
|
||||
## Rules
|
||||
- Keep macro markup at the required storage-body level.
|
||||
- Never load remote or untrusted `!include` sources.
|
||||
- Do not claim a rendered result without a target-environment preview.
|
||||
|
||||
## Output
|
||||
Return the diagram source, storage macro, validation result, and any target-environment prerequisite.
|
||||
@@ -0,0 +1,24 @@
|
||||
---
|
||||
name: gfiber-logging
|
||||
description: Decide and review GFiber service log levels while keeping production INFO output bounded and traceable. Use when adding, changing, or auditing service logs.
|
||||
---
|
||||
|
||||
# gfiber-logging
|
||||
|
||||
## Inputs
|
||||
Changed paths or service root, the request or flow under review, and the project logging configuration.
|
||||
|
||||
## Workflow
|
||||
1. Read `references/levels.md` to classify each event; use `references/cases.md` for known service patterns.
|
||||
2. Check new lines for correlation, minimized fields, and bounded volume.
|
||||
3. Use `references/audit.md` for a static audit; measure representative traffic separately when a path is high-volume.
|
||||
4. Report each finding with evidence and distinguish measured results from risk estimates.
|
||||
|
||||
## Rules
|
||||
- Use the approved contextual logger when the project supports one.
|
||||
- Never log secrets, PII, or full request/response bodies; cap identifier lists.
|
||||
- Treat INFO caps and DEBUG deployment settings as project configuration facts. Report missing evidence rather than assuming them.
|
||||
- This skill is read-only. Do not edit code or production configuration.
|
||||
|
||||
## Output
|
||||
State the scope, each finding (location, level, reason, volume risk, action), audit command/results, and any unmeasured risk.
|
||||
@@ -0,0 +1,22 @@
|
||||
---
|
||||
name: page-reviewer
|
||||
description: Review a Confluence-ready draft and its posting context before publication. Use when a user wants an evidence-backed PASS, REVISE, or BLOCK verdict; this skill never publishes or edits a page.
|
||||
---
|
||||
|
||||
# page-reviewer
|
||||
|
||||
## Inputs
|
||||
Draft body, intended space/title/parent, and any available approved connector context.
|
||||
|
||||
## Workflow
|
||||
1. Run deterministic local checks for content safety, storage structure, links, and diagram markup.
|
||||
2. If an approved connector is available, check title and target context; otherwise report that check as unavailable.
|
||||
3. Anchor every finding to a line or section and issue PASS, REVISE, or BLOCK.
|
||||
|
||||
## Rules
|
||||
- Never publish, edit, or treat placeholders as safe secrets.
|
||||
- Distinguish allowed internal destinations from unverified hosts using the project policy.
|
||||
- A missing required validation is a stated limitation, not a pass.
|
||||
|
||||
## Output
|
||||
Return verdict, scope, findings (severity, anchor, evidence, action), checks run, and the next safe step.
|
||||
@@ -0,0 +1,22 @@
|
||||
---
|
||||
name: unslop
|
||||
description: Suggest precise, audience-appropriate revisions for generic or overly polished prose while preserving meaning. Use when a user asks to review a draft’s voice or clarity.
|
||||
---
|
||||
|
||||
# unslop
|
||||
|
||||
## Inputs
|
||||
Draft text, intended audience, and an applicable project style reference when one exists.
|
||||
|
||||
## Workflow
|
||||
1. Preserve frontmatter, code, XML/HTML, quotations, and technical claims.
|
||||
2. Identify specific tells using `references/tells.md`; consult the selected style reference before recommending a change.
|
||||
3. Return small, anchored edits and explain the reader benefit.
|
||||
|
||||
## Rules
|
||||
- Do not call a dialect, disagreement, or concise writing “slop.”
|
||||
- Do not rewrite facts, cited wording, or structured content for style.
|
||||
- Treat scoring thresholds as review aids, not publication gates, unless the project defines them.
|
||||
|
||||
## Output
|
||||
Return the audience assumption, findings, minimal suggested diffs, preserved sections, and any style-policy uncertainty.
|
||||
Reference in New Issue
Block a user