agentsclimarketplace

Address pr comments cecil

Skill Cecilapp/Cecil/.github/skills/address-pr-comments-cecil

A simple and powerful content-driven static site generator.

Install
npx -y skills add Cecilapp/Cecil --skill address-pr-comments-cecil

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

Standard workflow to address pull request review comments in Cecil. Use when responding to review feedback, fixing requested changes, or preparing a clear reviewer reply with reproduction, fix, tests, and response.

SKILL.md

1.9 KB, as published. Nobody here has run it

Address PR Comments (Cecil)

Use this workflow to process review feedback consistently.

Response profile: Standard.

Scope

  • Applies to PR comments and requested changes.
  • Goal: produce a correct fix and a reviewer-ready response.

Required Sequence

  1. Reproduction
  • Identify the exact issue described by the reviewer.
  • Reproduce with the smallest possible scenario.
  • Confirm expected vs. actual behavior.
  1. Fix
  • Implement the minimal safe change.
  • Preserve existing public behavior unless the review explicitly requests a behavior change.
  • Follow project conventions in AGENTS.md and .github/instructions/php-src.instructions.md.
  1. Tests and checks
  • Run the smallest relevant checks first.
  • Use project commands as needed: composer code:style, composer code:analyse, composer test, composer test:cli.
  • If a check is skipped, state it explicitly with reason.
  1. Reviewer response
  • Explain what was changed and why.
  • Reference files and key lines.
  • Summarize validation performed and outcomes.
  • Call out risks, assumptions, and follow-ups if any.
  • Keep details concise but sufficient for asynchronous review (what changed, why, and proof of validation).

Output Template

Use this structure in your final PR comment response:

  • Issue reproduced: yes/no + short evidence
  • Fix applied: concise summary + impacted files/components
  • Validation: commands run + result (passed/failed/skipped)
  • Notes: assumptions, limitations, risks, or next steps

Guardrails

  • Do not include unrelated refactors.
  • Do not revert user changes outside the scope.
  • Keep diffs focused and reviewable.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.