Conversation
|
👋 pkcll, thanks for creating this pull request! To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team. Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks! |
There was a problem hiding this comment.
Pull request overview
This PR adds Cursor IDE configuration for triaging and fixing Chainlink CI failures, along with project-specific rules for Git, GitHub CLI, and Go development workflows.
Changes:
- Added a Cursor skill (
fix-chainlink-ci) with reference documentation, examples, and workflow guidance for handling GitHub Actions failures - Added Cursor rules for
ghCLI usage, Git workflow safety, and Go coding standards - Added
.cursorignoreto exclude sensitive files and large dependency directories from indexing
Reviewed changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
.cursorignore |
Excludes secrets, credentials, cloud config, and dependency directories from Cursor indexing |
.cursor/skills/fix-chainlink-ci/reference.md |
Command reference for debugging Chainlink PR CI failures using gh and git |
.cursor/skills/fix-chainlink-ci/examples.md |
Worked example demonstrating CI triage workflow for PR #20708 |
.cursor/skills/fix-chainlink-ci/SKILL.md |
Main skill definition with workflow for diagnosing and fixing CI failures |
.cursor/rules/go.mdc |
Go coding guidelines for Chainlink including style, testing, and module management |
.cursor/rules/git.mdc |
Git workflow rules covering safety, rebasing, staging discipline, and worktree usage |
.cursor/rules/gh-cli.mdc |
GitHub CLI usage patterns for PR inspection, CI debugging, and API queries |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| - edit files, remove conflict markers, keep intended behavior | ||
| - `git add <files>` | ||
| - `git rebase --continue` | ||
| - If the rebase requires rewriting history, push with `--force-with-lease` (never plain `--force`). If session rules require it, propose the exact command and wait for explicit confirmation. |
There was a problem hiding this comment.
The phrase 'If session rules require it' is ambiguous. Consider clarifying what 'session rules' means in this context or removing the conditional if it always requires confirmation.
| - If the rebase requires rewriting history, push with `--force-with-lease` (never plain `--force`). If session rules require it, propose the exact command and wait for explicit confirmation. | |
| - If the rebase requires rewriting history, push with `--force-with-lease` (never plain `--force`). If your organization’s or this project’s contribution policies require prior approval before force-pushing, propose the exact command and wait for explicit confirmation. |
|
1 participant
Summary
gh,git, and Go style/testing references..cursorignorebaseline to avoid indexing secrets and heavy dependency dirs.Usage
If CI is red, you can use the Cursor command
/fix-chainlink-ciwith a PR link or failing job/run link to triage and suggest the minimal fix.ghCLI; local repo checkout (~/repos/chainlink)/fix-chainlink-ci <PR URL | PR number | failing Actions job/run URL>Examples
/fix-chainlink-ci https://github.com/smartcontractkit/chainlink/pull/20708/fix-chainlink-ci https://github.com/smartcontractkit/chainlink/actions/runs/<run-id>/job/<job-id>