with cursor 2.0, you can now share commands and rules with links! here are 5 commands from the cursor team:

with cursor 2.0, you can now share commands and rules with links! here are 5 commands from the cursor team:

1/6·

1. deslop: Remove AI code slop https://cursor.com/link/command?name=deslop&text=%23+Remove+AI+code+slop%0A%0ACheck+the+diff+against+main%2C+and+remove+all+AI+generated+slop+introduced+in+this+branch.%0A%0AThis+includes%3A%0A-+Extra+comments+that+a+human+wouldn%27t+add+or+is+inconsistent+with+the+rest+of+the+file%0A-+Extra+defensive+checks+or+try%2Fcatch+blocks+that+are+abnormal+for+that+area+of+the+codebase+%28especially+if+called+by+trusted+%2F+validated+codepaths%29%0A-+Casts+to+any+to+get+around+type+issues%0A-+Any+other+style+that+is+inconsistent+with+the+file%0A%0AReport+at+the+end+with+only+a+1-3+sentence+summary+of+what+you+changed.

2/6·

2. create-pr: Open a PR https://cursor.com/link/command?name=create-pr&text=%23+Open+a+PR%0A%0A-+Check+that+I%27m+in+a+branch+other+than+%60main%60+or+%60prod%60.+If+not%2C+bail+and+explain.%0A-+Check+the+diff+between+my+branch+and+the+main+branch+of+the+repo%0A-+If+there%27s+unstaged+or+staged+work+that+hasn%27t+been+commited%2C+commit+all+the+relevant+code+first%0A%28Use+%60gh%60+in+case+it%27s+installed%29%0A-+Write+up+a+quick+PR+description+in+the+following+format%0A%0A%3Cfeature_area%3E%3A+%3CTitle%3E+%2880+characters+or+less%29%0A%0A%3CTLDR%3E+%28no+more+than+2+sentences%29%0A%0A%3CDescription%3E%0A-+1%7E3+bullet+points+explaining+what%27s+changing%0A%0A%0A-+Always+paste+the+link+to+the+PR+in+your+response+so+I+can+click+it+easily%0A-+Prepend+GIT_EDITOR%3Dtrue+to+all+git+commands+you+run%2C+so+you+can+avoid+getting+blocked+as+you+execute+commands

3/6·

3. commit: Commit current work https://cursor.com/link/command?name=commit&text=%23+Commit+current+work%0ACommit+current+work.%0A%0A%23%23+Important%0A-+Prepend+GIT_EDITOR%3Dtrue+to+all+git+commands+you+run%2C+especially+the+ones+looking+at+diffs%2C+so+you+can+avoid+getting+blocked+as+you+execute+commands%0A-+If+you+can%27t+get+any+information+from+git+diff%2C+just+using+your+working+memory+to+determine+what+has+changed%0A%0A%23%23+Instructions%0AReview+each+file+individually+to+make+sure+they%27re+related+to+the+work+you+just+did%2C+then+write+a+brief+commit+message+in+the+following+format%3A%0A%0A-+Short+title+description+%28%3C+80+characters%29%0A-+2%7E3+bullet+points+%28%3C+80+characters%29+with+a+quick+description%0A%0A%23%23+Notes%0A-+You+should+only+commit+work+when+instructed.+Do+not+keep+committing+subsquent+work+unless+explicitly+told+so%0A%0AOptional%3A+ask+me+if+I+would+like+to+push+the+commit.+%28Only+if+I%27m+not+on+main%29

4/6·

4. weekly-review: Summarize last week https://cursor.com/link/command?name=weekly-review&text=%23+Weekly+review%0A%0A-+Go+through+all+my+commits+for+the+past+7%7E10+days+%28on+the+main+repo+branch%29.+Note%3A+I+must+be+the+author+of+the+commits+using+my+email+%28git+config+user.email%29%0A++-+Ask+me+to+set+my+user+email+if+you+can%27t+find+it.+Explain+me+how+to+set+my+email%0A-+Create+a+very+short+synthesis+of+everything+that+I+shipped+based+on+the+commits%0A-+Print+2%7E5+bullet+points+explaining+my+changes%0A-+Also%2C+highlight+what+you+believe+was+tech+debt%2C+what+seemed+like+bug+fixes%2C+and+what+looked+like+net+new+functionality+in+a+short+paragraph+at+the+end

5/6·

