Skip to content

chore: add Claude Code configuration and update Xcode version#171

Merged
joaolfp merged 2 commits into
masterfrom
chore/add-claude-config
Jun 27, 2026
Merged

chore: add Claude Code configuration and update Xcode version#171
joaolfp merged 2 commits into
masterfrom
chore/add-claude-config

Conversation

@joaolfp

@joaolfp joaolfp commented Jun 27, 2026

Copy link
Copy Markdown
Collaborator

✨ Summary

  • add CLAUDE.md with codebase documentation for Claude Code
  • add .claude/ directory with commands and skills configuration
  • migrate pr-summary skill from .cursor/ to .claude/skills/
  • update Xcode version from 26.1.1 to 26.5

🔧 Type of Change

  • ✨ Enhancement
  • 🐞 Bug fix
  • 🔐 Security fix
  • 💥 Breaking change
  • 🚀 New feature
  • 📦 New release
  • 📚 Documentation
  • ♻️ Refactor

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@mergify

mergify Bot commented Jun 27, 2026

Copy link
Copy Markdown

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

  • Queue this pull request

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces several new commands and skills for Claude Code, including workflows for automated code reviews, PR summaries, and opening PRs, alongside a new CLAUDE.md guidance file. The review feedback highlights several improvement opportunities in the scripts, such as using git add -u instead of git add -A to prevent staging untracked files, using --body-file with gh pr create to avoid shell escaping issues, and ensuring pr-description.md is added to .gitignore to prevent accidental commits of temporary files.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

- If the current branch is `main` (or the default branch):
- Inspect the unstaged/staged changes (via `git diff` and `git status`) to infer a branch name in kebab-case that matches the type of change (e.g. `docs/update-readme`, `feat/add-login`, `fix/crash-on-startup`).
- Run `git checkout -b <inferred-branch-name>` to create and switch to the new branch.
- Stage all changed files with `git add -A` and commit them with an appropriate conventional-commit message.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Using git add -A automatically stages all untracked and modified files, which can accidentally commit sensitive files, build artifacts, or temporary files that aren't ignored by .gitignore. It is safer to use git add -u to only stage tracked files, or explicitly ask/confirm with the user before staging all untracked files.

Suggested change
- Stage all changed files with `git add -A` and commit them with an appropriate conventional-commit message.
- Stage modified files with git add -u (or ask the user before staging untracked files) and commit them with an appropriate conventional-commit message.


6. **Push and create the PR**
- Push the branch to the remote: `git push -u origin <branch>`.
- Create the PR with `gh pr create` using `--title`, `--head`, `--base main`, and `--body` with the generated description.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Passing a multi-line markdown description directly to --body in a shell command can easily cause shell escaping issues, syntax errors, or truncation. It is much safer to write the description to a temporary file and use gh pr create --body-file (or -F ), or pass the body via standard input.

Suggested change
- Create the PR with `gh pr create` using `--title`, `--head`, `--base main`, and `--body` with the generated description.
- Create the PR with gh pr create using --title, --head, --base main, and --body-file with the generated description written to a temporary file.


6. **Deliver the result**
- Reply with the PR summary in a **markdown code block** (so the user can copy it from the chat).
- **Also write** the same content to `pr-description.md` in the repository root so the user can open the file and copy from there. Tell the user the file path; they can delete the file after pasting into the PR.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Writing pr-description.md to the repository root will leave an untracked file in the user's working directory, which might be accidentally committed if they run git add . or git add -A later. To prevent this, consider suggesting that the user add pr-description.md to their .gitignore file, or write it to a standard temporary directory.

Suggested change
- **Also write** the same content to `pr-description.md` in the repository root so the user can open the file and copy from there. Tell the user the file path; they can delete the file after pasting into the PR.
- **Also write** the same content to pr-description.md (ensure this file is in .gitignore to avoid accidental commits) in the repository root so the user can open the file and copy from there. Tell the user the file path; they can delete the file after pasting into the PR.


6. **Deliver the result**
- Reply with the PR summary in a **markdown code block** (so the user can copy it from the chat).
- **Also write** the same content to `pr-description.md` in the repository root so the user can open the file and copy from there. Tell the user the file path; they can delete the file after pasting into the PR.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Writing pr-description.md to the repository root will leave an untracked file in the user's working directory, which might be accidentally committed if they run git add . or git add -A later. To prevent this, consider suggesting that the user add pr-description.md to their .gitignore file, or write it to a standard temporary directory.

Suggested change
- **Also write** the same content to `pr-description.md` in the repository root so the user can open the file and copy from there. Tell the user the file path; they can delete the file after pasting into the PR.
- **Also write** the same content to pr-description.md (ensure this file is in .gitignore to avoid accidental commits) in the repository root so the user can open the file and copy from there. Tell the user the file path; they can delete the file after pasting into the PR.

@github-actions

Copy link
Copy Markdown
1 Warning
⚠️ Big PR

Generated by 🚫 Danger

@codecov

codecov Bot commented Jun 27, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 64.16%. Comparing base (fecf589) to head (665ad45).
⚠️ Report is 56 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #171      +/-   ##
==========================================
- Coverage   67.52%   64.16%   -3.37%     
==========================================
  Files           6        6              
  Lines         194      173      -21     
==========================================
- Hits          131      111      -20     
+ Misses         63       62       -1     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@joaolfp joaolfp merged commit 6041b8f into master Jun 27, 2026
5 of 6 checks passed
@joaolfp joaolfp deleted the chore/add-claude-config branch June 27, 2026 03:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant