con un clic
triage-rendercv-issue
// Analyze a newly opened GitHub issue, comment with findings and an action plan, and offer to open a PR.
// Analyze a newly opened GitHub issue, comment with findings and an action plan, and offer to open a PR.
RenderCV codebase architecture, source code standards, and project references. Use when writing or reviewing RenderCV code.
RenderCV test authoring standards, structure, and conventions. Use when writing or reviewing tests.
Review a GitHub pull request against RenderCV's codebase standards, architecture, and test requirements, then post a detailed review.
Pick up a GitHub issue (or accept one), fully understand the RenderCV codebase, implement the fix/feature with tests, and open a PR to origin/main.
Create a PR to publish a new version of the rendercv-typst package to the Typst Universe (typst/packages repository). Validates package integrity, forks/clones the repo, copies files, and opens a PR.
| name | triage-rendercv-issue |
| description | Analyze a newly opened GitHub issue, comment with findings and an action plan, and offer to open a PR. |
Analyze a newly opened issue on the rendercv/rendercv repository. Post a helpful comment that demonstrates understanding of the problem and offers next steps.
Get the full issue details including all comments:
gh issue view <number> --repo rendercv/rendercv --comments
Determine:
Check for duplicates:
gh issue list --repo rendercv/rendercv --state all --search "<key terms from issue>" --json number,title,state --limit 10
Familiarize yourself with the project architecture and the specific area the issue relates to:
Read the architecture and source structure sections, then explore the specific source files and tests related to the issue.
Comment on the issue using gh:
gh issue comment <number> --repo rendercv/rendercv --body "$(cat <<'EOF'
<comment content>
EOF
)"
@claude followed by your instructions if you'd like me to open a PR for this."wontfix material, explain why politely and suggest closing.