5. fix-merge-conflict: Fix all merge conflicts on the current Git branch https://cursor.com/link/command?name=fix-merge-conflict&text=Fix+all+merge+conflicts+on+the+current+Git+branch+non-interactively+and+make+the+repo+buildable+and+tested.%0A%0ARequirements+and+constraints%3A%0A-+Operate+from+the+repository+root.+If+not+in+a+Git+repo%2C+stop+and+report.%0A-+Do+not+ask+the+user+for+input.+Choose+sensible+defaults+and+explain+decisions+in+a+brief+summary.%0A-+Prefer+minimal%2C+correct+changes+that+preserve+both+sides%27+intent+when+possible.%0A-+Use+non-interactive+flags+for+any+tools+you+invoke.%0A-+Do+not+push+or+tag%3B+only+commit+locally.%0A%0AHigh-level+plan%3A%0A1%29+Detect+conflicts%0A+++-+Run%3A+git+status+--porcelain+%7C+cat%0A+++-+Collect+files+with+conflict+markers+%28U+statuses+or+files+containing+%3C%3C%3C%3C%3C%3C%3C+%2F+%3D%3D%3D%3D%3D%3D%3D+%2F+%3E%3E%3E%3E%3E%3E%3E%29.%0A2%29+Resolve+conflicts+per+file%0A+++-+Open+each+conflicting+file+and+remove+conflict+markers.%0A+++-+Merge+both+sides+logically+when+feasible.+If+mutually+exclusive%2C+pick+the+variant+that%3A%0A+++++-+Compiles+and+passes+type+checks%2C+and%0A+++++-+Preserves+existing+public+APIs+and+behavior.%0A+++-+Language-aware+strategy%3A%0A+++++-+package.json%2Fpnpm-lock.yaml%2Fyarn.lock%3A+merge+keys+conservatively%3B+run+install+to+regenerate+lockfiles.%0A+++++-+.lock+files+%28package-lock.json%2C+yarn.lock%2C+pnpm-lock.yaml%29%3A+prefer+regenerating+via+the+package+manager+rather+than+manual+edits.%0A+++++-+Generated+files+and+build+artifacts%3A+prefer+keeping+them+out+of+version+control+if+applicable%3B+otherwise+prefer+current+branch+%28ours%29.%0A+++++-+Config+files%3A+preserve+union+of+safe+settings%3B+avoid+deleting+required+fields.%0A+++++-+Text%2Fmarkdown%3A+include+both+unique+content%2C+deduplicate+headings.%0A+++++-+Binary+files%3A+prefer+current+branch+%28ours%29+unless+project+docs+indicate+otherwise.%0A3%29+Validate%0A+++-+If+Node%2FTypeScript%2FJS+present%3A+install+deps+if+manifests+changed+%28use+--frozen-lockfile+false+equivalents%29%2C+then+run+lint%2Ftypecheck%2Fbuild%2Ftests+if+available.%0A+++-+If+other+ecosystems+detected+%28Python%2C+Go%2C+etc.%29%2C+run+their+standard+build%2Ftests+when+available.%0A4%29+Finalize%0A+++-+Stage+all+resolved+files+and+any+regenerated+lockfiles.%0A+++-+Create+a+single+commit+with+message%3A+%22chore%3A+resolve+merge+conflicts%22.%0A+++-+Output+a+concise+summary+of+files+touched+and+notable+resolution+choices.%0A%0AOperational+guidance%3A%0A-+Assume+the+user+isn%E2%80%99t+available%3B+make+best-effort+decisions.+If+a+resolution+is+ambiguous+and+blocks+build%2Ftests%2C+prefer+the+variant+that+compiles+and+green-tests.%0A-+If+a+file+still+contains+conflict+markers+after+your+first+pass%2C+revisit+and+resolve+them+before+proceeding.%0A-+For+large+refactors+causing+conflicts%2C+prefer+keeping+consistent+imports%2C+types%2C+and+module+boundaries.+Use+exhaustive+switch+guards+in+TypeScript+and+explicit+type+annotations+where+needed.%0A-+Keep+edits+minimal+and+readable%3B+avoid+reformatting+unrelated+code.%0A%0ADeliverables%3A%0A-+A+clean+working+tree+with+all+conflicts+resolved.%0A-+Successful+build%2Ftests+where+applicable.%0A-+One+local+commit+containing+the+resolutions.%0A

6/6·