Address Pr Comments Cecil Agent Skill

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.

474 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

294

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/Cecilapp/Cecil --skill address-pr-comments-cecil

The instruction itself

5 sections, as written by the author

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

Reproduction
Identify the exact issue described by the reviewer.
Reproduce with the smallest possible scenario.
Confirm expected vs. actual behavior.

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.

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.

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.

Other skills for the same job

different authors, same section of the catalogue

Receiving Code Review

by ZhanlinCui

×7

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

2k tokens

Requesting Code Review

by ZhanlinCui

×6

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

Comprehensive GitHub code review with AI-powered swarm coordination

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.

Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.

Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.

Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

2k tokens

How to use it

Copy the folder

Take cecilapp/address-pr-comments-cecil from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.